|
Post by AvaCam on Feb 16, 2008 18:44:09 GMT -5
I think a very good feature would be the ability to undo or redo changes that have been made to the buttons. I have on more than one occasion accidentally deleted a menu button and subsequently all of the the sub-buttons. At times like that I wished that I could undo my changes, thereby restoring the settings to before my boo boo. It could be presented when the edit buttons mode is enabled and look like the back/forward buttons from a browser (go Firefox!).
What do you think Moon?
|
|
|
Post by Exuro on Feb 16, 2008 19:44:28 GMT -5
Yea I have accidently deleted entire menus before. It is quite annoying. Maybe not an undo/redo thing, but @ the bottom of every button edit window should be a save button and a cancel button. That way if you screw up you hit cancel, and if you like your changes you hit save.
|
|
|
Post by Moongaze on Feb 18, 2008 16:35:54 GMT -5
I can do the cancel button on the bottom, instead of just having the X at the top of the window. As for an undo feature ... I *might* be able to store the LAST button's data in an undo database and if you make a mistake, it will restore the last button changed. If it was a menu button that got deleted, it will track all submenu buttons as well.
... no clue when I'll impliment that though ...
I could also pop a message box asking to confirm when a user will LOSE a group of submenu buttons ...
|
|
|
Post by Chaos on Feb 18, 2008 22:28:56 GMT -5
Go with the message box. It's not that hard to add and solves a lot. I'd say just make sure to include an option to disable it as well.
|
|
|
Post by AvaCam on Feb 18, 2008 23:39:29 GMT -5
Ooo I like the idea of prompting whether they're sure that they want to smoke the sub-menu and it's contents. How about an ability to backup/restore the configuration instead of undoing changes, would that be an easier stupid-user protector?
|
|
|
Post by Moongaze on Feb 19, 2008 15:21:32 GMT -5
When the template system is in place, the user could back up their configuration with a template, then restore it if they want. Thankfully, the undo idea that I had in mind could work out well, but only for the last change made. When the user logs in again, the undo state would be cleared again, to restore the extra 1k to 10k of memory it might eat.
There are a lot of options for how I can go about this. The prompt, I think, would be the best option. I originally was going to have a prompt for some parts of the button editing functionality, but pulled it at the last minute, thinking it wasn't needed.
|
|
|
Post by Exuro on Feb 20, 2008 0:13:07 GMT -5
Couldn't you make it so when you click on a button to edit it, LS copys and saves the current button data somewhere. Then after you change what you like and hit "save", the edit window closes, LS applys those changes, and deletes the copy of the old stuff. If you screw something up and hit "cancel", LS will then copy what you have in the other location and overwrite the current stuff, in essence undoing all chnanges you made since opening the button edit window that time. I don't think it would take extra memory since LS would delete the data after you save what you like. And from my limited programming experience I thing it would be possible. Let me know what you think.
|
|
|
Post by Moongaze on Feb 20, 2008 18:27:43 GMT -5
If I understand you correctly, it does that already. If you change the button click types or spell assignments and then hit X (or hit ESC), the button will not be changed. If you hit save, it will make the changes. The only time this is NOT true is when you edit the other features of the button (button size, distance, etc). Only the spell assignments and button actions are saved. I'm assuming you would want the button size and location data to also be saved with the backup, instead of just the button spell/action data? I think people forget about the X at the top-right of the window, or the ability to just close the window with ESC ... but maybe you mean something else?
|
|
|
Post by Exuro on Feb 20, 2008 20:28:22 GMT -5
Yea thats exactly what I meant. I didn't forget about the X, I just never knew that it had that functionality. It does make sence because is you exit the screen w/o hitting the save button, the settings shouldn't save. And for someone like me not to know the ins and outs of how LS works is a bit weird. I suggest of making it a bit more obvious in some way.
"I'm assuming you would want the button size and location data to also be saved with the backup, instead of just the button spell/action data?"
That statement is true and it would be nice if you would include that. And maybe to make it more obvious just copy the X functionalty into a cancel button next to the save one. I think that would stick out more to people b/c that is how most windows on the computer are. It is always click either "ok", or "cancel".
|
|
Kharon
Very Talkative Beta Tester
Posts: 100
|
Post by Kharon on Feb 21, 2008 1:22:32 GMT -5
-there should be a confirm dialog for ctrl-right clicking a menu button, cuz thats an easy mistake to make and not in the settings screen....
|
|
|
Post by Moongaze on Feb 21, 2008 15:13:32 GMT -5
Exuro: Agreed. The cancel button and the X button will use the same code (basically, when you click cancel, it will run the code in "X" ... so no double instances of the code). I will add the other settings to be backed up as well (button size, location, etc). Kharon: I'll add the dialog prompt for people who a) delete the menu button via holding CTRL, and b) override a menu in the button settings window by making it NOT a menu. This should help with both situations.
|
|