Inspector Bar: problems with AdvColorSelector

VCL TMS VCL UI Pack
1

Hi Bruno,

I'm afraid I have another problem with the Inspector Bar... This time I am using an AdvColorSelector linked to the Inspector Bar via a TFormControlInspectorEditLink. The problem here is that the GetEditorValue event of the EditLink fires before the Select event of the ColorSelector. This means that I can't get the new selected color for the currently selected InspectorItem. 
As with the FontDialog issue from last week, the problem does not occur in a simple test app, only in my main app. I have traced the difference down to the TAdvCustomSelector.HideDropDown which sets the FDropDownWindow.Visible to false. In the test app that is the end of the line, execution passes back up through the stack and on to set the SelectedColor. However in my main app setting the visible false triggers the focus to move away from the Item and this in turn triggers the GetEditorValue. 
I can't find any obvious differences between the configuration of the InspectorBar, ColorSelector and EditLink in the main and test app though clearly something is messing one up.
Do you have any ideas as to why this might happen - or how I can prevent the focus change happening prematurely?

2

I have no idea here how OnGetEditorValue is triggered before the selected color is set.

I will really need more details, i.e. a sample source app with which we can reproduce this here.
3

Hi Bruno,

I really tried to make a sample program that would do what happens in my main app but without any success. It turns out that the fix you proposed for the similar pfFont problem last week does not work for me either so there is something really weird happening somewhere in the bowels of my (probably very bad) code. 
I have created a fix that works for me - I use the GetEditorValue to store the current InspectorItem to a global variable and then trigger a 10ms timer to allow the selectedcolor to be set. 

Anyway, thanks for trying to help and sorry I broke your otherwise excellent component!

4

Ok, if you happen to see the problem again and can reproduce it, please send a project so we can investigate.