Unexpected redraw and delayed response to action & unexpected behavior

[petermad]

2AntonyD
It looks like the buttons "More rules" and "Fewer rules" are not put down under the new added rule, until it is fully rendered. It would be better if those buttons were moved down before rendering the added rule or if the buttons were hidden while the added rule is rendered.

[ghisler(Author)]

As I have explained above, I have ONLY reduced the flickering when changing the sort order. I haven't changed anything when adding rules or changing a value. That would require major internal changes which could break a lot of other things, and doesn't cause a major slowdown. I'm therefore postponig this to a later version, sorry.

[white]

2ghisler(Author)
Can I get an answer to this:

And how is it supposed to work? Moving a row up or down with the mouse is only possible when all rows fit in the dialog?

I still don't know whether this is intentional or not.

And are you going to update the help text as suggested?

[petermad]

Moving a row up or down with the mouse is only possible when all rows fit in the dialog

That is problematic, escpcially because the user cannot change the height of that part of the dialog, to work around the problem.

[white]

That is problematic, escpcially because the user cannot change the height of that part of the dialog, to work around the problem.

And there is a high chance the user doesn't know about the alternative of using the keyboard, even if the user reads the help page. Because of the awkward placement of the help text.

[ghisler(Author)]

Moving a row up or down with the mouse is only possible when all rows fit in the dialog?

You either need to use the keyboard, or click in a row and then scroll down to see the up/down button.

[white]

Moving a row up or down with the mouse is only possible when all rows fit in the dialog?

You either need to use the keyboard, or click in a row and then scroll down to see the up/down button.

The up/down button is disabled and users don't know they can use the keyboard.

[petermad]

The up/down button is disabled

Exactly

[AntonyD]

If I'm seeing this correctly, there is even a super bug related to the ability to move rules using the Ctrl+UP/DOWN combination.

Create two consecutive different rules that use Boolean logic (YES/NO). Activate the first rule and try to move it down to make it the second.
So, my second rule moves to the first place instead of the former first rule AND additionally changes the Boolean state value.
If it was - YES, it will become - NO and vice versa... This may not happen the first time - try to raise/lower it a couple of times in a row.
And it will definitely work.
https://www.upload.ee/files/18188092/record_2025_06_08_16_03_04_804.mp4.html

I still completely do not understand the logic of selecting a rule/row of UI-objects.
I specifically highlighted the Nth cell from the "Plugin:" column and with the Ctrl+UP/DOWN combination I wanted to move it down,
making it N+1 in order. And yes - this action will be performed, but for some reason the activation focus shifts from this cell to a cell
in the "Value:" column. And it seems that the entire row (the entire rule) will still be highlighted - the one I am working with.
BUT since there is no CONTINUOUS selection\highlighting of these objects in the row, I am only focused on the selection of ONE cell
among them. And this selection jumps around as it pleases. From one column to another...

[ghisler(Author)]

2petermad
The up/down button only gets enabled when there is a mouse move event over the button. This is done because Windows 11 hides the up/down arrows on the scrollbar when enabled and not hovering above it.

2AntonyD
This only happens when using Ctrl+Up/Down. It looks like the key combination gets passed down to the combobox and switches the item. I will try setting the key to zero to prevent that.

When switching through rows, the focus will ALWAYS be put on the value column (edit box or combobox).

[white]

The up/down button only gets enabled when there is a mouse move event over the button.

As said, only when all rows fit on screen, otherwise the button doesn't get enabled.

Of course implementing it the same way as in the custom column editor, would be much better..
(And being able to use Ctrl+Up/Down in the custom column editor too instead of only Ctrl+PgUp/PgDn, would add to the consistency and ease of use.)

[petermad]

As said, only when all rows fit on screen, otherwise the button doesn't get enabled.

Confirmed - Windows 7 and 10.

[AntonyD]

....
When switching through rows, the focus will ALWAYS be put on the value column (edit box or combobox).

But the problem is that switching between rows does NOT mean 100% that I am trying to enter the correct values.
I could just as likely switch to another row altogether – to change the plugin ITSELF – and thus all the related objects
to the right and their values.
That is, there is no 100% correlation with the fact that we need to get there and only there.
Maybe we should give the user the option to choose where they want to go?
please remove this mandatory "putting".

[ghisler(Author)]

I think the only solution is to move the up/down button below the Help button outside if the scroll box, so I will try that.

[AntonyD]

I think the only solution is to move the up/down button below the Help button outside if the scroll box, so I will try that.

I hope you meant to say that you will move the ENTIRE combination of buttons and "arrows" OUTSIDE the area with the rules?
ALL three objects - the add/remove buttons and the up/down button - should then be completely placed OUTSIDE
the frame with the objects forming the rules!

like that:
https://i.ibb.co/Kc1CjLN8/2025-06-10-151957.png