|
mazz Beginner
Joined: 27 Oct 2010 Posts: 15
|
Posted: Mon May 09, 2011 12:21 am
Rename/replace trigger line |
I can't get you the code to it but I have noticed sometimes while coding and I add a trigger line that is a replica, I get the below box about rename, delete, or cancel. And most times it freezes up where I have to end the program to do anything.
Ok, it seems I can't add attachments and I don't know how to do img so...
The box name is "Rename Setting" and it shows the exact trigger you were working on with the three options rename, delete, cancel.
CMUD version 3.34. It also did it on 3.33a. |
|
|
|
Rahab Wizard
Joined: 22 Mar 2007 Posts: 2320
|
Posted: Mon May 09, 2011 2:07 am |
Yes, if you try to create a new trigger whose name is identical to an existing trigger, you will get that message. You need to rename the trigger in order to save it. If you specify an id for a trigger, that is the trigger name. If you do not specify an id, the trigger pattern is the name. So, if you want to have two different triggers with the same pattern, you need to give them different id's. That message box allows you to give the trigger a unique id.
|
|
|
|
mazz Beginner
Joined: 27 Oct 2010 Posts: 15
|
Posted: Mon May 09, 2011 12:42 pm |
Rahab wrote: |
Yes, if you try to create a new trigger whose name is identical to an existing trigger, you will get that message. You need to rename the trigger in order to save it. If you specify an id for a trigger, that is the trigger name. If you do not specify an id, the trigger pattern is the name. So, if you want to have two different triggers with the same pattern, you need to give them different id's. That message box allows you to give the trigger a unique id. |
Yeah, I know what it does. The problem is if I try to cancel or rename it in some instance, CMUD completely freezes up causing me to have to end the program. I was wondering if anyone else had the same problem. |
|
|
|
Rahab Wizard
Joined: 22 Mar 2007 Posts: 2320
|
Posted: Mon May 09, 2011 12:57 pm |
No, I have not had that problem. I think you will have to do a little more testing and give a little more detail so we can reproduce it or give some suggestions. You say that it doesn't happen all the time. Can you narrow down the conditions under which it happens? Do you click or type anything that causes it to freeze up, or does it freeze as soon as it pops that window up? Is it a particular trigger pattern that this happens with? A particular package? Can you make it happen in a new session? At the moment, we have almost no information to work with.
|
|
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|