XWidgetSoft Forum

When you have entered the Xwidget IDE made a change to a timer, for instance changing the timer interval and then you quit the IDE it prompts you to save or quit.

Saving obviously implies that all your recent changes are accepted and saved to a config or preference area, registry or similar.

Cancel implies that all your changes have been abandoned and are NOT saved. This is how ALL traditional applications work - we all expect an application to act in this manner.

However, Xwidget does NOT respect a cancel option. It causes recent changes to be accepted rather than abandoned which causes confusion when coding or debugging. In the example above you can change the interval, exit the IDE, cancel all changes and when you return to the IDE you will find that the interval is the updated value and that Xwidget has not reverted to the previous value.

This is a BUG.

Workaround: None.

Severity : HIGH

Jim please add this to the ever-increasing, never-decreasing, rather embarassing list of bugs in Xwidget.

I will add it and check it Dean to confirm. Thanks

_________________
...and remember: don't take life too seriously...
My profile on Deviantart: http://jimking.deviantart.com/

Thanks Jim. It matters not whether you have autosave enabled or disabled, it always pops up with a save/cancel confirmation box (which it shouldn't if you haven't made any changes and also shouldn't if autosave is disabled) and it subsequently ignores any cancel.

- When the autosave is enabled no confirmation box appears. So works fine (tested)
- Yes. The cancel button seems that not works as it should and saves equally the changes (tested)

We had talk about it when Tony has uploaded the test version of Designer 2.0. A great addition and a VERY useful thing is the UNDO-REDO buttons. For the script screen the CLTR-Z / Y work fine, but for the designer's main screen doesn't exist any similar function..
Personally until Tony add this part, I always use the Package Button like a backup, so if something goes wrong, I run that .xwp and the previous state is restored.

_________________
...and remember: don't take life too seriously...
My profile on Deviantart: http://jimking.deviantart.com/

Undo/redo quite easy to achieve, any changes in the designer should write to an intermediate config file. If the file is different from the permanent config file then it should present a confirmation dialog to save. If the intermediate file is the same as the permanent config then no changes have been made and the dialog does not need to pop up when you close the designer.

Easy undo/redo on the designer is achieved by naming the intermediate config files with a suffix:

config.ini
config.ini.1
config.ini.2
config.ini.3
.
.
.
&c

The designer can open whichever older config it requires.

If the preferences are written to the registry then the save process uses the permanent config file and then writes the contents to the registry.

I think the designer automatically saves the IDE configuration whenever it runs in debug mode or similar so when you do exit and click to cancel the save, the save has already happened.

1. Please check that Do you checked the option "auto save"
2. when you click the "Run" or "Debug", IDE will save and run

_________________
XWidget Software Developer
[] [] []
[]

Tony, exactly, I found that out in my earlier post.

However, it is mean to be an IDE and it should act like one.

If you make a change in the designer and test it and find you don't want it - then exit - well, it has saved your changes whether you like it or not. The Save/cancel dialog prompt that pops up is then completely pointless.

It pops up regardless of whether you have made any code changes, it leads you to think that you can cancel your designer changes and you can't. It is a pointless and stupid addition to have a save/cancel that is there for no purpose other than to lead you astray.

It is a bug.

If the IDE has to save before running or debugging then it should save to intermediate config files as described above so that you can revert your changes when the dialog box states 'save' or 'cancel' and you press 'cancel'.

Tony, take your lead from how other IDEs do it. Follow what they do.