potential bug or intended: "activate" option in script edito

Post Reply
Caled
Posts: 399
Joined: Thu Apr 09, 2009 4:45 am

potential bug or intended: "activate" option in script edito

Post by Caled » Tue May 05, 2009 8:59 am

Am I supposed to be able to de-activate non-trigger script objects? They are all created as 'activated' by default, though upon saving these objects (keys, actions, aliases, scripts etc) for the first time, the little tip shows up explaining that it is saved and I may now activate it by clicking 'activate'.

If I do click 'activate', the object appears to be deactivated (the tick disappears) but as soon as I click any other object, the tick reappears.

It has been like this for a while, but I assumed it was meant to be like that (excepting the tip upon saving). It could be handy at times (during system building, and bug-finding) to be able to deactivate script objects in this way (event handler scripts in particular) but that's only a minor thing. I'm not sure whether the bug is in the tip appearing, or in the objects not deactivating.

User avatar
Heiko
Site Admin
Posts: 1548
Joined: Wed Mar 11, 2009 6:26 pm

Re: potential bug or intended: "activate" option in script edito

Post by Heiko » Wed May 06, 2009 8:50 am

The activate icon on scripts basically means that this script is not going to get compiled the next time you start Mudlet. It'll be used in later versions when the package management is in to activate certain packages.

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests