Using Mint 19.2 64 bit. The grayline window has disappeared - I can barely see an outline of it but the window itself is transparent. There is a yellow dot next to grayline in the window menu that i don't remember seeing before. Did I do something? Everything looks OK in preferences.
73, Bill NZ0T
Any help?
Runing CQRLog & WSJT-X (up to date versions). Trying to figure out how to send logs to QRZ.com
Is there a button I am missing ?
Tim
From cqrlog - help:
Online log upload support
CQRLOG supports online log upload to HamQTH, ClubLog.org and HRDLOG.net
Uploading to others must be done with ADIF export and manual upload, I think.
--
Saku
OH1KH
Hi Bill!
Do you mean the window does not even have frames, or is it just there is no map inside the window frames?
The map is at /usr/share/cqrlog/images/BigEarth.bmp You should see it with any image viewer. Is it ok?
--
Saku
OH1KH
Hi Saku, thanks so much fro your reply.
The window is transparent and I barely see a border on the right side. When I move the cursor over the borders the movement arrows show up. But there is no map showing. It seems to be there but is not visible. I do see the map at /usr/share/cqrlog/images/BigEarth.bmp.
73, Bill NZ0T
Hi Bill!
Do you have very high resolution display card/monitor?
There are some comments about column positioning problems. Window scaling should be 1 (no higher). https://www.cqrlog.com/comment/7083#comment-7083
You could also test with different desktop themes.
I do not have that kind of monitor/display card so I can not make any tests or give more help but I have feeling this could be similar kind of problem.
--
Saku
OH1KH
Hi Saku,
Well I upgraded to Mint 19.2 from 19.1 a couple of weeks ago but everything was fine. Then a few days ago all of a sudden the grayline window went transparent. Other than installing the usual updates from Mint I have done nothing. On my other computer the grayline window works as it should so I think you are correct in that something has changed with my shack computer or monitor. I use the Mate desktop with both of them so I don't think it's the desktop. I need to find where I can adjust the window scaling and try that first.
73, Bill NZ0T
Saku,
I have two logs created inside my CQRLOG and i just discovered that the grayline window works in log 2. I do not use that log which was created to store FT4 contacts until LOTW accepted them. Log 1 is my main log and that is the one that the grayline window is transparent on. This makes no sense to me - same computer an monitor , same CQRLOG but grayline works on one log and not the other. Is there some preference somewhere that I may have changed by accident?
Well, I'm an idiot! I finally figured out that somehow, I have no idea how, the grayline window had been reduced all the way horizontally. Using ALT/TAB and cycling through the windows I discovered that the grayline window was there but minimized all the way horizontally. All I had to do was pull it back over and now all is OK.
Thanks again Saku and sorry to use so much bandwidth!
73, Bill NZ0T
H! Bill!
No problem!
There are some cases you do not even think when you search a reason. One is window that is so narrow that it is just a vertical line. Other is that it is rolled up so that you can see only the windows name and minimize/maximize/close buttons.
Then there is, at least with my LXDE desktop, a situation where you can drag whole window so down that you see just a small horizontal line of it at the bottom of display.
Those are easy to fix.
But then there has sometimes been a bug of wsjt-x where it places its window so high on display that window name and control buttons on top right corner can not be seen. I have not seen that with cqrlog, but it might be possible, too.
This causes also situation that you can not drag window. Minimize, Maximize, restore at the bottom of screen (at desktop manager) do not help.
So the window is stuck.
As with cqrlog and also wsjt-x program records all window sizes and positions this can make big problem if position or size is somehow corrupted. Problem continues after program has been started again.
Deleting wsjt-x config folder, or transferring all qsos to new log in cqrlog's case may be the only solution.
But these all are good knowledge, not waste of bandwidth!
Main thing is that you got your log working again.
--
Saku
OH1KH