Custom Query (518 matches)
Results (1 - 3 of 518)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #425 | invalid | "Delete state" code fails to delete subject-related INI keys | ||
| Description |
The saved states include three "Subject"-related keys. When a state is deleted, these three keys are not deleted. |
|||
| #520 | fixed | "Quick" page help shows help too often | ||
| Description |
With a fresh install of FM/2, with no pre-existing FM3.INI file, it usually starts up by popping up the Settings notebook open to the "Quick" page and it also pops up the help for that page. This is all good. If one happens to close the settings notebook while the "Qucik" page is still displayed, then the next time FM/2 opens the settings notebook the "Quick" page is displayed again. This is also good. But the help page keeps popping up automatically, too! This is annoying. And it is misleading in the sense that one might think that whatever choice was made earlier has not been saved and that one has to make their choice again. |
|||
| #127 | fixed | "Remember" drive exclusion list | ||
| Description |
When running FM/2 for the first time after an installation of FM/2, FM/2 scans all the hard drives. If the drive scan "fails" on any drives a dialog pops up asking if it is OK to set a parameter for FM/2 that tells it not to scan those drives. Having to respond to this dialog after every install of FM/2 is annoying. And since many people have Windows on C: and the Windows partition is often unreadable from OS/2, I cannot believe I am alone in this experience. It would be nice if the parameters, including the "exclusion list", (e.g. /BC %*) could be "remembered" so that it could be re-applied during subsequent installations. One possible way to implement the "memory" would be within the FM3.INI file. Another possibility would be to use Henk Kelder's WPTOOL utility (which would query the existing object during the installation). |
|||
