Closed richardm90 closed 4 years ago
Interesting, thanks for raising this. We'll do some testing, try to recreate it, and see if we can tighten anything up to make it more robust.
Let us know if you find a way to consistently reproduce this issue
@connorholyday
I think I might have found it. I opened a source member, made some changes, saved the source member, and then pressed Ctrl+E to compile. The compile failed so I clicked on the Failed to compile area to see the messages and at this point the source seemed to revert to the state when it was originally opened.
If I then close the source and open it again the changes are intact so the save worked. It appears to be clicking on the Failed to compile area that is doing something to the state of the source.
Hey @richardm90 we've just fixed this bug :) expect it to be patched in the next update!
Great news, that was a nasty one.
@richardm90
We have just pushed out 0.4.4. Please restart ILEditor and test again.
Thanks!
Just tested this and it looks good, I'm not seeing that problem anymore.
I've added tentative to the title because it's not an issue I've been able to replicate the steps and it may already be a known issue and possibly even fixed.
This has happened twice now, the first time I thought I must have done something daft when I wasn't paying attention. I've been editing and saving a source file, I've then jumped over to my 5250 session to compile it and check the source listing jump back in to ILEditor2 make some further changes and so on and then at some point during this iterative process the source reverts to an earlier version of itself, not the last saved version, possibly the original version when it was first opened, but as I say I've not been able to replicate the steps so it's difficult to be sure.
Maybe when I'm jumping over to my 5250 session I'm pressing some combination of keys that is causing this, I'm not sure and will add to this issue when I get more evidence.