Am i correct that what you are saying is slow is when you select a clip, it is slow to display it's details in the memo panel?
___________________________
Yes.
And could you be more specific about how slow is slow?
___________________________
Let's say I navigate the
Grid pane using the
Up/Down cursor keys. (This is how I usually do it.)
If the cursor is (say) being moved
Up, it will frequently halt/pause - even though the cursor
Up key has been pressed again once or even twice or thrice - for about 1 or 2 sec. Then the cursor will rapidly "catch up" the number of
Up key depressions it has missed, missing out displaying (or maybe only momentarily displaying) any of the intervening clips in the
Memo pane, until it is resting on and displaying in the
Memo pane the latest clip the cursor was moved to.
Similarly if the cursor is (say) being moved
Down.
It's like a buffer is waiting to be initialised/loaded with the data, in some circumstances. It's not consistent for every clip or clip type, and I can't see that the clip contents necessarily makes any difference to this behaviour.
This behaviour seems to be consistent and repeatable. One can repeat the movement of the cursor over the same clips in the
Grid pane, and pretty much the same behaviour is repeated - as near as I can see, at any rate. So it's not as though a buffer array has been refreshed and is faster the second time around.
Whilst the cursor is in a "paused" state, the
Memo pane display does not change (is not updated)
So that also answers the last part of your Q:
And here is another thing that would provide a clue -- if you find a clip -- let's say one without an image -- that is slow to load, is it always slow to load even if you keep alternating between selecting it and another clip? or is it only slow the first time you select it but not the repeat times soon after?
That is, it's equally slow the second time - So it's not as though a buffer array has been refreshed and is faster the second time.
And here's another odd thing:If I start off at the bottom of the
Grid, at the "latest" clip and that row
highlighted, and move the
Up cursor several rows up the
Grid, then that clip/row is
highlighted in the
Grid and will eventually be displayed (after the delay) in the
Memo pane.
If I then press
Ctrl+End, the cursor does not - as one would expect - go to the last clip in the
Grid, but remains where it was.
However, if I then press the
Up key, the highlight immediately appears in the penultimate clip row, so it must have been logically pointing at the
last clip position
before the
Up key was pressed, but was not being displayed as such.
This is such odd behaviour that I have wondered whether some other process - e.g., (say) my use of SQL in Virtual Folders - isn't somehow interfering in the cursor movement process. It looks as though some computation or a wait might be going on, causing the delays.
