Zugg Software :: View topic - [3.05] Is requiring trig sub-states to be unique from other trigs intentional?

Posted: Sun Mar 15, 2009 2:17 am

In a class 'Test', create a trigger with pattern 'One'.
Create a second trigger with pattern 'Two'.
Create a trigger sub-state in 'Two' named 'One'.

The error window will now pop up telling you that it must be named something unique. Is this intentional? I see no reason why they can't have the same pattern as one is a sub-state.

Posted: Sun Mar 15, 2009 9:50 pm

I think you're are misunderstanding. The trigger IDs have to be unique the sub-state patterns do not have to be. By default CMUD makes the trigger pattern (up to 64 chars I believe) the ID. If you accept the proposed name you will see that the sub-state trigger has an ID of "One1" and a patter of "One" as indicated by "One1 : One" in the tree display. So yes, this is expected behavior. I believe CMUD has always operated like this (at least it should have been). Very Happy

Posted: Sun Mar 15, 2009 10:35 pm

Hi Tech, I do understand what it is doing, but I still don't see why it want or cares about sub-states.

Trigger: One

Trigger: Two
Sub-Trigger: One

Why it should care if Trigger 'One' and Sub-Trigger 'One' have the same name?

Posted: Mon Mar 16, 2009 5:56 am

Because the sub-state trigger, like all triggers has a unique ID. Now if you questioning whether or not sub-states should have unique id's, then that's something else altogether. I know you can you set state's specifically using #SET or #STATE but I think that goes my the main trigger ID.

The more I think about, I can see your point. Zugg'll have to weigh in on this one.

Posted: Mon Mar 16, 2009 5:53 pm

Yes, right now all trigger states need to have unique ID values. This is because they are stored in a database and the ID field is a unique key value for the records. Not something that is easily changed, sorry.