Wanted to just create a list of some issues I've seen in JS8 which I think would be relatively easy to fix/implement and isn't some fantastical wishlist. Surely, many of these issues have been mentioned, but hopefully there is at least one undocumented one in here.
*Clicking HB will send to group if selected to the right.
*No auto reply is somewhat random, if any msg detected in waterfall maybe. (can we just block that offset + mode bandwidth?)
*Is the offset change broken in JSON API for TX?
*Can't find good documentation of the API and it's behavior (I'll write this if you'd like, just want some input)
*HB timer resets if auto heartbeat reply is set (effectively it never sends unless band is dead)
*Messages in activity window not showing up in conversation window (that obvious should be there)
*Doubling/splitting of messages in conversation window (Sometime the splitting corrects when message is complete)
*The frequency scheduler seems a bit unintuitive. While I don't want to call it broken, is it?
Features which would be nice:
*Adding escape character to modify decoding display for lower case (example HTTP://URL.COM/^AB^CD^^ prints to screen as HTTP://URL.COM/aBcD^)
*APRS Buttons in program
*Now the harder one, a temp style graph that shows activity last X min/hour for clear slots (even a simple implementation that adds a +1 to predefined slots/frame, say 50hz, and clears every 10 mins would be useful to avoid a large timetable of values)
*Area to enter custom CAT commands before/after PTT, on program start/shutdown.
*MSG outbox expiration date
I do have about 20 years of hobby C programming (embedded, server side, sockets), and can contribute, but time constraints don't really allow me to dive deep into anything non-work related anymore. Like I mentioned, I'd be happy to document the API, and maybe a lot of heavy lifting or features can be implemented with 3rd party programs (JS8spotter comes to mind).
-Karlan AI5TS
Wanted to just create a list of some issues I've seen in JS8 which I think would be relatively easy to fix/implement and isn't some fantastical wishlist. Surely, many of these issues have been mentioned, but hopefully there is at least one undocumented one in here.
*Clicking HB will send to group if selected to the right.
*No auto reply is somewhat random, if any msg detected in waterfall maybe. (can we just block that offset + mode bandwidth?)
*Is the offset change broken in JSON API for TX?
*Can't find good documentation of the API and it's behavior (I'll write this if you'd like, just want some input)
*HB timer resets if auto heartbeat reply is set (effectively it never sends unless band is dead)
*Messages in activity window not showing up in conversation window (that obvious should be there)
*Doubling/splitting of messages in conversation window (Sometime the splitting corrects when message is complete)
*The frequency scheduler seems a bit unintuitive. While I don't want to call it broken, is it?
Features which would be nice:
*Adding escape character to modify decoding display for lower case (example HTTP://URL.COM/^AB^CD^^ prints to screen as HTTP://URL.COM/aBcD^)
*APRS Buttons in program
*Now the harder one, a temp style graph that shows activity last X min/hour for clear slots (even a simple implementation that adds a +1 to predefined slots/frame, say 50hz, and clears every 10 mins would be useful to avoid a large timetable of values)
*Area to enter custom CAT commands before/after PTT, on program start/shutdown.
*MSG outbox expiration date
I do have about 20 years of hobby C programming (embedded, server side, sockets), and can contribute, but time constraints don't really allow me to dive deep into anything non-work related anymore. Like I mentioned, I'd be happy to document the API, and maybe a lot of heavy lifting or features can be implemented with 3rd party programs (JS8spotter comes to mind).
-Karlan AI5TS