v1.802

jksjks
in Software release information

From the CHANGE_LOG file:

v1.802 February 7, 2025

  Added support for multiple iframe instances, up to 16. (thanks VK3KHZ)

    Admin > Extensions > iframe has a new button called "populate with standard entries" which

    will add 6 new iframe entries in addition to the new "DX spots" default added last release.

    They are: solar conditions, K-index, HF propagation, lightning map, and aurora.


 Fixed bug preventing change of proxy host name in certain cases.


nitroengineTremolatYogicatHB9TMCbensonG4ZFE

Comments

  • jimjackiijimjackii

    Thank you for the iframe options.

    I wanted to customise the Part 7 Solar Condition (solar cond) for me, but there was a problem.

    The default setting is a window with 175 x 555 with HTML code:

    <center><a href="//www.hamqsl.com/solar.html" title="Click to add Solar-Terrestrial Data to your website!" target="_blank"><img src="//www.hamqsl.com/solarn0nbh.php"></a></center>

    I have set the HTML code for another panel with the following HTM code:

    <center><a href="//www.hamqsl.com/solar.html" title="Click to add Solar-Terrestrial Data to your website!" target="_blank"><img src="//www.hamqsl.com/solar101vhf.php"></a></center>

    Change Upright to landscape - solarn0nbh.php -> solar101vhf.php.

    However, I had forgotten to adjust the window size.

    This is then displayed like this:

    kiwi_solar_cond_panel.jpg


    Now I can no longer reset the settings. No matter what I set and save now, it always stays with this display. Even a "Clear instance" and "Populate with standard entries" does not help.

    I have cleared the browser cache (on different computers) and restarted KiwiServer - tried several times, but nothing changes in the display.

    Regards, Steffen

  • jksjks

    I saw the problem exactly once. Then I couldn't get it to reoccur. It works as expected now. So probably some strange set of conditions that is causing a problem.

    If possible I'd really like to connect as admin to your system and take a look.

  • jimjackiijimjackii

    I have sent you an email with the login details.

  • jksjks

    So the problem was that on the admin iframe page you had two instances set to the same "extension menu entry" name. This is not a problem on the iframe page, because the two are distinguished by the instance number (0-15).

    But on a user connection it means only the first one encountered will be included in the extension menu. Such that you don't get two entries with the same name (no name duplication allowed). So when you were changing the width/height parameters for one in on the iframe page it may or may not have appeared to change the one the user page was viewing.

    On your Kiwi I gave them different menu names: solar-h and solar-h to distinguish the horizontal and vertical layout of the image. So I don't think there is actually a bug here. Except that on the admin page I could flag a menu name as being in use when you try and enter it I suppose.

  • jimjackiijimjackii

    Thank you for solving the problem.

    I have understood that. I didn't realise or didn't notice that there were 2 entries with the same name. I hadn't created them directly, they were probably the result of my experimenting.

    The warning about 2 identical entries might be a good idea.

    Regards, Steffen

  • jksjks

    I should also mention that there is a related bug: You can enter up to 16 instances in the admin interface. But only the first 8 appear in the extension menu. This has been fixed for the next release.

  • bensonbenson

    Nice addition to have multiple iframe instances available. In order to "Allow iframe to tune Kiwi" what is required to indicate what entries are frequencies on html pages?

    Tks, Ben

  • jksjks
    edited February 11

    Here's an example you can put in the HTML section of an iframe instance. Be sure to check the "Allow iframe to tune Kiwi" checkbox. So the onclick event just calls tune() which uses the built-in postMessage function to send a tuning string to the server. That string has the same format as what's used in the "f=..." URL parameter. Except that it also allows spaces for better readability. So you can set freq, passband, mode and zoom.

    The way I made the sk6aw.net spot frequencies clickable was to have spots.kiwisdr.com act as a MITM proxy and inject the onclick=... stuff into the reply HTML from sk6aw.net

       <!DOCTYPE html>
   <html>
   <body>
      <style>
        a.freq {
         color: yellow;
         cursor: pointer;
        }
      </style>
       
      <script type="text/javascript">
        function tune(msg) { parent.postMessage(msg, '*'); }
      </script>
       
      <a class="freq" onclick="tune('7020 cw')">7020 cw</a><br>
      <a class="freq" onclick="tune('10136 usb')">10136 usb</a><br>
      <a class="freq" onclick="tune('14106 usb')">14106 usb</a><br>
   </body>
   </html>


  • jksjks

    The fun just never stops, lol.

    A couple systems running Debian 8 had the v1.801/802 update fail when using the new binary update scheme. Some sort of shared library problem. Wasn't an issue when compiled from sources. So for now I have disabled binary updates for Debian 8 until I can figure out what's going on.

Sign In or Register to comment.