Custom Query (31 matches)
Results (7 - 9 of 31)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8 | fixed | Make test versions available before the release of 2.00 | ||
| Description |
Guessing from the development "speed" in the last months, it will take some more time to get 2.00 out (docs and a few remaining other items). Test versions should be downloadable, recently, just after a new working private build was done. That would make the beta release idea obsolete. |
|||
| #9 | fixed | Make key def strings in menu items update automatically with keyset change | ||
| Description |
The key def functions are already prepared for that. MenuAccelString() handles that. |
|||
| #10 | fixed | Rework key and maybe menu defs to use Save instead of SmartSave | ||
| Description |
A Save key or menu command should execute a Save (as expected), not a SmartSave. SmartSave would only save a file if it was changed. The original Save always saves a file. This was suggested by John Small. I don't like the idea to support the SMARTSAVE constant any further, because the key def file is already much too complicated. It provides much more options then the original. The additional complexity affords that we should really try to reduce the number of constants to zero. BTW: SMARTSAVE only applies on the key def, not on the menu items. Of course, they should be synchronous. |
|||
