Interface display

[G4DWV]

Hi,

Just out of curiosity could you please explain why the main window of log4OM s-l-o-w-l-y fills in when the main window has been drawn? It does not snap onto the screen as I would expect, even on subsequent loadings (from the cache).

I am not asking in order to complain at all, I am just curious from a programming point of view.

I know as little about programming as it is possible to know, without knowing anything . I will be starting to teach myself programming (C#) when my book (http://www.amazon.co.uk/gp/product/1119096685?) arrives. Visual Studio 2015 is already installed in a bare Windows 10 partition away from any distractions, ready to go.

TIA

Guy

[G4POP]

Just out of curiosity could you please explain why the main window of log4OM s-l-o-w-l-y fills in when the main window has been drawn? It does not snap onto the screen as I would expect, even on subsequent loadings (from the cache).

Checking my loading time in Help/Show log, the load time for the main window is 6 seconds on my i5 computer running Windows 10 and 9 seconds on my old Toshiba Pentium 4 laptop running XP

You can check yours the same way in show log check the timers between

Logwriter ############# Program started

to

Log4OMMainWindow: Database connected

Clearly this depends on the performance of your computer and particularly the graphics card and RAM but also other programs running in the background can slow things down.

Biggest culprit for slowing your computer down in Google Chrome which is very resource hungry and is very active in the background even when Google Chrome is not running !!!!!

[G4DWV]

I am asking relatively speaking, viz what I would expect compared with other programs running on the same PC with the same config; viz under identical conditions. The main window does not pop onto the screen, but gets drawn very slowly. No other program has an unexpectedly long load time other than Inkscape. I have Log4OM on two computers and the finding is the same on both.

What does the 'loading time' in the log actually measure? I am asking about the draw speed of the contents of the main window when loading - the elements seem to get drawn one my one. There is no "Log4OMMainWindow" in my logfile.

Chrome did have some issues with it running in the background when the browser itself was not loaded, but these were fixed some time ago. I have removed all instances of Google update. I run the vanilla chromium dev edition.

The load time is quite acceptable and my computer is running as lean as I can make it, even to the point of regularly checking that the prefetch database/system is not corrupted (not that rare on the computers I come across for fixing/repairing/tuning). It is just the relatively slow drawing speed of the elements of the main window contents that piqued my curiosity compared with other programs with a similarly busy main window.

[G4POP]

I am asking about the draw speed of the contents of the main window when loading - the elements seem to get drawn one my one.

With me that is the same as the load time recorded in the logfile, give or take the blink of an eye

Check out this screen grab from the time you see the cursor double click my shortcut on the desktop to fully open - This is in real time

https://youtu.be/KFBOwJr0fLw

[G4DWV]

Very nice picture of you both.

Your loading does *exactly* the same as mine, the window takes 2-3 seconds to fill in (starts at 0:07) rather than everything being there at the same time. I am not asking about the absolute load time, just the way it takes a few seconds for the main Log4OM to fill up. It is a very slow drawing of the contents so that it really does stand out compared with everything else on this PC.

I am happy with the load time (mine is similar to yours). I am just curious, from a programming point of view, about the window filling over two seconds.

[G4POP]

As you can see there are many things being loaded at runtime and that need to be present when the window is fully loaded, things like Geomagnetic data, band plans, SOTA lists etc.

#################################################################################################################
2016-01-08 15:32:07.5524 INFO: LogWriter: ########################################## PROGRAM STARTED ######################################################
2016-01-08 15:32:07.5564 INFO: LogWriter: #################################################################################################################
2016-01-08 15:32:07.5673 INFO: Log4OMMainWindow: ############## USER IS ADMINISTRATOR ##############
2016-01-08 15:32:07.5704 INFO: Log4OMMainWindow: Program started
2016-01-08 15:32:07.5744 INFO: Log4OMMainWindow: Log4OM folder set: C:\Users\g4poparrl.net\Google Drive\G4POP Log4OM\config\
2016-01-08 15:32:07.5774 INFO: Log4OMMainWindow: Log4OM backup folder set: C:\Users\g4poparrl.net\Google Drive\G4POP Log4OM\config\Backup\
2016-01-08 15:32:07.5814 INFO: Log4OMMainWindow: Log4OM hamlib folder set: C:\Users\g4poparrl.net\Google Drive\G4POP Log4OM\config\hamlib\
2016-01-08 15:32:07.5854 INFO: Log4OMMainWindow: Log4OM version: 1.25.0.0
2016-01-08 15:32:07.5944 INFO: FileManagement: CONFIG begin load
2016-01-08 15:32:07.6114 INFO: FileManagement: CONFIG load completed
2016-01-08 15:32:07.6164 INFO: Log4OMMainWindow: Executing preload auto-start sequence
2016-01-08 15:32:07.6194 INFO: Log4OMMainWindow: Preload auto-start sequence completed
2016-01-08 15:32:07.6324 INFO: FileManagement: File Management begin load localization
2016-01-08 15:32:07.6464 INFO: FileManagement: File Management localization loaded
2016-01-08 15:32:07.6534 INFO: Log4OMMainWindow: BAND LIST load start
2016-01-08 15:32:07.6654 INFO: Log4OMMainWindow: BAND LIST load completed
2016-01-08 15:32:07.6694 INFO: Log4OMMainWindow: CONTEST load start
2016-01-08 15:32:07.6734 INFO: Log4OMMainWindow: CONTEST load completed
2016-01-08 15:32:07.6764 INFO: Log4OMMainWindow: MODES load start
2016-01-08 15:32:07.7195 INFO: Log4OMMainWindow: MODES load completed
2016-01-08 15:32:07.7235 INFO: Log4OMMainWindow: SATELLITES load started
2016-01-08 15:32:07.7275 INFO: Log4OMMainWindow: SATELLITES load completed
2016-01-08 15:32:07.7305 INFO: Log4OMMainWindow: Loading Awards list
2016-01-08 15:32:07.7345 INFO: FileManagement: AWARD LIST begin load
2016-01-08 15:32:07.7525 INFO: FileManagement: AWARD LIST load completed
2016-01-08 15:32:07.7555 INFO: Log4OMMainWindow: Awards list loaded
2016-01-08 15:32:07.7675 INFO: Log4OMMainWindow: Loading activations list
2016-01-08 15:32:07.7785 INFO: ActivationManagement: GetActivationList started
2016-01-08 15:32:07.8656 INFO: ActivationManagement: GetActivationList completed
2016-01-08 15:32:07.8706 INFO: Log4OMMainWindow: Activations list loaded
2016-01-08 15:32:07.8756 INFO: FileManagement: COUNTRY begin load countries
2016-01-08 15:32:07.8946 INFO: FileManagement: COUNTRY load completed: 402
2016-01-08 15:32:07.9036 INFO: FileManagement: IOTA begin load database
2016-01-08 15:32:07.9066 INFO: SolarDataManagement: GEOMAGNETIC DATA (DGD) downloading from ftp://ftp.swpc.noaa.gov/pub/latest/DGD.txt
2016-01-08 15:32:07.9126 INFO: SolarDataManagement: GEOMAG data begin download
2016-01-08 15:32:07.9967 INFO: FileManagement: IOTA load database completed: 1178
2016-01-08 15:32:08.0087 INFO: FileManagement: Begin loading SotaDatabase
2016-01-08 15:32:08.0127 INFO: FileManagement: begin load text file C:\Users\g4poparrl.net\Google Drive\G4POP Log4OM\config\summitslist.csv
2016-01-08 15:32:08.0897 INFO: FileManagement: Text file load completed
2016-01-08 15:32:08.0937 INFO: FileManagement: SOTA Summits List (Date=04/01/2016)
2016-01-08 15:32:08.0977 INFO: FileManagement: SummitCode,AssociationName,RegionName,SummitName,AltM,AltFt,GridRef1,GridRef2,Longitude,Latitude,Points,BonusPoints,ValidFrom,ValidTo,ActivationCount,ActivationDate,ActivationCall
2016-01-08 15:32:08.6271 INFO: FileManagement: begin load text file C:\Users\g4poparrl.net\Google Drive\G4POP Log4OM\config\SotaAssociations.csv
2016-01-08 15:32:08.6321 INFO: FileManagement: Text file load completed
2016-01-08 15:32:08.9273 INFO: FileManagement: SotaDatabase loaded
2016-01-08 15:32:08.9313 INFO: FileManagement: TUNE REMINDERS load start
2016-01-08 15:32:08.9523 INFO: FileManagement: TUNE REMINDERS load completed
2016-01-08 15:32:08.9563 INFO: FileManagement: Clublog begin load database
2016-01-08 15:32:09.1895 INFO: FileManagement: Clublog load database completed
2016-01-08 15:32:09.1945 INFO: FileManagement: SCL begin load unique callsign
2016-01-08 15:32:09.2315 INFO: FileManagement: SCL load completed: 4428
2016-01-08 15:32:09.2355 INFO: FileManagement: begin load RANKING
2016-01-08 15:32:09.2575 INFO: FileManagement: RANKING load completed
2016-01-08 15:32:09.2615 INFO: FileManagement: begin load RegExpFilters
2016-01-08 15:32:09.2665 INFO: FileManagement: RegExpFilters load completed Cluster
2016-01-08 15:32:09.2715 INFO: FileManagement: LOTW begin load from file C:\Users\g4poparrl.net\Google Drive\G4POP Log4OM\config\lotw.txt
2016-01-08 15:32:09.4207 INFO: Log4OMMainWindow: LOTW load from file completed
2016-01-08 15:32:09.4347 INFO: FileManagement: VIEW CONFIGURATION begin load for SmallQSO
2016-01-08 15:32:09.4507 INFO: FileManagement: VIEW CONFIGURATION load completed
2016-01-08 15:32:09.4537 INFO: FileManagement: VIEW CONFIGURATION begin load for SmallQSO
2016-01-08 15:32:09.4587 INFO: FileManagement: VIEW CONFIGURATION load completed
2016-01-08 15:32:09.4827 INFO: FileManagement: BAND PLAN begin load database for region 1 / 223
2016-01-08 15:32:09.4887 INFO: FileManagement: Bandplan loading user file: C:\Users\g4poparrl.net\Google Drive\G4POP Log4OM\config\bandplan_r1_user.xml
2016-01-08 15:32:09.5037 INFO: SolarDataManagement: GEOMAG download completed
2016-01-08 15:32:09.5087 INFO: FileManagement: BAND PLAN load database completed
2016-01-08 15:32:09.5097 INFO: SolarDataManagement: GEOMAGNETIC DATA (DGD) load from file completed
2016-01-08 15:32:09.5217 INFO: SolarDataManagement: GEOMAGNETIC DATA (DSD) downloading from ftp://ftp.swpc.noaa.gov/pub/latest/DSD.txt
2016-01-08 15:32:09.5277 INFO: SolarDataManagement: GEOMAG data begin download
2016-01-08 15:32:09.5407 INFO: WCFManagement: RunServices starting with path
2016-01-08 15:32:09.5618 INFO: WCFManagement: Opening
2016-01-08 15:32:09.8892 INFO: WCFManagement: Opened
2016-01-08 15:32:09.8932 INFO: WCFManagement: RunServices STARTED
2016-01-08 15:32:09.9132 INFO: TCPServer: Closing TCP Connection [RESET LISTENING SOCKET]...
2016-01-08 15:32:09.9242 INFO: TCPServer: Listening on port 8081
2016-01-08 15:32:09.9293 INFO: TCPServer: Executing C:\Users\g4poparrl.net\Google Drive\G4POP Log4OM\Log4OmCommunicator.exe TCPPORT:8081 HRDLOGUSER:G4POP HRDLOGUPCODE:f66b378865
2016-01-08 15:32:10.0073 INFO: Log4OMMainWindow: Starting omnirig CAT
2016-01-08 15:32:10.0113 INFO: OmniRigManagement: Starting OmniRig
2016-01-08 15:32:10.0293 INFO: SolarDataManagement: GEOMAG download completed
2016-01-08 15:32:10.0343 INFO: SolarDataManagement: GEOMAGNETIC DATA (DSD) load from file completed
2016-01-08 15:32:10.0413 INFO: SolarDataManagement: GEOMAGNETIC DATA (Predicted) downloading from ftp://ftp.swpc.noaa.gov/pub/latest/Predict.txt
2016-01-08 15:32:10.0453 INFO: SolarDataManagement: GEOMAG data begin download
2016-01-08 15:32:10.5500 INFO: SolarDataManagement: GEOMAG download completed
2016-01-08 15:32:10.5575 INFO: SolarDataManagement: GEOMAGNETIC DATA (Predicted) load from file completed
2016-01-08 15:32:11.0364 INFO: Log4OMMainWindow: Executing preload auto-start sequence
2016-01-08 15:32:11.0404 INFO: Log4OMMainWindow: Preload auto-start sequence completed
2016-01-08 15:32:11.1337 INFO: Log4OMMainWindow: Connecting to database...
2016-01-08 15:32:11.1392 INFO: DatabaseManagement: *** Connecting to Database SqlLite ***
2016-01-08 15:32:11.1462 INFO: DatabaseManagement: SQLITE Begin Connection Validation
2016-01-08 15:32:11.1602 INFO: DatabaseManagement: SQLITE Connection Valid
2016-01-08 15:32:11.1637 INFO: DatabaseManagement: *** Connected to database C:\Users\g4poparrl.net\Google Drive\Logbooks\G4POP.SQLite ***
2016-01-08 15:32:11.1867 INFO: SQLiteDatabaseManagement: Recalculating statistics...
2016-01-08 15:32:11.2598 INFO: #=qmUSkZ9xHFf4FrO9gOzN1wKiVd06XCBWweozxyQtBA4A=: Statistics recalculated and refreshed
2016-01-08 15:32:11.2733 INFO: Log4OMMainWindow: Database connected At this point my window is fully drawn

4/5 seconds

I just tested the load/draw ime with HRD (Logbook only) and it was 8 seconds on the same computer - It also loads lots of data at runtime - But then HRD is 93MB in size

[G4DWV]

Okay, thanks for your help Terry.

BTW, the last time in your log, viz Log4OMMainWindow: Database connected, does not appear anywhere in mine. It is not on the computer that I use for radio, but there is a log/database. Is this of any significance? If it is not, there's no need to spend any of your valuable time on it.

Functionality does not seem to be affected at all, v1.24 of Log4OM.

[IW3HMH]

Terry is using an Alpha release, where form names are not encrypted.
This has been made to fix the issue with form placement not kept between different versions.
This is why you cannot find that string in your log.

In Log4OM 1.25 Windows placement will be correctly saved, and will be kept when V. 1.26 will be available.
Unfortunately the transition from 1.24 to 1.25 will still be affected by this issue.

back to your original question, as Terry correctly said, there are a lot of initializations that are made by Log4OM during startup.
We load all data structures, recalculate statistics, load all user/system config files, load and parse the log, execute scheduled updates if something is getting older and so on.
Many of those things are made in a separate thread, but other things are loaded and used in the main user interface, so this could slow up the startup.

[G4DWV]

Thanks Daniele.