|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Thu Dec 13, 2007 6:53 am
A suggestion about how to display IDs in the Package Editor |
When an ID is blank the name displayed in the editor is the trigger text or the event name, etc. If an ID is defined it becomes the ID in the editor. Since I like to see what the event is triggering on or what the trigger text is, I find this mildly annoying that I have to select the trigger/event to see what it triggers on.
A small enhancement for usability would be to put the ID in parens () right after the normal name if an ID is supplied. That way you can see the ID if it has one and you can always see the trigger/event info as well. |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Thu Dec 13, 2007 5:39 pm |
I'll add that to the wish list. The reason it shows the ID is that usually people have given a name to a complex trigger where the name is more recognizable than the complex trigger pattern.
|
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Thu Dec 13, 2007 9:37 pm |
For me I only add an ID so I can enable/disable it via a script. I guess I'm more utilitarian, having the ID replace the trigger text just obscures it for me, causing me to have to click on them to remember what the trigger matches. With a decent folder structure I never have a problem recognizing what my patterns do. Your explanation comes as a bit of a surprise, as it would never have occurred to me to start assigning IDs just so it looked prettier.
|
|
|
|
Morgal Beginner
Joined: 06 Nov 2006 Posts: 26
|
Posted: Thu Dec 13, 2007 9:49 pm |
im with Reed on this, i only have IDs so i can #T+/- them... weird to hear people use them to make things pretty.
Could the replace not be an option?
Morgal |
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Thu Dec 13, 2007 9:57 pm |
There are a number of aesthetically pleasing combinations, such as:
This one makes the assumption that ID_Name is shorter and thus should be first:
(ID_Name) Normal_Trigger_Text
Or this one which gives preference to normal trigger text over the ID.
Normal_Trigger_Text (ID_Name) |
|
|
|
Guinn Wizard
Joined: 03 Mar 2001 Posts: 1127 Location: London
|
Posted: Thu Dec 13, 2007 10:01 pm |
I'd prefer the former since the ID is almost always going to be much shorter than the trigger text. If the text goes first you'll likely have the id pushed out of view
|
|
_________________ CMUD Pro, Windows Vista x64
Core2 Q6600, 4GB RAM, GeForce 8800GT
Because you need it for text... ;) |
|
|
|
ralgith Sorcerer
Joined: 13 Jan 2006 Posts: 715
|
Posted: Fri Dec 14, 2007 12:05 am |
I also vote for the former.
|
|
_________________ CrossOver: Windows Compatibility on Mac and Linux CMUD Advocate |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Jan 07, 2008 9:22 pm |
I'll add this to the wish list. Of course, with the former (placing the ID first), the sort order of the trigger in the tree view will be determined by the ID instead of the trigger pattern.
|
|
|
|
|
|