Some Data Fields are not accessible within Program

Need help? - Post here and we will find a solution for you.
Post Reply
User avatar
ac5ez
Novice Class
Posts: 13
Joined: 18 Jan 2017, 18:03
Location: Oak Point, TX USA

Some Data Fields are not accessible within Program

Post by ac5ez » 02 Oct 2018, 23:09

According to the Log4OM data structure there are three fields that do not appear on any of the QSO tabbed screens. They are:
APP_LOG4OM_MOBILE
APP_LOG4OM_QRP
APP_LOG4OM_PORTABLE
If I am reading these correctly one is for mobile operation, one is for QRP, and the third is for portable operation. There is ample real estate on the "Contest Information" tab where you show Ten-Ten, SKCC, FISTS, and FISTS CC information.
Right now these fields are not accessible. Using the comments or notes fields does not all any type of effective sorting.
73,
Ken, AC5EZ

User avatar
W7DRM
Moderator
Posts: 512
Joined: 19 Feb 2014, 20:44

Re: Some Data Fields are not accessible within Program

Post by W7DRM » 05 Oct 2018, 23:36

Hi Ken,

You are correct, those fields (Mobile, QRP and Portable) have been added to the log database structure, but they have not been added to the field layout for any of the display screens, like Recent QSO.

Possibly Lele can add those to the layout Column selection in the next maintenance release?

73,

Doug - W7DRM

User avatar
IW3HMH
Site Admin
Posts: 2200
Joined: 21 Jan 2013, 15:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: Some Data Fields are not accessible within Program

Post by IW3HMH » 16 Oct 2018, 18:27

Those data are "old" and not used anymore by Log4OM.
Those fields was used to expedite some activities in the code that was optimized and now run in real time.

They are in the data structure, and for that reason they are FULLY exported into ADIF.

By the way those fields are not set in any part of the code anymore, except on the data structures that read/write the ADIF and the database itself, so Log4OM is keeping them alive but not adding them anymore on new QSO. Basically they're there for retro-compatibility and to mantain consistent database output in ADIF.

I will probably dismiss them in the future from ADIF export.
Daniele Pistollato - IW3HMH

Post Reply