Open full view…

[Bug] Changing the description does not trigger to be saved

Tue, 01 Aug 2017 10:44:07 GMT

As the title already says, changing the description of an event does not mark the file as changed. Meaning once you will save and have not changed anything else (added/removed an event), it will not save anything any of your changes. Unfortunately I lost a lot of data because of it :( Hope this will be fixed soon.

Tue, 01 Aug 2017 12:17:56 GMT

I experimented a bit with this as I'm using AT2 intensively for a project. If there's something that's going to make me lose my work, I want to know about it up front. It seems that the only time information is lost is when you type in a field, then don't click anywhere outside the field before quitting or saving. This is true for Tags, Summary or any other field in the inspector. It also can happen in the event manager, although it might be less likely if you have OCD like me and tend to close extra windows before quitting programs. As long as the text is blue, the user interface hasn't submitted the changes to the back end of the program. If you quit or save with blue text in a form field, the back end in effect doesn't even know you have been updating. The most information you could lose would be the updates to a single field for a single event or entity. You can avoid this by just clicking outside the field anywhere: on another input area, out in the timeline or even outside the program on the desktop or the window for another program. Just remember that the blue text is a warning of sorts. The colour change has significance. So I'm not sure if this is a bug, so much as something that needs explicit mention in the user manual.

Wed, 02 Aug 2017 01:11:24 GMT

Hi, razyr is correct, at the moment when you type in a field, it will only update the information when you change the focus of the field (eg. clicking away from the field). Unfortunately saving does not change the focus of the field, which is why the last typed information in a text field in the inspector won't be saved. I just wanted to clarify creativemd, that this is what you are seeing? We will look into a way where saving the file changes the focus so that it saves the latest changes, but at the moment in order to avoid the problem, just remember to click away from the text field before you save the file. Jess

Tue, 08 Aug 2017 08:15:18 GMT

Sorry, for my late response. I'm pretty sure that's the issue. Thanks for you help, changing the focus is a lot faster than creating and removing a new event (my attempt to make sure it will be saved).