||Re: Programmatically Adding An Event
||Thu, 6 Dec 2018 10:34:00 -0500
I did get them to line up but had to play with bitmapAlignment
leaving it at default they were unaligned and making them both
btmapAlignment = 1 // Left
seemed to align them. Something not quite right with alignment.
Maybe its dNavigation.dll that threw them off. I haven't played with them
since I used Resource Hacker to extract them.
Since I'm still using 2.62/2.80 in production cause 12 still isn't ready for
prime time, I prefer working with individual bitmaps.
"Mervyn Bick" wrote in message news:BeX$ITXjUHA.904@ip-AC1E04A7...
On 2018-12-06 4:46 PM, firstname.lastname@example.org wrote:
> OK that's right, he used PeekMessage(() to test the down state of the
> mouse button rather than using GetAsyncKeyState() to test the down state
> of the pushbutton.
> Not sure which way would have been better in this case. I'd like to think
> my way is better. LOL
> I did notice in my control that the downBitmap wasn't appearing when I
> defined that and the button didn't look like it was down.
> Possible adding UpdateWindow(oButton.hWnd) like is in Ronnie's code to the
> loop just before the sleep() will will cause that to repaint.
I haven't had time yet to dig too deeply but one thing I did notice was
that when I used the graphics for the pushbutons from dNavigation.dll
the two arrows didn't quite line up. When you use the individual .png
files they line up exactly.