ALE_2G Bug [fixed in v1.801]

DK9FIDK9FI
edited December 2024 in Problems Now Fixed

Dear all,

since some months there are problems with the ALE scan function (/?ext=ale,#,scan:0.75).

If this ption is running all buttoms on the left command field cannot be changed at all and you also cannot make a copy of received data from the center monitor field.

You must push STOP and start SCAN again.

Is this wanted or simply a bug ?

73,

Bernd DK9FI

Comments

  • jksjks
    edited December 2024

    I don't see this behavior at all. When a single frequency is specified after ext=ale that frequency is set but scanning does not begin until the scan button is pressed. I believed it has always worked this way. If you had used the name of the scan menu instead of a frequency, like "Ham" or "MARS", then scanning starts right away. Same if you give a list of your own frequencies separated by commas.

    At no point did any of the buttons not work for me. And I don't know what you mean by "cannot make a copy of received data from the center monitor field". Do you mean you can't cut and paste the text?

  • DK9FIDK9FI

    Hi,

    thanks for the answer.

    "Do you mean you can't cut and paste the text?"

    yes I cannot select and copy during the scan.

    or

    when it is running with my own frequencies I cannot change the frequency range e.g. ">10 MHz" or change the log time and some other options in this window.

    Everything is blocked.

  • jksjks

    Oh, while a scan is active.

    Yes, you won't be able to interact with the user interface while a scan is in progress because of how HTML/Javascript works. While scanning the frequency box is updated. And that will take away focus from whatever else you are trying to do: push a button, make a text selection etc. So you have to stop the scan first.

    This is just intrinsic to how the interface currently works.

  • DK9FIDK9FI

    ok,

    I understand but why is this effective since approx.February 2024 ?

    Last year there was no blocking at all during running scan...

    Bernd

  • jksjks

    I don't believe that's correct.

  • DK9FIDK9FI

    its your opinon right now, its my experience during last 2 years or so

  • jksjks
    edited December 2024

    Alright, I see what's gone wrong here.

    I found a very old version of the code to compare against. There was code long ago to prevent updates to the frequency field from taking UI focus away during ALE scanning. Looks like that feature was lost during a major rewrite of the code. So I have put that feature back and it now works as you had remembered it. This fix will be available in v1.801 when it is released, probably sometime in January.

    Apologies for my faulty memory. It gets worse every year!

  • DK9FIDK9FI

    no problem,

    many thanks for great help!

    If I have some ideas about improvements, must I write here in the forum or directly to you by e-mail ?

    A Happy New Year!

    Bernd

  • jksjks
    edited December 2024

    Except for small changes and bug fixes I've given up on making major improvements to the code because it plays right into the hands of the Chinese cloners. There is simply no point anymore. I consider the Kiwi to be feature complete. Sales and support will continue. But personally I have moved on to other things..

Sign In or Register to comment.