stmills said:
Does the History file start over each time Unitrunker shut down and re starts or is this an ongoing history?
The history
file (eg. the event log) continues to grow. However, the history grids start out empty each time the program is run. The grids are also limited to the last 8 hours (otherwise they'd eventually consume all memory bringing your system to its knees). I haven't had time to write the code to back-fill the history grids with the event logs from previous sessions. The other missing piece here is the ability to browse the event log files to see activity beyond 8 hours - eg. yesterday, a week ago, etc.
DiGiTaL Dee said:
I've been doing mass edits of labels and colors by editing the Unitrunker.xml file and using the Replace function in WordPad, since I wanted some different colors and longer radio ID labels, and needed to update mass numbers of talkgroups and radios with the same information.
You can stop using Wordpad or Notepad. You've got a real GUI. Use the multi-select feature. To select multiple items in a grid, hold down the control key while selecting (usually with mouse clicks). Select however many talkgroups or radio IDs, click the magnifying glass (on the toolbar). A new editing window will appear. Set the color (and other settings). Close the group or radio id window when you're done.
DiGiTaL Dee said:
Is it safe to modify and save the Unitrunker.xml file while the program is running without data loss, or will my changes be overwritten by Unitrunker when it updates the file itself when the program is closed?
A new Unitrunker.xml file is created each time (a) the program exits or (b) the user clicks the save icon.
The existing Unitrunker.xml file is renamed (a new revision number is assigned at this time) and the current system data is written as a fresh new Unitrunker.xml file.
DiGiTaL Dee said:
I do wish it had an auto-save function like the old versions did, mainly because of the possibility of power loss
With the new "journaled" archive system, I've purposely left this out. I was concerned that creating a new snapshot every 15 minutes or so would quickly consume too much disk space. We can come back to this later. Perhaps it isn't necessary to create a new snapshot - the program could create new "current" snapshot and auto-save to that. A manual save would create a new revision.
The other thought is - provided the user enabled event logging - it is possible to reconstruct the data from the event logs.
DiGiTaL Dee said:
I kind of miss the Finder function that the old versions had.
A finder is a must-have. The earlier prototype had this but it didn't survive the spring re-write. Look for an edit box in the various toolbars in a future release.
MattSR said:
the root system id is 3A0D - this is the system that has all the radio ID and group ID information
*snip*
The line looks like this:-
Code:
<System id="3A0D" type="Motorola" first="20071021115328" last="20080601014733" delegate="5D0D">
That's backwards. You want system 5D0D to delegate the responsibility of storing talkgroups and radio IDs to system 3D0D. Remove the "delegate=" attribute above, locate the <System> tag for 5D0D and add
delegate="3D0D".
BVince said:
Unitrunker does not see port 10. It gives me a choice of port 3 or port 13. Neither of these work of course.
This is a bug. Your system likely does not have a port 13. This same bug prevents the program from correctly recognizing port 10 (ports other than 1 through 9). For folks with a low numbered COM port, make sure the USB cable is plugged in
before starting the program. The radio need not be plugged-in or powered-on but the USB cable must be present (this isn't the way it should be - just the way it is for now).