Unexpected redraw and delayed response to action & unexpected behavior

[AntonyD]

1) Set internally DPI=120 (Configuration-Options-Font)

2) Open Search dialog

3) Activate Plugins tab && put in this section 2 plugins. Even any type of "tc" will suit for reproducing of this bug.

After that we can notice that two Buttons are active below all fields. That's a reasonable action.
BUT also there is an "active" the 'spinbox'? or how I should call this element? Which is responsible for changing
the rules order. You may ask me - why I put 'active' word in a quotation marks?
Because Immediately after adding these two fields, this element will not actually be active. It cannot be used
as intended. And this is actually the first problem.
Next - I can't figure out - HOW am I supposed to guess - which rule above which I can move with this element?
In other programs, where the same logic of displaying a similar control element existed - I understood it because
the ACTIVE row for moving was ALWAYS highlighted. And there was ALWAYS some active row. Here, it's all different.
After adding two rules - none of the rows becomes active. There is no highlighting of the ENTIRE line in principle.
I don't understand which line can be moved at a given time and where.
But this is not a bug yet - this is an unexpected behavior about this control.

4) Now (if you can figure out HOW to activate the desired line=rule), use this control and try to move the rule
down or raise it up. And you should observe an unexpected redrawing of the entire shape.
With the addition of unexpected scrollbars in both directions.
https://www.upload.ee/files/18141591/record_2025_05_26_14_03_11_642.mp4.html

Well: plus in general the process of redrawing UI-elements on this form looks very bad. Does everyone notice this?
ALTHOUGH it would seem - why are all the UI-fields being redrawn there at all? We only change the text inside, don't we?

P.S.
Bug is repro on TC x64 and NOT repro on TC x86

[petermad]

It works OK, the order just cannot be cycled when you reach the top or bottom - that is: if the text-cursor is in the first value field only the arrow-down works, and if the text-curs0r is in the last Value field only the arrow-up works. If the are 3 rows and the cursor is in the middle Value field, then both arrow-up and arrow-down works - and have a little patience for the text-cursor to reappear after the order is changed. In your video after every movement of the rows, you can only see a glimpse of the text-cursor in the active row, because you immediately click again.

[ghisler(Author)]

Wow, why is it so slow on your system? Is this over a remote connection?

[AntonyD]

no - it's a pure local laptop. I've had this program behavior for a very long time. But I didn't try to focus on it.
by the way, it still looks fast on a white background. on the more beloved gray, everything is still more deplorable and slower to draw.

[AntonyD]

2petermad
Okay, I understand that, but I tried to describe the behavior from other programs where a similar operation is performed.
1) which does not have such graphic redrawing lags
2) it would probably be more accurate to say that there is no redrawing at all - the values in the fields just change instantly.
3) there is a GLOBALLY visible row selection, which greatly improves the overall usability of such a list control.

[ghisler(Author)]

The problem is that I completely clear the comboboxes and replace their content when swapping, which seems to cause a lot of redrawing events. The solution is simple: I will disable redrawing while swapping the columns, and only redraw them when done.

[white]

The problem is that I completely clear the comboboxes and replace their content when swapping, which seems to cause a lot of redrawing events. The solution is simple: I will disable redrawing while swapping the columns, and only redraw them when done.

Can't you simply swap the position of controls (swap top property) and adjust your array of rows, or something like that?

[AntonyD]

2ghisler(Author)
it's good that a solution has probably been found (we'll check on the next build), but why does everything else go unnoticed?
why is there no highlighting of the really active ENTIRE row with the rule?
HOW should a user navigate at the moment when he wants to move something somewhere, but does not understand: what and about what?
Why doesn't at least the first line IMMEDIATELY become active/highlighted as soon as we add the first rule through the button???

[AntonyD]

2white
I wrote almost the same thing, but before I could send it, I received a message about your post)))
And I decided to remove the repeats from mine)) Great job, colleague!

[ghisler(Author)]

Can't you simply swap the position of controls

No, because it also changes the tab order.

[AntonyD]

But the command to replace "TabOrder" in programming also seems to exist. And according to the sum of the actions - coordinate change + TabOrder change = we will get a much more responsive form of dialogue than with the idea of completely deleting and re-forming new text content in each combo box + also selecting the necessary elements from the lists + changing values in the free editing fields.

[ghisler(Author)]

This should be fixed in RC4, please test it!

27.05.25 Fixed: Find files, Plugins tab: disable redrawing while sorting columns (32/64)

[AntonyD]

https://www.upload.ee/files/18145315/record_2025_05_27_14_11_43_562.mp4.html

just look at this and pls say - does it look like as a fixed? IMHO no.
Now everything is especially bad when adding a new line with a rule.

[ghisler(Author)]

I cannot reproduce the problem with scrollbars. When they don't show up, it is much faster, don't you agree?

[AntonyD]

I don't know what speed is being referred to, because after I closed the search dialog form,
recording a video for you in which I indicated that everything had gotten WORSE than it was,
now—after trying to open it again—I experienced a TOTAL rendering delay of 7 seconds before
all these rule's fields finally appeared on the form.
That is, everything has become much, much worse and slower than it was.