Opened 10 years ago
Last modified 7 years ago
#31 assigned enhancement
Add ability to reload configuration without restarting
Reported by: | Lewis Rosenthal | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Release_1.1 |
Component: | eFTE core | Version: | PreRelease_1.0 |
Keywords: | Cc: |
Description
Currently, any configuration change needs to be re-read upon program startup. It is not possible to make a configuration change and have that change read by the running instance, requiring a shutdown/restart of the app. A "Reload configuration" item on the Edit menu would be a welcome enhancement.
Change History (8)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
I think the way to do this is to have the first version attempt to open the second with the new configuration. If the 2nd fails to open the first version will remain open to allow the user to fix the config error that caused the second to fail. If it succeeds the second will close the first. I can pass the first's PID on the command line to tell the second it is a config reload (affects a potential error message) and tell it who to close on success.
comment:3 by , 9 years ago
Milestone: | → Release_1.0 |
---|---|
Owner: | set to |
Status: | new → assigned |
comment:4 by , 9 years ago
Tested this History isn't very good at getting you to the same point. Need to research when and how this is saved. Need to start in efte directory to use temp.dsk. Perhaps putting efte in the data path would solve this.
comment:5 by , 9 years ago
Version: | 1.0 → PreRelease_1.0 |
---|
comment:6 by , 9 years ago
Status: | assigned → accepted |
---|
comment:7 by , 9 years ago
Milestone: | Release_1.0 → Release_1.1 |
---|
comment:8 by , 7 years ago
Owner: | removed |
---|---|
Status: | accepted → assigned |
The easy way to achieve this would be to have efte exit and then reload itself to the same state using a temp history and desktop file. Need to remember to set the indent style. Need to research how close the reload is to the original (i.e. cursor placement selections etc). Need to cleanup after. How should broken config errors be handled?