Actions
Bug #44
closedchirp XML editing problems
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/07/2012
Due date:
% Done:
0%
Estimated time:
Chirp Version:
daily
Model affected:
XML
Platform:
Linux
I read the instructions above:
Description
- You cannot enter a frequency which is not divisible by 2.5Khz. W1AW uses many frequencies which are not. Yes, specific radios have specific step size limitations in their frequency synthesizers. Limit has no business being applied when editing an XML file.
- Insert row above works but insert row below does not if you are on last memory location (but additional memory locations are valid).
- Adding new memory locations is a major pain. It will not display more memory locations than were in XML file or manually added one by one. To add a memory location, you must go to the last entry, insert row above, select the last two locations, right click -> exchange memory locations. Then you can use insert above to add some new empties but it is very slow and tedious. Propmpt the user for how many rows to insert.
- When you insert row above, it always scrolls to the top. This gets really unpleasant if you are working down at memory location 50 or 200.
- when you insert row above, you are forced to dismiss a dialog box "moved 7 entries [DONE]"
- There is no setting for power level. Yes, radios have different support for power levels. That is a conversion issue. Pick the nearest, nearest below, or nearest above depending on user preferences.
- selection of lines is very unreliable. Sometimes you select a cell, sometimes a row.
- copy and paste cannot do an insert. So you have to tediously insert two dozen blank cells to overwrite.
- move memory/selection up/down can only move by one line at a time.
- There is no Duplex "Split". Even though that option is available on, for example, a UV-3R binary file. This makes it very hard to create entries for amateur satellites. UV-3R and VX-7R support splits. If you copy and paste a split from a binary file, it gives an error saying "Pasted memory 7 is not compatible with this radio because: Duplex split not supported". Chirp XML is supposed to be a superset of radio features, not a subset.
- There is no everride if you try to copy or import a memory it does not like. Frequently it is the program which is wrong, not the user.
- There is no TX Disable column or setting. Yeah, some radios aren't good at supporting this. On one radio you might set power level to 0W, on another you might set duplex to no-tx, on another there might be a specific bit for this, on another you might split frequency to 0hz transmit, on another you might set modulation no-tx, split to a frequency outside the permitted range on radios where this disables TX, and as a last resort you might want to force power to the lowest level (for example 0.05W on VX-7R), split to a relatively innocuous frequency that is within the VCO range but way outside the passband (60db down) and lowest power level, split to a frequency in the relatively unregulated ISM bands, or split to a relatively unusued frequency inside the ham bands and select the lowest power level. Of course, a decent radio would support a NO-TX bit in the channel memory and have a "battle shunt" mode that overrides NO-TX in case you want to send a distress call on a frequency you can't legally transmit on in other circumstances. You do not want to accidently transmit on police, fire, weather, air traffic control, maritime, FM broadcast, FRS/GMRS, CB, beacon, PLB, or other scanner/receive only frequencies.
- Copy and paste fails if you copy multiple records to the last record - it does not increase last record number to make room.
- Import XML pedanticaly validates its XML input. This is inconsistent with interoperability with other programs and even between versions of chirp. XML fields should be allowed in any order (XSD:Any vs XSD:Sequence) within a record. Any XML field should be allowed to be missing. Any XML field whose tag name is unrecognized should not cause import to fail. Issue a warning instead (one warning dialog per file imported, not per error). Pedantically validate your output, not your input.
- XML export is not formatted properly. It is not human readable. Include line breaks and indent. Run through xmltidy for an example. Properly formated XML will import OK.
- Scrolling horizontall does not kep the loc, Frequency, and Name columns on left as it should.
- There is no comment field or other annotations. Prior suggestion to use CSV is recommending stone age technology. Many of these also effect editing a binary file.
Files
Actions