开云体育

Hi Mike, you already reported something similar a few months ago. /g/qlog/message/472 So it's not a new behavior but just a change in behavior that may be caused by a hamlib upgrade.

Since the update to 0.41.0 I'm having a strange issue. Nothing was changed other than the update and now my FTDX10 does not change band and frequency correctly. When clicking on a spot and going from

Also, based on your postscript we are probably not setting the flags correctly on app open versus showing the sub-windows after the app is open. Cheers Kyle

Seems like this is an occurance of this issue: https://github.com/foldynl/QLog/issues/530. In macos QT, floating windows are considered utility windows which have the behaviour your video

Michael good morning, sorry for the delay, but I couldn't answer before. Today I find myself in the same situation that I had before the update to 0.41. Surely between the first email and today I had

I'm not sure I am following what the problem is. Can you walk me through what you are doing so I can reproduce it? As well as what you expect to happen? Thanks MIchael, AA5SH [email protected]>

Thank you!!!

You have installed TQSL because you chose to install the Flatpak version From the README file: *Flatpak* package is available via Flathub <https://flathub.org/apps/io.github.foldynl.QLog>. *The

Fresh install of Linux Mint 21.2 Victoria. All updates installed. Installed QLog 0.41.0 (Linux Flatpak) No issues. ? Runs great. However when I execute the program a TQSL icon is placed on my task

Thanks Michael great job, I opened all the windows and I'm really sorry to have to tell you that there are two commands left on the keyboard for the "clock" and "radio" windows. My system is: macbook

I fully understand and support this request. Just my two cents. -- ___ Slav, EI6KW, SP3RXO https://www.hamqth.com/ei6kw

Got it Ladislav! Adding my comments in your comments ?... - had to redownload all the source. git pull command didnt worked. I don't know how you did it, but I'm sure that git pull must definitely

I'm not the original requester, but I will give you my reasoning. I have always used UTC time for any of my amateur radio operations. That is the way I was taught to do it over 40 years ago. I don't,

Oh I totally get that, you don't want to make a program so flexible that they can break it 10 different ways.?I'm mostly am concerned with 24-hour time when it comes to logging. Specifically.?So

Great release, Thanks Ladislav!

I know for me it is I use my laptop for both Ham and work/personal. I just prefer for my normal life just to be 12 hour. But for ham everything is typically in 24hr, QSL, contests etc. So it is just

OK. Flexibility is a good thing but excessive flexibility is counterproductive. The average user isn't capable of foreseeing all the things they could break with various settings. I'm not talking

Let me add my comments: - had to redownload all the source. git pull command didnt worked. I don't know how you did it, but I'm sure that git pull must definitely work. When I create a release, I use

What I have learned in dealing with the larger audience, and also through my working career in computer support in large companies, is that everybody has their own preferences. There is no one "right"

Thanks for another great release!!! Just some notes: - had to redownload all the source. git pull command didnt worked. - for some reason had to download hamlib 4.5. QLog didnt liked the latest