Shift+Ctrl+G does not focus the file in the Timeline if new Node is opened

[Tveloso]

This is pretty minor, but I thought I should report it anyway.

When using Shift+Ctrl+G from any other View, to go to the TimeLine View, if a different Timeline Node (from the last one used there) must be opened to satisfy the request, the file from the "source View" where the request was made does not get focused.  The correct Timeline Node is opened, but the first file in the resulting FileWindow is the one that's selected.

If we return to the  "source View", and press  Shift+Ctrl+G again, the correct file is now focused in the TimeLine.  Even if we select another file, in the "source View", that's in the "current TimeLine Node", the correct File gets focused.  But if the selected file in the  "source View", requires that a new Timeline Node be opened, then the issues happens again (the first File in the newly opened Timeline Node is focused, instead of the file from which the  Shift+Ctrl+G request was made).

[Mario]

Timing issue?

[Tveloso]

Mario, this seems to be consistent though.

Whenever the date of the file where Shift+Ctrl+G is pressed, differs from the "current Node" in the timeline, that file is not focused when the Timeline View opens.

The correct file is focused only when "current Node" in the Timeline View, happens to be the same as the date of the file where Shift+Ctrl+G was pressed.

[Mario]

Switching to the Timeline View and opening a node and then selecting a specific image burns a lot of CPU cycles, and a lot of Windows code is involved for opening windows, focus management etc.

My impression was that this is a timing issue and that IMatch somehow tries to focus a file while the timeline node is still loading (and the image is not there yet). This will be dependent on the database size, computer performance etc. I will look into this for a future IMatch release.

[Mario]

Fixed for IMatch 2023.
I have added a delay when selecting the file and a extra check for monitoring the File Window for completing the load operation. This should do the trick.

I could reproduce this with very large databases or by slowing down IMatch (simulating a somewhat slower computer). This glitch was a timing issue as I'd anticipated.

[Tveloso]

That's great!

Thank you so much Mario.