You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I designed a label with both static and merge field and set format and location and it worked beautifully. Closed the .glabels file. 1. Moved the .csv file aside, and when I opened the .glabels file I would get an error about the missing .csv. It's probably a good idea to let user know about the missing location file right away hen you load the .glabels file, but it is even more important to generate that error when tying to use the missing data, i.e. when you print. 2. This leaves the Format field populated but the Location field is cleared in the UI. My suggestion would be to leave the Location field populated with the missing file path. It helps remind what file you used when about to set a new path. If you save the file a 2nd time (this requires an unrelated change) the original location is retained (correctly) but you cannot find the value in the UI (surprising). Maybe save should generate an error too? 3. When I then tried to print a label (with the cleared Location field), I would get a blank label which was surprising behavior to me. It should have been at least a partially populated label (i.e. left join with no data), however, I would suggest no label is generated (join with no data) at all along with an error that I suggested in 1.
No worries if you don't want to address this edge case in 3.x. Just figured it would be good document with this issue. Maybe something to check on for 4.x?
The text was updated successfully, but these errors were encountered:
Debian 10 (buster)
glabels 3.4.1-1-1
I designed a label with both static and merge field and set format and location and it worked beautifully. Closed the .glabels file. 1. Moved the .csv file aside, and when I opened the .glabels file I would get an error about the missing .csv. It's probably a good idea to let user know about the missing location file right away hen you load the .glabels file, but it is even more important to generate that error when tying to use the missing data, i.e. when you print. 2. This leaves the Format field populated but the Location field is cleared in the UI. My suggestion would be to leave the Location field populated with the missing file path. It helps remind what file you used when about to set a new path. If you save the file a 2nd time (this requires an unrelated change) the original location is retained (correctly) but you cannot find the value in the UI (surprising). Maybe save should generate an error too? 3. When I then tried to print a label (with the cleared Location field), I would get a blank label which was surprising behavior to me. It should have been at least a partially populated label (i.e. left join with no data), however, I would suggest no label is generated (join with no data) at all along with an error that I suggested in 1.
No worries if you don't want to address this edge case in 3.x. Just figured it would be good document with this issue. Maybe something to check on for 4.x?
The text was updated successfully, but these errors were encountered: