21 replies to this topic

[daniel_r]

Hello Boki,

when I create a combobox item in a TNextInspector I can't use the scrollbar of the dropdown-list. Every time I click the arrows or try to drag the handle the combobox closes as I had clicked outside the list.

What can I do?

Perhaps this information might help: Whenever the mouse cursor is over the scrollbar the caret of the input field stops to blink. At all other positions (anywhere on the screen or in the dropdown-list) it blinks again.


Regards,
Daniel

[daniel_r]

Doesn't anyone else have this problem?

[daniel_r]

Shell I provide a demo application?

[Boki (Berg)]

Hello Daniel,

Please sorry for delay, I will check for this problem and this will be fixed in next v3.3.4

regards

[daniel_r]

Hello Boki,

if you find a solution, please post it here ASAP (Unless you plan to release the new version in the next days) My program is pretty useless without a (working) inspector component. :cry:

Regards,
Daniel

[daniel_r]

Any news?

[Boki (Berg)]

Hello,

New v3.3.4 will be released on January 10. I am full speed working on it.

regards

[daniel_r]

Hello Boki,

from where can I download the new version?

Regards,
Daniel

[Boki (Berg)]

Hello,

New version is out in 2 days, defintely, but I still can't produce your bug. Can you please compile one small exe demo and send it to me inside zip archive to my mail.

regards

[daniel_r]

Done.

[daniel_r]

Hello Boki,

since 3.3.4 has the same problem I made a little investigation of my own. Here some things I've noticed. I've used the TNxComboBox, since it has exactly the same problem.

In TNxPopupControl.MouseUp the line

CODE

if PtInRect(ClientRect, Point(X, Y)) then AcquireValue(X, Y)

 else if DropMode = dmOpen then ClosePopup;

is always wrong when I click on the scrollbar, because ...
ClientWidth = 100
Width = 121 (because of the scrollbar which normally counts as non-client)
so the popup gets closed every time I click on the scrollbar, but I think that's how it should be, since the scrollbars are outside of the client area. I wonder how this code could ever work on other systems.

Anyway, if I change this code to respect the total width of the control the popup get's still closed, but additionally the items gets selected. (As I had clicked on the item to the left of the cursor) There seem to be further width vs. client-width conflicts.


Additionally, I detected why the combobox caret stops blinking while the cursor is hovering over the scrollbar: For an unknown reason the CMMouseEnter and CMMouseLeave events are called alternating and very fast during that time.
It seems almost that CMMouseEnter triggers the call of CMMouseLeave and vice versa. (I added a beep-call in CMMouseLeave and holding the cursor over the scrollbar for just a second has caused so many beeps my system froze for about 10 seconds )

Hope that helps.


Regards,
Daniel

[daniel_r]

Hello Boki,

After further investigation, it seems that the continuous SetCapture - ReleaseCapture calls are the problem, not any (client)width miscalculations.
Perhaps my Delphi installation is flawed or it's some other way my fault.

Anyhow, do you see any way to solve this problem?

Regards,
Daniel

[hpoulsen47]

I have the same problem with scrollbars in comboboxItems in NextInspector, but only when I use NextInspector under Delphi2006.

So when will there be an official release of NextInspector for Delphi 2006

I have just updatet from 3.3.3 to 3.3.4 but the problem it still there

Henrik.

[daniel_r]

Yes, now I am convinced, that this problem relates to Delphi 2006.

It seems that OnMouseLeave is fired, as soon as the cursor leaves the client area.
But OnMouseEnter is fired, as soon as the cursor enters the bounding area.

In earlier version, always the the bounding area was taken into account.

I guess the only solution would be using WM_ACTIVATE, but that would require wrapping the drop-down list and the edit field into a single control, otherwise the edit field cannot be focused while working with the list without either one receiving a "deactivate" message.

Regards,
Daniel

[bwells2004]

Is there a quick fix for this issue? I'm dead in the water without it. Can someone please help.

[Markus]

Did you try changing

CODE

if DropMode = dmOpen then SetCapture(Handle);

to

CODE

if DropMode = dmOpen then SetCaptureControl(Self);

in TNxPopupControl.CMMouseLeave?

Delphi applications/components should use SetCaptureControl() instead of SetCapture(). I'm wondering why their usage is mixed in NxInspector...

PS: The Scrollbar is drawn in WMNCPaint(), so it shouldn't belong to the component's client rect (no matter what Delphi version you're using).

[daniel_r]

Did you try changing

Yes, it didn't make a difference.

so it shouldn't belong to the component's client rect

Did I say anything different?

Anyway, that's exactly the problem. In D2006 CMMouseLeave gets called if the cursor leaves the client area. If you click on the scrollbar the list handles the mouse message, since all mouse messages are captured and the click message never reaches the scrollbar.

The list calculates that the click position is outside its client area and closes the popup. Since it assumes that any click outside the client area is either handled by the scrollbar or occours from a click anywhere on the screen.

But since mouse message capturing already starts when the cursor is over the scrollbar, the scrollbar can never process the click message and instead the list control assumes the user has clicked elsewhere on the screen.


Regards,
Daniel

[abraham_ll]

I have exactly the same problem.
Any fixes?

[Boki (Berg)]

Hello,

I am working on it. I will put one {$IFDEF} for Delphi 2006 version.

regards

[daniel_r]

Hello Boki,

sorry if I'm nagging, but is there any hope, that comboboxes in D2006 will work again soon?

Regards,
Daniel