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
This is caused by the RTF document. Due to the way RTF is designed, there are many ways to represent the same styled document. Java stores the information in a more abstract way, and then regenerates the flat document on demand. This usually comes out as a slightly different representation, with the same visual results. Unfortunately, I can't really make a visual comparison (or, at least, certainly not efficiently), so detecting real changes is quite difficult.
A better solution might be to register a change listener to the underlying document. Or better yet, an UndoManager - if there is nothing to undo, it can probably be assumed that there have been no changes.
I have temporarily fixed this in 8eb131f by using a document listener as well as comparing only certain properties of the frames resources.
However I also had to reset the variable when visibility of the frame changed, so I am wondering if maybe IsmAvatar's idea of checking the undo manager, which the frame does now have, is a little more elegant.
Edit: At the current moment in time that solution is not possible because as soon as a new project is loaded the frame is reverted and starts out with at least 1 bullshit undo.
After fixing the behavior of the undo manager in 5344d6a to know when to properly clear its undo history on a visibility change or revert I can say that this now properly works, as such I am closing this ticket as resolved.
Open a game like Street Race.gm6 and open the game infomation and close it. LGM acts like you've changed something.
The text was updated successfully, but these errors were encountered: