This bug could be related to a previous one regarding menus, which has been fixed for 499.1197. However, this one doesn't seem to cause any crashing of Dream Seeker. Basically, macro sets can be created with winclone(), but they cannot be removed by setting "parent=false".
It would be nice to get this fixed, because it would make it easier to create hotkey customization systems for games. It's sad that so many games still rely on Dream Seeker for creating custom macros. A professional looking, well polished game should have a hotkey settings HUD, for intuitive customizing.
Numbered Steps to Reproduce Problem:
1. Create a new evironment.
2. Paste this code:
mob/verb
Clone_Macro_Set()
winclone(usr, "macro", "cloned-macro-set")
Remove_Macro_Set()
winset(usr, "cloned-macro-set", "parent=none")
world << winget(usr, null, "macros")
3. Compile and run the project.
4. Press F1 to open the "Options and Messages" window.
5. Click "Clone Macro Set" in the verb panel.
6. Click "Remove Macro Set", and observe that the macro set is still listed in the output. Also observe the message Dream Seeker shows: "winset: Element cloned-macro-set not found.", which is a contradiction.
Expected Results:
The macro set is deleted from the world.
Actual Results:
The winset() proc is unable to find the macro set, and so it has nothing to delete, so the macro set is stuck in the world.
Does the problem occur:
Every time? Or how often?
Every time.
In other games?
Quite possibly.
In other user accounts?
Probably.
On other computers?
Probably.
When does the problem NOT occur?
Maybe not in an alternate space-time!
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked?
I'm not sure.
Workarounds:
Reset the interface completely: winset(usr, null, "reset=true").