UpdateEntArea Improvement: Ability to lock autogenerated scenarios
UpdateEntArea autogenerated scenarios are great, but they are regenerated each router reload. This means that a user cannot customize the autogenerated scenarios at all.
I propose putting a 2nd checkbox by each autogenerated scenario in the web admin and designate it as locking the scenario. This means that it will not be overwritten the next time UpdateEntArea is run.
Most of the logic is already in UpdateEntArea right now. There is a hard-coded part that prevents this from happening for Lighting autogenerated scenarios (likely so that the On,Off and Showtime scenarios get updated accordingly if more lights are added to a room). If you notice, you can actually change most autogenerated media/telecom/security scenarios and the changes will survive a reload.....
I would like to conditional this hard-coded part and enable/disable it depending on whether an autogenerated scenario is "locked" or not.
To support this functionality, a new field must be added to pluto_main:CommandGroup named 'Locked', and have it placed after 'TemplateParm2'
SQL: ALTER TABLE 'CommandGroup' Add 'Locked' BOOL NOT NULL AFTER 'TemplateParm2';
I will then need SqlCVS run, followed by sql2cpp the resulting generated files committed to SVN, after which I can complete the addition of this feature.
Also, the appropriate web admin page will need changed to update the "Locked" field with a checkbox. I will change the layout of the autogenerated scenarios on the webpage to be in a table layout like so: ( [ ] = checkbox)
|------------------------------------
|Autogen Scenario | Show | Locked |
|------------------------------------
|On | [ ] | [ ] |
|Off | [ ] | [ ] |
|Showtime | [ ] | [ ] |
|etc... | [ ] | [ ] |
|------------------------------------
This will make it much neater, and easier to understand the meaning of the checkboxes.