kopia lustrzana https://gitlab.com/eliggett/wfview
46
Feature requests
roeland jansen edytuje tę stronę 2023-02-15 18:38:29 +00:00
ID | Status | Priority | Description |
---|---|---|---|
009 | ip | low | add satellite setup pop-up window, where uplinik, downlink, mode (invert/non-invert), and fixed spectrum range is all set up |
012 | open | low | max hold time adjustment |
013 | open | low | audio scope for streamed audio |
015 | open | low | find serial number or other identifying method for devices over ethernet (if possible) |
018 | open | low | dual-channel RX audio w/ switch to select "dual" or mono |
019 | open | low | multiple rig preferences |
020 | open | low | Add 4M band |
021 | open | low | Add rigCaps supported band attribute, update Band tab |
026 | open | low | Handle control-c as proper quit, close rig connection nicely |
028 | open | low | Change permissions on password-containing preference file to 600 |
029 | open | low | Switch waterfall on/off (do we already have that? Maybe a hide button?) |
036 | open | low | Add "reverse mouse scroll direction" UI element and preference |
041 | open | medium | Use -h and --host command-line arguments, possibly additional ones, to support network connections that can be specified in a launcher icon or shortcut. How we handle passwords could be to always read that from the preference file, or, to have another command-line argument to load a specific preference file (per-rig basically). Something to think about. |
043 | open | low | Add spreadsheet-like editing to the software memory, banks, etc. Enhance satellite memory to include mode, invert/non-inverting, passband, etc |
044 | open | low | Add radio memory import/export to CSV (maybe just a menu item for this... I don't personally use the radio's built-in memory) |
045 | open | low | Realated to 001: ToFix overwrites the edges. Shoudln't we save it on start and restore on exit? |
Notes:
Peak-hold (012): When a new peak is found, reset a counter. With each new data that come in, add to the counter. If the new data are a new peak, keep the peak and reset the counter. If the counter reaches some "max", then reset the peak down to zero? So the reset condition is when the held-peak is old and has not been exceeded. And the holding condition is that we haven't held the peak very long. Or maybe decrease each seconds the peaks by so that a generated peak holds for max 10 seconds. Just like the Max Hold function being Off, 10 sec or On.