You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An entry into a CW functionality could be a CW interface, which first of all only allows CW keying via Hamlib, adjustable for both rigs separately. From my view this should be connected with a relatively small programming expenditure ???
Later one could add other interfaces, like Winkey etc..
One application could initially be a simple window with CW memory keys.
In a new settings tab the settings for the CW interface per rig, an initial CW speed setting and the assignment of the memory keys could be made.
However, I'm not sure if it should wait until an integrated concept has been developed!
However, I would recommend to involve someone who already intensively uses the CW functions in an existing program (mostly Windows) already during the planning stage.
I myself have little experience on this subject. From my view there are various requirements and desires of users, so that one must assume surely of a higher planning expenditure for the functionality and the organization of the program modules.
You can also orientate yourself with 'N1MM Logger', 'UcxLog' or 'Log4OM2'. UcxLog (Shareware with free trial period) ist often used and Log4OM2 is a newer and free Logging Software. Possibly also 'Virtual ComPorts' for external keyers are required, which would then have to be implemented in the Linux version.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
An entry into a CW functionality could be a CW interface, which first of all only allows CW keying via Hamlib, adjustable for both rigs separately. From my view this should be connected with a relatively small programming expenditure ???
Later one could add other interfaces, like Winkey etc..
One application could initially be a simple window with CW memory keys.
In a new settings tab the settings for the CW interface per rig, an initial CW speed setting and the assignment of the memory keys could be made.
However, I'm not sure if it should wait until an integrated concept has been developed!
However, I would recommend to involve someone who already intensively uses the CW functions in an existing program (mostly Windows) already during the planning stage.
I myself have little experience on this subject. From my view there are various requirements and desires of users, so that one must assume surely of a higher planning expenditure for the functionality and the organization of the program modules.
You can also orientate yourself with 'N1MM Logger', 'UcxLog' or 'Log4OM2'. UcxLog (Shareware with free trial period) ist often used and Log4OM2 is a newer and free Logging Software. Possibly also 'Virtual ComPorts' for external keyers are required, which would then have to be implemented in the Linux version.
I think this will require some work.
Beta Was this translation helpful? Give feedback.
All reactions