| View previous topic :: View next topic |
| Author |
Message |
Chris Site Admin
Joined: 02 Mar 2004 Posts: 10467
|
Posted: Wed Jun 09, 2004 3:40 am Post subject: |
|
|
| I'm working on custom menus and submenus, which are taking a little longer than expected. Hopefully it will be ready on Thursday. |
|
| Back to top |
|
 |
beardboy
Joined: 02 Mar 2004 Posts: 444 Location: SLC, Utah
|
Posted: Wed Jun 09, 2004 3:51 am Post subject: |
|
|
| Quote: | | I'm working on custom menus and submenus, which are taking a little longer than expected. Hopefully it will be ready on Thursday. |
Great work as always Chris.
A_ExitReason
When you have an Application Error this is listed as just "Exit" could it be changed to "Error" or something else just different than "Exit"?
thanks,
beardboy |
|
| Back to top |
|
 |
Chris Site Admin
Joined: 02 Mar 2004 Posts: 10467
|
Posted: Wed Jun 09, 2004 1:22 pm Post subject: |
|
|
Are you talking about the Run/RunWait commands, when they give a runtime error that causes the current thread to exit? If you are, it's a great idea and corrects my oversight, since the current behavior is not intuitive.
I'm adding the reason "Error", described as: "A runtime error has occurred in a script that has no hotkeys and is not persistent. An example of a runtime error is Run/RunWait being unable to launch the specified item." |
|
| Back to top |
|
 |
beardboy
Joined: 02 Mar 2004 Posts: 444 Location: SLC, Utah
|
Posted: Wed Jun 09, 2004 1:28 pm Post subject: |
|
|
| Quote: | | Are you talking about the Run/RunWait commands, when they give a runtime error that causes the current thread to exit? |
Correct a runtime error caused by Run/RunWait.
thanks,
beardboy |
|
| Back to top |
|
 |
Chris Site Admin
Joined: 02 Mar 2004 Posts: 10467
|
Posted: Wed Jun 09, 2004 5:27 pm Post subject: |
|
|
Ok, but keep in mind I'm changing it so that all runtime errors cause that ExitReason. But most other types of runtime errors are much more rare than Run/RunWait.
Thanks again. |
|
| Back to top |
|
 |
|