great - thanks. Look forward to new version.
Вид для печати
great - thanks. Look forward to new version.
Quick question about maps...
When we use the maps in the WWLOc windows.. and zoom into each large grid (e.g. JN) the map becomes highly pixellated and "blocky". I know that is a limitation of the JPG file used to generate the map.
Is anyone else using a much higher resolution map successfully? Is it a case of simply copying another map file in?
That's right. An image is used for WW-locator window. Of course, I can use here "Map" window. But it's more difficult. :)Цитата:
Сообщение от Jim Smith
Yes, found a much higher res map (it's about 10MB) and it works just fine in the WWLoc window, and looks good.
It's finally time for manager base)))Цитата:
Сообщение от IK2XDE
This is how it should work. This button is for inserting current manager from the database into log window. Not for find manager for current station!
Yes correct,
the problem is that it doesn't verify the match of the call, and inserts any selected manager to any call... even if different.
There should be a check here, if the call doesn't match, don't enter the manager.
Thanks for the attention.
73 de IK2XDE Andrea
Цитата:
Сообщение от IK2XDE
The problem also persists in version 141
insert any manager to any call even if they don't match.
Another small problem, when I insert the call in the log window,
in the managers window it automatically positions itself on the first manager found ,
instead it should position itself on the last, most recent one.
Thanks for the attention.
73 de IK2XDE Andrea.
Hey Alexey,
Hope you're starting the year off well. I've got a little tech puzzle on my hands. Running LogHX version 3.0 build 742, and I'm noticing a quirk—stations I've worked in FT8 are showing up as gray dupes when I'm in FT4, and vice versa. Strange, right?
I've attached a test run with PY5EJ to give you a visual. The red arrows should point you to the head-scratcher. I don't have PY5EJ's station logged in 17M+FT4, but the system thinks otherwise. This happens with other stations as well.
Вложение 349400
Any insights on what I might be missing? Would appreciate your wizardry to unravel this mystery.
Cheers,
PY5XT - Eleandro
Вложение 349402Цитата:
Сообщение от PY5XT
Mode - MFSK, not FT4! All right!
There are two things here:
1. This highlighed QSO you shown in the picture is mode MFSK and submode FST4 not FT4
- FST4 = FST4 do not require the strict, independent time synchronization and phase locking of modes like EbNaut.
- FT4 = FT4 uses 4-GFSK modulation, transmission takes 4.48s with a 7.5s timing window.
2. by the ADIF standards (https://adif.org/314/ADIF_314.htm) for FT4 mode we should use mode MFSK submod FT4, as we can read in the chapter "III.B.9 Mode Enumeration"
Вложение 349414
I have this as standard for my log, do you think this is the issue I facing? I should use FT4 instead of MFSK? I didn't get how to fix.
Sorry
Check new 743 prerelease.Цитата:
Сообщение от IK2XDE
Well,Цитата:
Сообщение от RX4HX
now when I type the DXCall in the "QSO Entry" window,
in the manager window the cursor is positioned correctly on the last and most recent manager found.
But the INSERT button, that inserted the manager selected,
in the QSO entry window, in the Manager field, has disappeared
Now please
explain to us how works the new mask ......DXCALL - MANAGER - INSERT MANAGER...??
It doesn't seem to work...?
Previously, to insert a new manager it was enough to press the "INS" button,
a new row was created, and the new data was inserted.
(and I see that this one still works)
I take this opportunity to wish you and your family a good end and a good start to the year.
Happy New Year
As always, thank you for your continued commitment to log development, on behalf of all users.
Thank you.
73 de IK2XDE Andrea.
Цитата:
Сообщение от IK2XDE
ok, testing
v 743 31/12/23 09.26
INSERT MANAGER from the "manager windows" seem work,
bur I must type manually "manager" in the filed,
best solution is that take it automaticaly from database.
(the last and most recent).
Another problem is do not overwrite the manager field in the "QSO entry" window,
if for example there is already other information coming from qrz.com
Thanks.
73 de IK2XDE Andrea
Try now -Цитата:
Сообщение от IK2XDE
http://rx4hx.qrz.ru/files/loghx/prer..._build_743.exe
Happy New Year! :)
Great,Цитата:
Сообщение от RX4HX
now the manager field is automatically populated with the correct manager.
Now if I do "Insert manager" it inserts the manager into the "qso entry" window
only if the field is empty, it does not overwrite the information coming from qrz.com
(keep in mind that in general setup, I put "replace info" in the callbook management).
I think at this point you will have to give priorities,
first check on qrz.com and overwrite all the information, (if replace info is cheked)
then, if the user type "insert manager" , force his choice, an replace field with the manager chosen from the local database.
I hope I explained myself correctly.
Thank you.
73 de IK2XDE Andrea