 |
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
 Posted: Thu Dec 06, 2007 4:57 pm
Couple of version history questions.
|
| Quote: |
| Shift-ESC now only works when a thread is actually needed for the command line |
I assume that this means a thread's only created if the command line thread is running something at the time that Shift-Esc is pushed?
| Quote: |
| Added "Compatible versions" filter option to Package Library to only show packages with version fields compatible with running CMUD version |
How strict are you going to be about this? WoW for example considers any addon from a previous version incompatible (and refuses to load them, but you can override that if the addon's from the same major version but an earlier minor version. Addons from earlier major versions can't be loaded ever, though). Since CMUD preserves backwards-compatability much more than the WoW UI does, but also has the added problem of an addon being meant for a newer version than the client has, you could take this either way. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Dec 06, 2007 7:11 pm
|
| Quote: |
| I assume that this means a thread's only created if the command line thread is running something at the time that Shift-Esc is pushed? |
Yes. The command line must have already created a thread. So the command line needed to be using a #WAITxxx or #THREAD command. If you just enter a big #LOOP into the command line, a thread isn't created, so there is no way to implement Shift-Esc. This makes Shift-Esc a pretty minor and useless "feature", but I decided the speed improvement of only creating a thread when it was needed was more important.
| Quote: |
| Added "Compatible versions" filter option to Package Library to only show packages with version fields compatible with running CMUD version |
You'll notice that a package has two new fields: Minimum Version and Maximum Version. The "Show Compatible versions" filter requires that the currently running CMUD version must be >= the Minimum and <= the Maximum. It's up to you (the package designer) to set these fields properly.
When you create a new package, the Minimum is set to CurrentMajorVersion.00 and the Maximum is set to CurrentMajorVersion.99. This is what people suggested in another thread where this feature was first requested.
You can still use or install *any* package. The "Show Compatible" filter just filters the Package Library display, and it isn't even enabled by default. |
|
|
|
|
|
|
|
|
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
|
|
