Custom Query (31 matches)
Results (10 - 12 of 31)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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. |
|||
#12 | fixed | Rework Find and Case commands: mark/token/word | ||
Description |
Esp. the mark commands do unexpected actions if nothing is marked. Additionally, not all commands exist yet. Moreover, the key assignments for these actions should be reworked. The changes have to be implemented in newmenu and in the popup menu. |
|||
#26 | fixed | Removing a key from its parent RegContainer value removes a zero char too much | ||
Description |
After executing NepmdDeleteConfigTree \NEPMD\User\AutoRestore
the section RegKey is OK, but in RegContainer, the entry for AutoRestore.AutoSave.Backup.Colors. ... .Toolbar. to AutoSaveBackup.Colors. ... .Toolbar. (zero chars replaced by single dots).
The faulty function is The removed RegKeys are: \NEPMD\User\AutoRestore\Ring\LoadLast \NEPMD\User\AutoRestore\Ring\MaxFiles \NEPMD\User\AutoRestore\Ring\SaveLast The removed RegContainer keys are: \NEPMD\User\AutoRestore\Ring \NEPMD\User\AutoRestore It may have relevance that two container levels were removed.
Luckily, this bug didn't appear until now. It has to be fixed before the deletion of a tree will be added to |