View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002143||Ham Radio Deluxe||Enhancement||public||2017-07-19 20:16||2019-11-08 02:32|
|Target Version||Fixed in Version||22.214.171.124|
|Summary||0002143: Option to disable column width change notification on Logbook exit|
|Description||As part of a recent build a new warning notification was added upon Logbook exit. This notification informs the user that columns widths have changed and asks whether the current settings should be saved. At best, this is an annoyance as I typically use the Logbook width command to resize the columns to match displayed data.|
I am request that an option be added to turn off this notification as I receive it each time I go to exit Logbook and it is quite annoying to have to respond each time I exit.
|Steps To Reproduce||Hit Logbook "Width" button to dynamically resize columns.|
Notification dialog will display.
|Tags||No tags attached.|
Possible dialog box:
Columns widths have changed. Save them to profile named "Default"?
[ ] Don't ask each time I exit Logbook
I think this is at least a partial duplicate of 2588.
This issue (2143) doesn't capture the fact that column widht is presently stored for the whole application rather than per database (by name) or per database vie (by each window; there can be more than one view of the database records per database that's open.
2588 correctly captures the fact that there are several settings that probably should be saved per database, probably retrieved and applied based on the name of the database when it is opened. This might be a little bit complicated given the Logbook's attempt to provide some pre-defined "layouts" for windows, controls, and columns. It requires some care to sort out because the different views might or might not change -- columns shown in the various Award views, for example.
I think this issue (2143) should be closed as "won't fix" or "duplicate", and then we can get to work on the decisions and design necessary to address the larger issue described by 2588.
|2017-07-19 20:16||k2ie||New Issue|
|2017-07-20 04:18||k2ie||Note Added: 0003700|
|2019-03-02 01:14||WA9PIE||Assigned To||=> K7ZCZ|
|2019-03-02 01:14||WA9PIE||Status||new => assigned|
|2019-03-02 01:14||WA9PIE||Project||1 - Backlog => 3 - Current Dev List|
|2019-05-09 15:07||K7ZCZ||Note Added: 0007923|
|2019-05-09 15:07||K7ZCZ||Relationship added||related to 0002588|
|2019-05-09 15:13||K7ZCZ||Note Edited: 0007923||View Revisions|
|2019-10-25 03:36||K7ZCZ||Status||assigned => resolved|
|2019-10-25 03:36||K7ZCZ||Resolution||open => duplicate|
|2019-10-25 03:36||K7ZCZ||Testing||=> Not Started|
|2019-11-04 03:31||WA9PIE||Status||resolved => closed|
|2019-11-04 03:31||WA9PIE||Fixed in Version||=> 126.96.36.199|
|2019-11-08 02:08||WA9PIE||Fixed in Version||188.8.131.52 => 184.108.40.206|
|2019-11-08 02:32||WA9PIE||Project||3 - Current Dev List => Ham Radio Deluxe|