Re: QSL label design
Posted: 13 Feb 2013, 16:27
Kurt, double check if all parameters from QSL (qsl sent, sent date, received, received date, sent via, received via and so on) are EXPORTED from your current log into ADIF.
If not, you need to do a massive update once loaded into Log4OM to have all fields up-to-date.
I can't suggest you to move to Log4OM before you feel ready to do that, but you should take this into account to have less "troubles" later.
About hard coded labels:
you're true, i have decided to have an hard coded label print to let users have the label system available. My "work philosophy" is to deploy working (bug free) basic features and then grow them following user needs, suggestions and compliants.
As said i will periodically stop developing NEW features, and collect all user requests to make deep changes (if needed) to main functions to follow user needs and ideas.
Label customization is one of those points, like some flexibilities in cluster screen and other "utilities" like Net Control, recently deployed.
73
Daniele IW3HMH
If not, you need to do a massive update once loaded into Log4OM to have all fields up-to-date.
I can't suggest you to move to Log4OM before you feel ready to do that, but you should take this into account to have less "troubles" later.
About hard coded labels:
you're true, i have decided to have an hard coded label print to let users have the label system available. My "work philosophy" is to deploy working (bug free) basic features and then grow them following user needs, suggestions and compliants.
As said i will periodically stop developing NEW features, and collect all user requests to make deep changes (if needed) to main functions to follow user needs and ideas.
Label customization is one of those points, like some flexibilities in cluster screen and other "utilities" like Net Control, recently deployed.
73
Daniele IW3HMH