When I edit a file, most of the time there is an asterisk to indicate that the file has been edited, but not always.
I just did a lot of node editing, then moved the selected object, but no indication that any change had been made on the title bar.
I am using Google Drive File Stream for file storage, libraries, art library, etc. which may be an indicator. GDFS isn’t like Google Drive - there are no complete file system on the computer - you mount a drive from the cloud and have a symbolic link off ~/ . I accept that it takes longer to load, but it’s only a couple of seconds more out of a 12-16 hour day.
And to reiterate, this is occasional. It’s not a graphical interface issue - if I refresh the screen or drag the Lightburn screen to the other physical screen, there’s still no asterisk.
I reopened LB and just repeated the activity using the same source file and as soon as I nudged a node, the asterisk returned.
If it happens again (It has happened a noticeable amount - that I couldn’t put it down to a glitch), I will close and see if it prompts for a save due to a change.
It’s possible there are specific operations that don’t set the modified flag - Changing the selection doesn’t, for example, so we add it to any operation that does alter the project, and it’s possible we’ve missed one. If you can narrow it down, that would help, but I’ll do a quick scan through the node edit and move code to see if I missed one.
Edit: Found one - Apply path to text didn’t set it, and I found a couple others as well, like splitting a primitive, breaking a path, or changing the draw order of shapes. All of these now have it, and it’ll be in the next update.
It’s possible that the Mac for some reason isn’t showing the modified flag on the title bar itself. We’ve had some issues in the past with the framework not repainting some controls, which is part of the reason we tried to update to a newer version, but that means a) dropping 10.11 support, and b) picking up a bunch of new performance issues which were only resolved by moving forward another version (IE dropping 10.12 support too), and that’s … unpalatable. I’ll have to dig a bit and see if I can figure out why it’s happening.
It’s not a problem, really. Just letting you know.
Now I know to always check and not rely on the asterisk (not that I did that often) its all good. If there was never an asterisk in the first place, it wouldn’t affect my workflow.
