Thanks Tom. This is likely an unintended result of fixing the resize flicker for grid headers. I'll check this out.I have noticed a version 18 glitch. When you adjust the columns for the 'LCN, Frequency,Label, etc.', the column header adjusts but the columns underneath do not!?!? If you go to, for example, Peers and then back again to Call History, then the columns will adjust. Tom
If you're upgrading, this easy approach is to set the installation directory to match the working folder of your current (release 17 or earlier) installation when running the MSI installer.Mattsenft said:While I have felt pretty confident in knowing my way around the program, I couldn't figure out how to import my data from 17 into 18. Can you point me in the right direction?
I have noticed a version 18 glitch. When you adjust the columns for the 'LCN, Frequency,Label, etc.', the column header adjusts but the columns underneath do not!?!? If you go to, for example, Peers and then back again to Call History, then the columns will adjust. Tom
It's on the TODO list.Would it be possible? (Pretty please), to save the column adjustments when exiting the program so that they will be lined-up the way you had them the next time the program is run? Tom
I've added persistence of column settings on the main panel. The column info is saved at the tail end of the Configure.xml file. Look for it in release 19. If a user chooses to roll back, older versions should silently ignore this new, unexpected data.save the column adjustments when exiting the program
I've fixed that too for release 19.WyoWabbit said:the column header adjusts but the columns underneath do not!?!?
I cannot find .18 on the download page....
Column widths in the main window are saved (but not yet for other windows).
Hi Tom;
I've added persistence of column settings on the main panel. The column info is saved at the tail end of the Configure.xml file. Look for it in release 19. If a user chooses to roll back, older versions should silently ignore this new, unexpected data.
If this release goes well, I'll add it for the other windows. The reason for moving cautiously is the site/system windows' column settings will be saved in the Untrunker.xml data file. This change won't be backwards compatible. Previous versions of Unitrunker won't know how to skip over the new information.
In short, saving columns for Site/System windows should appear in release 20.
I've fixed that too for release 19.
FC402195AA0326A701
FC40211DAA03
FD081011
FC402195AA03
FC2CC301
FC402173AA03
FD081011
Will do.AudioDave1 said:Maybe a bug, check it out.
A much earlier version did this - a separate text file for each site. Release 19 knows to skip over the data so it could be used as a way to migrate backwards if needed. Your suggestion is sound but doesn't scale. Say I run into a similar situation in a few months. Should I create yet another new file? Don't forget the main data file is stored as multiple revisions. If they upgrade and run into problems, they can revert to the older version of the software and then revert to the slightly older version of their data.WyoRabbit said:Maybe, instead of adding the column settings to the end of this file, just use a new settings file?
Correct. The program could load the site's event log into the history grid but doesn't do so at this time. This is one of many fine ideas I've yet to do.Audiodave1 said:It appears the history for TG/UID's is lost on shut down unless I am missing something. The logging feature isn't related to history to my knowledge.
Not hard at all. How many users would be interested in using such a feature?Radioman96p71 said:How hard would it be to add a raw serial input to the decoders?