Thread: Stupid buttons...

Ok, I'm trying to let the user move the button while they've clicked it and hold their mouse button down, I've tested the BN_SETFOCUS message (I needed something that was sent BEFORE the user depressed the mouse button) to see if it was sent, and it is. Also, I've checked hTemp to make sure it has the button's hWnd, and it does...and I can't for the life of me see the problem with the code. Someone help me out here, I'm racking my brains to death.

Code:

	case WM_COMMAND:
		switch(HIWORD(wParam))
		{
		case BN_SETFOCUS:
			bdrag = true;
			hTemp = (HWND)lParam;
			break;
		}
		return 0;
	case WM_LBUTTONUP:
		bdrag = false;
		return 0;
	case WM_MOUSEMOVE:
		if(bdrag == true)
			MoveWindow(hTemp, mX, mY, 80, 60, TRUE);
		return 0;

In theory that should work (yeah, and the mX and mY variables DO contain the right mouse info)

SetWindowPos() didn't make any difference (at least visibly, I guess. but that's where it all counts ), and the TRUE at the end of MoveWindow() invalidates the parent for you...

Hmm...this is a thinker.

Thanks for the help, though.

Just out of sheer (sp?) curiosity, maybe you should handle the WM_MOUSEDOWN instead of the BS_SETFOCUS. I don't really understand why you don't just use mousedown. I'd work with that message and see if that works.

Well, see for that it'd be a helluvalot more work. I'd have to keep check to see if the click was in any button on the window (there can be up to 50!) then figure out some odd way to get the handle.

This is for a windows designer that outputs pure API code, if you're wondering why anyone would want to do these things

ArgX! I might wind up with the MOUSEDOWN method, though...I sure hope it doesn't come to that.

Got it!

You have to give your button the BS_NOTIFY style in order for it to send BN_SETFOCUS msg to its parent.

I couldn't shake the damn button free from the mouse after that...

Originally posted by Ken Fitlike
Got it!

You have to give your button the BS_NOTIFY style in order for it to send BN_SETFOCUS msg to its parent.

I couldn't shake the damn button free from the mouse after that...

Why? I didn't know that was necessary. Well, anyway, good job Ken Fitlike!

You might find this handy.

for any child window that you want dragged around their parent, just handle the WM_LBUTTONDOWN message and do this:

SendMessage(childWindowHandle, 0xF012, 0, 0);

this does the default "window dragging behaviour"

hope this helps.
U.

You might find this handy....SendMessage(childWindowHandle, 0xF012, 0, 0);

Handy? Surely you jest. That's truly amazing! Where did you learn that one? Are there others?

edit: actually, I just tried it and it didn't work.

>You have to give your button the BS_NOTIFY style in order for it to send BN_SETFOCUS msg to its parent. <

I had already done that! I told you I knew it sent the BN_SETFOCUS message ...But it still never dragged for me!


>>You might find this handy.

I'm gonna go try that out right now.. Sounds great, thanks a heap.

Ok, so it kinda works...I modified it to fit my purposes, and now again in theory this should work, but ti still isn't:

Code:

	case WM_COMMAND:
		switch(HIWORD(wParam))
		{
		case BN_SETFOCUS:
			SendMessage(hwnd, WM_LBUTTONDOWN, 0, lParam);
                                                break;
		}
		return 0;
	case WM_LBUTTONDOWN:
		SendMessage((HWND)lParam,WM_SYSCOMMAND,0xF012,0); 
		return 0;

I thought it was pretty ingeneous...but it seems windows thought differently...any help HERE?

SendMessage(hChild,WM_SYSCOMMAND,0xF012,0);
buggar.. i'm sorry about that... i saw the post and thought i'd pop it in quickly before heading home.... i should have checked my code first!! my apologies!!

i hope its working for you now though.

I'm sure there are other ones like that somewhere.. but it's just typical of microsoft not to document things like this!! I managed to find this hard coded value in the depths of a news group from late 1997 or somewhere around that time.. if i come up with more i'll be sure to let you know

good luck!!
U.

>>Sub-class the cntrl

I kinda get what you're saying, but I have no clue how to do it...