I've compiled it for PPC Arm, May I know what device did you try it on?
Nobody else mentioned that they had a problem with the scrollbox of the
HScrollBox in any of the forums. So it might just be Isolated on my device.
I didn't just think that the mouse events are supported on the scrollbar,
but rather I'm sure that they are supported, because it's in both the .NET
Framework SDK and the .NET Compact Framework Help file that the mouse events
MouseDown, MouseMove and the MouseUp are supported in the .NET Compact
Framework. Those mouse events were inherited from System.Windows.Forms.Control
control class. It is my belief (and Jonathan had also mentioned it on his
thread) that .NET CF may have a bug and that the said mouse events and even
the Click system event are not being triggered on the HScrollBar control.
The reason why i'm resorting to using the said mouse events is to create an
alternate Scroll event, The reason why I want to create an alternate scroll
event is because the Scroll event is not supported in .NET CF. The reason why
I want to handle the Scroll event is because when I scroll the scrollbox of
the HScrollBar and release it, it always returns to the left most end and the
HScrollBar.Value always returns to the HScrollBar.Minimum. Is there a way to
capture the mouse event before it gets sent down to the control that is
occupying that area.
Thanks for the suggestion, but I've already tried compiling it bare, with
only the HScrollBar control and the minimum required code just to check the
HScrollBar.Value and to wire a simple mouse event to that control, and it
still wouldn't work, but if I try both the bare code and the code that I'm
using for my project and compiled it for desktop PC, everything works. If you
have any other suggestions, I'd be more than happy to try it out. If not, as
a final solution I might create an alternate HScrollBar deriving from either
the ScrollBar base control class or the Control control class itself. I
think, when they created the .NET CF version and derived the ScrollBar base
control class, from the Control control class, they might have overriden
those event handlers and forgot to call its base event handler, which might
explain why even if we wire event handlers to those events it gets blocked by
the overriden event handlers which in turn fails to call its base event
handler, hence no other event handlers are processed.