gamedevlists-windows Mailing List for gamedev (Page 56)
Brought to you by:
vexxed72
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(48) |
Oct
(58) |
Nov
(49) |
Dec
(38) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(124) |
Feb
(83) |
Mar
(17) |
Apr
(37) |
May
(12) |
Jun
(20) |
Jul
(47) |
Aug
(74) |
Sep
(62) |
Oct
(72) |
Nov
(54) |
Dec
(13) |
2003 |
Jan
(36) |
Feb
(8) |
Mar
(38) |
Apr
(3) |
May
(6) |
Jun
(133) |
Jul
(20) |
Aug
(18) |
Sep
(12) |
Oct
(4) |
Nov
(28) |
Dec
(36) |
2004 |
Jan
(22) |
Feb
(51) |
Mar
(28) |
Apr
(9) |
May
(20) |
Jun
(9) |
Jul
(37) |
Aug
(20) |
Sep
(23) |
Oct
(15) |
Nov
(23) |
Dec
(27) |
2005 |
Jan
(22) |
Feb
(20) |
Mar
(5) |
Apr
(14) |
May
(10) |
Jun
|
Jul
(6) |
Aug
(6) |
Sep
|
Oct
(12) |
Nov
(1) |
Dec
|
2006 |
Jan
(18) |
Feb
(4) |
Mar
(3) |
Apr
(6) |
May
(4) |
Jun
(3) |
Jul
(16) |
Aug
(40) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
(2) |
2007 |
Jan
(5) |
Feb
(2) |
Mar
(4) |
Apr
(1) |
May
(13) |
Jun
|
Jul
(26) |
Aug
(3) |
Sep
(10) |
Oct
|
Nov
(4) |
Dec
(5) |
2008 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Andrew G. <an...@ra...> - 2002-02-08 00:03:22
|
We need archives! Either detect WM_NCMOUSEMOVE or WM_MOUSELEAVE and use ShowCursor(TRUE), to make the cursor visible until it re-enters the client area. // andrew ----- Original Message ----- From: "Ignacio Castaño" <cas...@ya...> To: <gam...@li...> Sent: Thursday, February 07, 2002 11:46 PM Subject: [GD-Windows] cursor over titlebar > Hi, > I hide the mouse cursor using ShowCursor(0) when my app is activated, so > that the cursor doesn't appear over the window. However, I would like to > show it when it's over the titlebar, to allow the user to move the window. > Any hints would be appreciated! > > > Ignacio Castaño > ca...@as... > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: > http://sourceforge.net/mailarchive/forum.php?forum_id=555 > |
From: Jon W. <hp...@mi...> - 2002-02-08 00:03:21
|
Look for WM_NCMOUSEMOVE and show it when you see those. The question becomes one of when to hide the cursor again. If you only hide on regular mousemove, then the user may be fast enough that his cursor escapes your window without first passing through the NC area. TrackMouseEvent may help here, perhaps. WM_NCxx == non-client area window messages. Cheers, / h+ > -----Original Message----- > From: gam...@li... > [mailto:gam...@li...]On Behalf Of > Ignacio Castaño > Sent: Thursday, February 07, 2002 3:47 PM > To: gam...@li... > Subject: [GD-Windows] cursor over titlebar > > > Hi, > I hide the mouse cursor using ShowCursor(0) when my app is activated, so > that the cursor doesn't appear over the window. However, I would like to > show it when it's over the titlebar, to allow the user to move the window. > Any hints would be appreciated! > > > Ignacio Castaño > ca...@as... > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: > http://sourceforge.net/mailarchive/forum.php?forum_id=555 > |
From: Brian H. <bri...@py...> - 2002-02-08 00:01:22
|
Look at WM_NCMOUSEMOVE and if it enters your title area, show the cursor? case WM_NCMOUSEMOVE: { POINTS pts =3D MAKEPOINTS( lParam ); ev.evType =3D HEvent::ET_MOUSEMOVE; POINT pt =3D { pts.x, pts.y }; ScreenToClient( hWnd, &pt ); if ( pt.x < 0 ) ShowCursor( TRUE ); //or something like that } break; > -----Original Message----- > From: gam...@li...=20 > [mailto:gam...@li...] On=20 > Behalf Of Ignacio Casta=F1o > Sent: Thursday, February 07, 2002 3:47 PM > To: gam...@li... > Subject: [GD-Windows] cursor over titlebar >=20 >=20 > Hi, > I hide the mouse cursor using ShowCursor(0) when my app is=20 > activated, so that the cursor doesn't appear over the window.=20 > However, I would like to show it when it's over the titlebar,=20 > to allow the user to move the window. Any hints would be appreciated! >=20 >=20 > Ignacio Casta=F1o > ca...@as... >=20 >=20 >=20 > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com >=20 >=20 > _______________________________________________ > Gamedevlists-windows mailing list=20 > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=3D555 >=20 |
From: <cas...@ya...> - 2002-02-07 23:40:26
|
Hi, I hide the mouse cursor using ShowCursor(0) when my app is activated, so that the cursor doesn't appear over the window. However, I would like to show it when it's over the titlebar, to allow the user to move the window. Any hints would be appreciated! Ignacio Castaño ca...@as... _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Javier A. <ja...@py...> - 2002-02-07 08:08:51
|
SetCapture() is the correct way to handle mouse drag (press button, move mouse around, release button) functionality. It's important to handle WM_CAPTURELOST as well. SetCapture() is appropriate here because it's a temporary state. SetCapture() is NOT the correct way to receive all mouse input even if the mouse is outside the window, because this is not temporary. In fact, receiving mouse input when the mouse is outside the window should be done only in drag situations (but I know this is not always possible). Javier Arevalo Pyro Studios ----- Original Message ----- From: "Brian Hook" <bri...@py...> To: <gam...@li...> Sent: Thursday, February 07, 2002 2:23 AM Subject: [GD-Windows] Out of window mouse up messages > I'm tracking drag state in my app, however I'm running into a problem > when the mouse button is pressed, the cursor is dragged outside the > window, and then the mouse button is released. I never see the release, > which gets my app confused. > > Is there a simple way of getting around this, or should I simply check > the mouse button state every time I get a move message to verify its > authenticity? |
From: Rob H. <ro...@ga...> - 2002-02-07 06:09:14
|
I can think of 2 ways to get around this problem. 1: Go back to using SetCapture(). When the window loses the mouse capture( the user clicked a window owned by another thread ) you will get a WM_CAPTURECHANGED message. Buttons do this type of thing so they can make sure the BUTTONUP message comes while the mouse is actually on the button. 2: Try using TrackMouseEvent(). This will enable the specified window to receive WM_MOUSELEAVE and WM_NCMOUSELEAVE messages. Rob -----Original Message----- From: gam...@li... [mailto:gam...@li...] On Behalf Of Brian Hook Sent: Wednesday, February 06, 2002 7:46 PM To: gam...@li... Subject: RE: [GD-Windows] Out of window mouse up messages Hmmmm, one minor problem, not sure if it's a real problem, is that I won't actually "see" the mouse up until the cursor comes back into the window since I won't be getting the WM_MOUSEMOVE while it's outside the window. Brian _______________________________________________ Gamedevlists-windows mailing list Gam...@li... https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=555 |
From: Brian H. <bri...@py...> - 2002-02-07 02:46:14
|
Hmmmm, one minor problem, not sure if it's a real problem, is that I won't actually "see" the mouse up until the cursor comes back into the window since I won't be getting the WM_MOUSEMOVE while it's outside the window. Brian |
From: Brian H. <bri...@py...> - 2002-02-07 02:37:35
|
A-ha, that should work. I hacked my stuff to use SetCapture() when the mouse was pressed, but we've already gone over why SetCapture() is bad =) Brian |
From: Brian S. <bs...@mi...> - 2002-02-07 02:35:28
|
WM_MOUSEMOVE tells you which buttons are pressed. If you get one with a button up when your isDragging flag is set, you know someone released outside your window, so you can just execute your EndDrag() function (or CancelDrag(), or whatever). > -----Original Message----- > From: Brian Hook [mailto:bri...@py...] > Sent: Wednesday, February 06, 2002 5:23 PM > To: gam...@li... > Subject: [GD-Windows] Out of window mouse up messages >=20 > I'm tracking drag state in my app, however I'm running into a problem > when the mouse button is pressed, the cursor is dragged outside the > window, and then the mouse button is released. I never see the release, > which gets my app confused. >=20 > Is there a simple way of getting around this, or should I simply check > the mouse button state every time I get a move message to verify its > authenticity? >=20 > Brian |
From: Brian H. <bri...@py...> - 2002-02-07 01:23:21
|
I'm tracking drag state in my app, however I'm running into a problem when the mouse button is pressed, the cursor is dragged outside the window, and then the mouse button is released. I never see the release, which gets my app confused. Is there a simple way of getting around this, or should I simply check the mouse button state every time I get a move message to verify its authenticity? Brian |
From: Jon W. <hp...@mi...> - 2002-02-06 04:54:07
|
I found a "product graphics" section at http://www.microsoft.com/partner/businessresources/salesresources/ However, it contains shots of the Windows retail box, rather than the Windows logo. Most companies are rather protective about their logo and how you use it, so it might not be OK to just swipe one and use it. I'm assuming you already read http://www.microsoft.com/trademarks/ It seems from that that you really can't use their Windows logo without going through certification. I believe that may be their intent. Now, whether they're gonna send copyright nazis to your house in the middle of the night or not, I have no idea. As for curbing the "buy the wrong thing" problem: You could have your web page look at the user agent, which most of the time has the operating system in it. So sub-string for the OS installed, and warn the user if the UA doesn't seem to match the package they're buying. You could also put a cookie in the window that allows them to download the other platform within the next 7 days or something, assuming you have a studly database back-end that can properly validate/expire these kinds of one-time-use tickets. Cheers, / h+ > -----Original Message----- > From: gam...@li... > [mailto:gam...@li...]On Behalf Of > Brian Hook > Sent: Tuesday, February 05, 2002 6:44 PM > To: gam...@li... > Subject: RE: [GD-Windows] Getting Windows logo for Web page > > > > I don't think there's anything stopping you placing a Windows > > logo on a page, providing you have the standard "Microsoft > > Windows and blah blah, are trademarks of" and so on at the > > bottom somewhere. An awful lot of companies have this type of > > thing on their download pages. > > Right, but where do I get the regular Windows logo in a form that's > resizable, etc. for placement on a Web page? I had hoped Microsoft > would have this in some "marketing package" or something like that in > EPS form, etc. > > > Having the "Designed For Microsoft Windows" logo though is a > > different matter which requires you to meet all kind of > > certification requirements, I guess this is what you saw on ms.com > > Right. The above is overkill, we just need the logo so that someone > doesn't click the wrong "Buy Now!" button. That's a big concern for us, > because basically they're going to see: > > Click here to purchase Candy Cruncher for Windows > Click here to purchase Candy Cruncher for OS X > > And I just KNOW we're going to get people clicking on the wrong ones, so > hopefully pretty pictures will avoid some of the confusion. > > Brian > > > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > |
From: Brian H. <bri...@py...> - 2002-02-06 02:43:55
|
> I don't think there's anything stopping you placing a Windows > logo on a page, providing you have the standard "Microsoft > Windows and blah blah, are trademarks of" and so on at the > bottom somewhere. An awful lot of companies have this type of > thing on their download pages. Right, but where do I get the regular Windows logo in a form that's resizable, etc. for placement on a Web page? I had hoped Microsoft would have this in some "marketing package" or something like that in EPS form, etc. > Having the "Designed For Microsoft Windows" logo though is a > different matter which requires you to meet all kind of > certification requirements, I guess this is what you saw on ms.com Right. The above is overkill, we just need the logo so that someone doesn't click the wrong "Buy Now!" button. That's a big concern for us, because basically they're going to see: Click here to purchase Candy Cruncher for Windows Click here to purchase Candy Cruncher for OS X And I just KNOW we're going to get people clicking on the wrong ones, so hopefully pretty pictures will avoid some of the confusion. Brian |
From: Andrew G. <an...@ra...> - 2002-02-06 02:33:35
|
I don't think there's anything stopping you placing a Windows logo on a page, providing you have the standard "Microsoft Windows and blah blah, are trademarks of" and so on at the bottom somewhere. An awful lot of companies have this type of thing on their download pages. Having the "Designed For Microsoft Windows" logo though is a different matter which requires you to meet all kind of certification requirements, I guess this is what you saw on ms.com // andrew ----- Original Message ----- From: "Brian Hook" <bri...@py...> To: <gam...@li...> Sent: Wednesday, February 06, 2002 2:17 AM Subject: [GD-Windows] Getting Windows logo for Web page > I'd like to put up a Windows logo next to the link to purchase CC for > Windows. Anyone know the "proper channels" to get such a thing? I saw > the logo certification at microsoft.com, but that looks like overkill > for what I'm doing. > > Brian > > > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > |
From: Brian H. <bri...@py...> - 2002-02-06 02:16:42
|
I'd like to put up a Windows logo next to the link to purchase CC for Windows. Anyone know the "proper channels" to get such a thing? I saw the logo certification at microsoft.com, but that looks like overkill for what I'm doing. Brian |
From: Matt D. <ma...@co...> - 2002-01-30 10:00:26
|
It's important to note that Windows' makes a huge distinction between client and non-client areas of the window and has mutually exclusive messages to deal with the two areas. I know I keep forgetting about WM_NCxxx messages :-( Matt Davies Programmer, Confounding Factor ma...@co... www.confounding-factor.com -----Original Message----- From: gam...@li... [mailto:gam...@li...]On Behalf Of Brian Hook Sent: 30 January 2002 01:33 To: gam...@li... Subject: RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE > I guess you have something like ShowCursor(FALSE); Exactly. > Instead of using SetCapture, why not detect WM_NCMOUSEMOVE > messages and make the system cursor visible so that it is > displayed in the title bar. Hey, that works! =) Originally I was using SetCapture() because WM_MOUSEMOVE wouldn't report movements outside the client area (so I didn't know when to ShowCursor( TRUE )), not to mention the cursor wasn't being drawn correctly in the titlebar. By also trapping WM_NCMOUSEMOVE and doing a ScreenToClient() and posting that as a regular mousemove to my own event queue, it allowed me to ditch SetCapture() -- however, since I wasn't sure I was going to be able to fix all this, I ended up removing my dependency on WA_CLICKACTIVE =| Anyway, looks like things are much better structured now. Less cruft, that's for sure. Thanks to everyone that helped! Brian _______________________________________________ Gamedevlists-windows mailing list Gam...@li... https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows |
From: Brian H. <bri...@py...> - 2002-01-30 01:33:00
|
> I guess you have something like ShowCursor(FALSE); Exactly. > Instead of using SetCapture, why not detect WM_NCMOUSEMOVE > messages and make the system cursor visible so that it is > displayed in the title bar. Hey, that works! =) Originally I was using SetCapture() because WM_MOUSEMOVE wouldn't report movements outside the client area (so I didn't know when to ShowCursor( TRUE )), not to mention the cursor wasn't being drawn correctly in the titlebar. By also trapping WM_NCMOUSEMOVE and doing a ScreenToClient() and posting that as a regular mousemove to my own event queue, it allowed me to ditch SetCapture() -- however, since I wasn't sure I was going to be able to fix all this, I ended up removing my dependency on WA_CLICKACTIVE =| Anyway, looks like things are much better structured now. Less cruft, that's for sure. Thanks to everyone that helped! Brian |
From: Brian S. <bs...@mi...> - 2002-01-30 01:29:21
|
> > This might be related to the overall problem >=20 > Well, removing SetCapture() allowed me to get those messages. >=20 > > line out, the cursor disappears in the title bar (it's user > > draw in the client area and system draw outside the window, > > but in the titlebar nothing happens). >=20 > The above remains a problem -- I can get rid of the calls to > SetCapture() if I'm willing to live with an invisible cursor on the > titlebar. This is rather bothersome since it makes moving the window > around very difficult. I think SetCapture is just going to cause you problems...I never had to use it to write things that ran in a window. Are you giving your window a cursor in your WNDCLASS (when you call RegisterClass)? If you didn't do that, I wouldn't be surprised if you didn't get a cursor in your non-client area (you know, the hipster term for the title bar :). I believe that ShowCursor will still control cursor visibility in your client area (which is what you want, since you're drawing your own there), so it shouldn't affect your app. If that's not it, then it beats the hell outta me! --brian |
From: Andrew G. <an...@ra...> - 2002-01-30 01:19:06
|
I guess you have something like ShowCursor(FALSE); in your program to hide the system cursor so you can draw your own? Instead of using SetCapture, why not detect WM_NCMOUSEMOVE messages and make the system cursor visible so that it is displayed in the title bar. // andrew ----- Original Message ----- From: "Brian Hook" <bri...@py...> To: <gam...@li...> Sent: Wednesday, January 30, 2002 1:03 AM Subject: RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE > > Do you ever call SetCapture() to capture the mouse? > > Yes. > > > And if yes, do you call ReleaseCapture() on deactivate? > > Yes. > > This might be related to the overall problem, however, so I'll look into > that. Right now I'm capturing the mouse on WM_MOUSEMOVE also, although > I don't remember why =) Basically, if I get a WM_MOUSEMOVE and the > point is in the client area, then I do a SetCapture(). If I comment > this line out, the cursor disappears in the title bar (it's user draw in > the client area and system draw outside the window, but in the titlebar > nothing happens). > > I would love to be able to get rid of my calls to SetCapture() though. > > Brian > > > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > |
From: Brian H. <bri...@py...> - 2002-01-30 01:17:58
|
> This might be related to the overall problem Well, removing SetCapture() allowed me to get those messages. > line out, the cursor disappears in the title bar (it's user > draw in the client area and system draw outside the window, > but in the titlebar nothing happens). The above remains a problem -- I can get rid of the calls to SetCapture() if I'm willing to live with an invisible cursor on the titlebar. This is rather bothersome since it makes moving the window around very difficult. -Brian |
From: Brian H. <bri...@py...> - 2002-01-30 01:03:17
|
> Do you ever call SetCapture() to capture the mouse? Yes. > And if yes, do you call ReleaseCapture() on deactivate? Yes. This might be related to the overall problem, however, so I'll look into that. Right now I'm capturing the mouse on WM_MOUSEMOVE also, although I don't remember why =) Basically, if I get a WM_MOUSEMOVE and the point is in the client area, then I do a SetCapture(). If I comment this line out, the cursor disappears in the title bar (it's user draw in the client area and system draw outside the window, but in the titlebar nothing happens). I would love to be able to get rid of my calls to SetCapture() though. Brian |
From: Brian S. <bs...@mi...> - 2002-01-30 00:36:09
|
Do you ever call SetCapture() to capture the mouse? And if yes, do you call ReleaseCapture() on deactivate? > -----Original Message----- > From: Brian Hook [mailto:bri...@py...] > Sent: Tuesday, January 29, 2002 3:54 PM > To: gam...@li... > Subject: RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE >=20 > > Are you even recieving WM_NCHITTEST messages? If anything, > > that might prove useful in tracking down which window is the culprit.. >=20 > Nope, those aren't showing up in Spy++ either. >=20 > Brian |
From: Andrew G. <an...@ra...> - 2002-01-30 00:18:24
|
Mad. Do you get the same problem on the DirectDraw "Windowed" sample? (part of the DX8 SDK). I get all the expected messages from that and it's a fairly basic sample so might give you something to comapre your app with, or see how the order of messages differs from yours. It's probably one of those fun "oh I have to do that?" Windows problems :) // andrew ----- Original Message ----- From: "Brian Hook" <bri...@py...> To: <gam...@li...> Sent: Wednesday, January 30, 2002 12:02 AM Subject: RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE > Yep. DefWindowProc() gets called on all messages except the ones it > shouldn't =) (specifically, WM_CREATE, WM_DESTROY and WM_ERASEBKGND). > > Brian > > > -----Original Message----- > > From: gam...@li... > > [mailto:gam...@li...] On > > Behalf Of Andrew Grant > > Sent: Tuesday, January 29, 2002 3:57 PM > > To: gam...@li... > > Subject: Re: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE > > > > > > Do you call DefWindowProc at the bottom of your message loop? > > > > > > // andrew > > > > ----- Original Message ----- > > From: "Brian Hook" <bri...@py...> > > To: <gam...@li...> > > Sent: Tuesday, January 29, 2002 11:39 PM > > Subject: RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE > > > > > > > > Oddly enough, I'm also not receiving WA_CLICKACTIVE in > > > > WM_ACTIVATE...curiouser and curiouser. > > > > > > Okay, it's gone from curious to annoying. If I click on my app's > > > title bar, I get WM_MOUSEACTIVATE and > > WM_ACTIVATE/WA_CLICKACTIVE. If > > > I click in the client area, however, I only get > > WM_ACTIVATE/WA_ACTIVE. > > > It's a pretty vanilla window. The only thing I can think > > of is that > > > some of the documentation throws around "Child window" as a term a > > > lot, and since the only child windows I have are created by Windows > > > (title bar, system menu), that my problem lies with that. > > > > > > Brian > > > > > > > > > _______________________________________________ > > > Gamedevlists-windows mailing list > > > Gam...@li... > > > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > > > > > > > > > _______________________________________________ > > Gamedevlists-windows mailing list > > Gam...@li... > > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > > > > > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > |
From: Brian H. <bri...@py...> - 2002-01-30 00:02:19
|
Yep. DefWindowProc() gets called on all messages except the ones it shouldn't =) (specifically, WM_CREATE, WM_DESTROY and WM_ERASEBKGND). Brian > -----Original Message----- > From: gam...@li... > [mailto:gam...@li...] On > Behalf Of Andrew Grant > Sent: Tuesday, January 29, 2002 3:57 PM > To: gam...@li... > Subject: Re: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE > > > Do you call DefWindowProc at the bottom of your message loop? > > > // andrew > > ----- Original Message ----- > From: "Brian Hook" <bri...@py...> > To: <gam...@li...> > Sent: Tuesday, January 29, 2002 11:39 PM > Subject: RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE > > > > > Oddly enough, I'm also not receiving WA_CLICKACTIVE in > > > WM_ACTIVATE...curiouser and curiouser. > > > > Okay, it's gone from curious to annoying. If I click on my app's > > title bar, I get WM_MOUSEACTIVATE and > WM_ACTIVATE/WA_CLICKACTIVE. If > > I click in the client area, however, I only get > WM_ACTIVATE/WA_ACTIVE. > > It's a pretty vanilla window. The only thing I can think > of is that > > some of the documentation throws around "Child window" as a term a > > lot, and since the only child windows I have are created by Windows > > (title bar, system menu), that my problem lies with that. > > > > Brian > > > > > > _______________________________________________ > > Gamedevlists-windows mailing list > > Gam...@li... > > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > > > > > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > |
From: Andrew G. <an...@ra...> - 2002-01-29 23:57:00
|
Do you call DefWindowProc at the bottom of your message loop? // andrew ----- Original Message ----- From: "Brian Hook" <bri...@py...> To: <gam...@li...> Sent: Tuesday, January 29, 2002 11:39 PM Subject: RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE > > Oddly enough, I'm also not receiving WA_CLICKACTIVE in > > WM_ACTIVATE...curiouser and curiouser. > > Okay, it's gone from curious to annoying. If I click on my app's title > bar, I get WM_MOUSEACTIVATE and WM_ACTIVATE/WA_CLICKACTIVE. If I click > in the client area, however, I only get WM_ACTIVATE/WA_ACTIVE. It's a > pretty vanilla window. The only thing I can think of is that some of > the documentation throws around "Child window" as a term a lot, and > since the only child windows I have are created by Windows (title bar, > system menu), that my problem lies with that. > > Brian > > > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > |
From: Brian H. <bri...@py...> - 2002-01-29 23:54:29
|
> Are you even recieving WM_NCHITTEST messages? If anything, > that might prove useful in tracking down which window is the culprit.. Nope, those aren't showing up in Spy++ either. Brian |