NANY 2013 Release: Customizable Remote Administration Panel (CRAP)

[hamradio]

Hey there, I've been using 2.1.0 build 73 RC1 since my previous message in my work setting and those 2 issues appear to be fixed indeed

I noticed that the about box still says "2.1.0 build 72" but the version number in the executable properties is correct (2.1.0.73).
Didn't run into any problem with it, though I must admit I didn't re-test every feature again.

-ConstanceJill (July 07, 2024, 06:00 AM)

Thanks, I didn't get the value changed in one spot resulting in it displaying it wrong. Will be simple enough to fix for either the rc version or next release version.

[ConstanceJill]

Hello!

I think I found a bug (in version 2.1.0 build 73 beta RC1) : after pressing F2 to open the layout editor, if some of the buttons in the layout are disabled, and the user selects a button in the list, then clicks "Move left" or "Move right" to change that button's position, then the number of lines that this button is moved up or down isn't 1 for each click, but seems to be affected by how many disabled buttons exist in the direction which the selected button is being moved towards.

Additional information: I can't reproduce this with either version 2.0.6 or 2.1.0 build 25 beta, which I have kept on hand, so the problem must have been introduced since then.

Edited again: it may require to have more than 2 disabled buttons for the issue to happen.

[hamradio]

Hello!

I think I found a bug (in version 2.1.0 build 73 beta RC1) : after pressing F2 to open the layout editor, if some of the buttons in the layout are disabled, and the user selects a button in the list, then clicks "Move left" or "Move right" to change that button's position, then the number of lines that this button is moved up or down isn't 1 for each click, but seems to be affected by how many disabled buttons exist in the direction which the selected button is being moved towards.

Additional information: I can't reproduce this with either version 2.0.6 or 2.1.0 build 25 beta, which I have kept on hand, so the problem must have been introduced since then.

Edited again: it may require to have more than 2 disabled buttons for the issue to happen.

-ConstanceJill (August 27, 2024, 09:59 AM)

Okay now that my busy August + Early September is over I am going to take a look. I haven't forgot just been busy.

Edit: Think I found the piece of misbehaving code and should be fixed locally.

The function should've only been skipping the disabled entries for faster moving...

[hamradio]

So the misbehaving code should be fixed in the uploaded beta version to where it stops at the first enabled entry from the selected item in either direction and only moves it that many times to account for the disabled entries if any. If previous/next is enabled it should only move one time else move the required times to skip the disabled entries while taking into account the start/end of the layout list. Let me know if it still misbehaves other than what I just described. I think it should be smart on moving items around the disabled entries of the layout list instead of just moving it one time but if you think it should only ever move any entry one time I can fix it back to that method still...

Uploaded RC#2 to the beta page.

[ConstanceJill]

Thanks, I'll start using it and, as usual, will let you know if I find any issue or possibility of improvement