cadcdev-tiki

[cadcdev-tiki] Win32 stuff

[Sam S. <sam...@gm...>]

I see the SVN commit notifications aren't working again .. I  
committed mouse support for win32.  I had to add two files to the  
win32 solution, and I had adjusted the search path for OpenAL in my  
project file before that to c:\openal\include, so you might need to  
change that back if you update.

I'm still having problems w/ the win32 tiki app quitting.  The app  
doesn't quit when my gamethread terminates, and my gamethread wont  
terminate when I close the window.  Is there something I'm forgetting  
to do?

-Sam

Re: [cadcdev-tiki] Win32 stuff

[Dan P. <ba...@al...>]

On Feb 18, 2006, at 10:52 AM, Sam Steele wrote:

> I see the SVN commit notifications aren't working again .. I  
> committed mouse support for win32.  I had to add two files to the  
> win32 solution, and I had adjusted the search path for OpenAL in my  
> project file before that to c:\openal\include, so you might need to  
> change that back if you update.

Doh... I'll look at the server and see if I can figure it out.

> I'm still having problems w/ the win32 tiki app quitting.  The app  
> doesn't quit when my gamethread terminates, and my gamethread wont  
> terminate when I close the window.  Is there something I'm  
> forgetting to do?

I dunno if you're doing this or not, but when the user closes the  
window, it's supposed to submit a HID message requesting that you  
quit. It then waits for the thread to quit. So if the quit message is  
being lost or not responded to properly, that might do it.

At least that's my memory of how it works on OSX, maybe the Win32 one  
was different.

Re: [cadcdev-tiki] Win32 stuff

[Sam S. <sam...@gm...>]

On Feb 18, 2006, at 3:17 PM, Dan Potter wrote:

> I dunno if you're doing this or not, but when the user closes the  
> window, it's supposed to submit a HID message requesting that you  
> quit. It then waits for the thread to quit. So if the quit message  
> is being lost or not responded to properly, that might do it.
>

The quit message is sent with dev = NULL, which means GenMenu's  
processHidEvent wont pass it along to inputEvent().  Should we add a  
"window system" device, or just let NULL devices pass into inputEvent()?

Btw, this was much easier to debug in Visual Studio than XCode..  
Apple should work on that :-P

-Sam

Re: [cadcdev-tiki] Win32 stuff

[Dan P. <ba...@al...>]

On Feb 18, 2006, at 1:04 PM, Sam Steele wrote:

> The quit message is sent with dev = NULL, which means GenMenu's  
> processHidEvent wont pass it along to inputEvent().  Should we add  
> a "window system" device, or just let NULL devices pass into  
> inputEvent()?

That if statement that checks it isn't my syntax, so that must've  
been Atani. Maybe it was put there to prevent a null deref when it  
checks to see if it's a mouse? Probably best to just let it pass NULL  
events straight on down.

> Btw, this was much easier to debug in Visual Studio than XCode..  
> Apple should work on that :-P

Yes indeed... there are many things I grudge VS, but its debugger has  
no peer currently. I can take a copy of VS8 with Visual Assist  
installed and pretty much zen into the code. :) I get more done with  
that setup than pretty much any other. I'm not sure exactly what's  
wrong with Xcode but it still seems more like a Fisher Price My First  
IDE than anything...

Re: [cadcdev-tiki] Win32 stuff

[Sam S. <sam...@gm...>]

On Feb 19, 2006, at 12:34 PM, Dan Potter wrote:

> That if statement that checks it isn't my syntax, so that must've  
> been Atani. Maybe it was put there to prevent a null deref when it  
> checks to see if it's a mouse? Probably best to just let it pass  
> NULL events straight on down.
>

Ok, I'll check in my fix for it, then.  I removed that if statement  
at the top, and adjusted the mouse if statements to be
	if (evt.dev != NULL && ...
to prevent the null pointer errors.  Now my tiki apps quit when I  
tell them to!  I should have some fun stuff to show off in  
TikiSquares in a few weeks :)

> Yes indeed... there are many things I grudge VS, but its debugger  
> has no peer currently. I can take a copy of VS8 with Visual Assist  
> installed and pretty much zen into the code. :) I get more done  
> with that setup than pretty much any other. I'm not sure exactly  
> what's wrong with Xcode but it still seems more like a Fisher Price  
> My First IDE than anything...

Mostly it's sluggish, and the tabbed interface is kind of quirky.  I  
actually hadn't realized how slow the OS X terminal is until I  
started coding on win32 again.. i fired up putty to connect to my  
linux box and there was noticeably less delay between hitting a key  
and seeing the letters.  Kinda like GNOME Terminal vs xterm I guess,  
eye candy = slower.

Is VS8 .NET or the one after it?  I should see if my college's MSDNAA  
site has the latest version before they disable my account (I haven't  
attended in over a year, but they haven't gotten around to deleting  
the account yet :) ).  I'm still working on VS .NET, which is pretty  
nice too, especially with the Ankh SVN plugin.

-Sam

Re: [cadcdev-tiki] Win32 stuff

[Dan P. <ba...@al...>]

On Feb 19, 2006, at 9:46 AM, Sam Steele wrote:

> Mostly it's sluggish, and the tabbed interface is kind of quirky.   
> I actually hadn't realized how slow the OS X terminal is until I  
> started coding on win32 again.. i fired up putty to connect to my  
> linux box and there was noticeably less delay between hitting a key  
> and seeing the letters.  Kinda like GNOME Terminal vs xterm I  
> guess, eye candy = slower.

Yeah... I always appreciated the snappiness of the raw X stuff like  
Xterm, and I used to use Jordan DeLong's minimalist Golem WM too. I  
couldn't ever stand the Gnome stuff because it was so slow. Then  
something snapped in my head and I just didn't care anymore as long  
as it was less of a PIA to use. :) Which means that compared to both  
Windows and Linux, OSX is the king for me hands down. I used to have  
complaints about the snappiness of OSX, but now that I have Tiger and  
a machine with a sufficient video card, most things seem  
instantaneous UI-wise. I wish they'd get on with enabling Quartz 2D  
Extreme.

Of course Xcode still just has a crappy UI, so it doesn't get any  
such excuses. :) The syntax highlighting is bad, the completion is  
slightly better than VS's defaults, but not as good as VA. There's  
WAAY too much expectation of mouse interaction still (something which  
is somewhat true of VS too, but you can at least customize most of it  
away with macros if nothing else). No way to trace into inlined  
functions. No auto variables. Horrifyingly bad STL support (true in  
VS up until 8 anyway, which has *amazing* STL support in the debugger  
now).

Then again Xcode is also free with the OS, while VS costs some huge  
sum of money unless you get on the gravy train to get it free.

I'm embarrassed to say that after all that time of using a good IDE  
at work, I'm pretty lost with the command line only KOS stuff these  
days. ;) Not as in "can't figure it out" but "brain just doesn't want  
to go into gear".

> Is VS8 .NET or the one after it?  I should see if my college's  
> MSDNAA site has the latest version before they disable my account  
> (I haven't attended in over a year, but they haven't gotten around  
> to deleting the account yet :) ).  I'm still working on VS .NET,  
> which is pretty nice too, especially with the Ankh SVN plugin.

VS7.0 was the first ".NET" version. It's kinda dumb, I think the  
marketing people won the first round and the tech people won the  
second round. VS7.0 was "Microsoft Visual Studio .NET", and VS7.1 was  
"Microsoft Visual Studio .NET 2003", but there were more overt  
references to 7.1. VS8.0 is now just "Microsoft Visual Studio 8" in  
most places, though the official name is still "Microsoft Visual  
Studio .NET 2005". It did have a technical point though: VS7 was the  
first one written with the .NET framework itself. That's one reason  
it was so slow and had so many UI quirks. It's come a long way in the  
recent ones.

Re: [cadcdev-tiki] Win32 stuff

[Simon R. <sim...@gm...>]

SSBrbm93IHRoaXMgd2lsbCBvbmx5IG1ha2UgdGhpcyB0aHJlYWQgZXZlbiBtb3JlIG9mZi10b3Bp
YyAoSQphcG9sb2dpemUgaW4gYWR2YW5jZSksIGJ1dCBzaW5jZSB0aGVyZSdzIGFscmVhZHkgYW4g
SURFIGRpc2N1c3Npb24KZ29pbmcgb24sIGhhcyBhbnlvbmUgZG9uZSBzb21lIEMvQysrIGRldmVs
b3BtZW50IHVzaW5nIEVjbGlwc2UgKHdpdGgKdGhlIENEVCBwbHVnaW4pLCBhbmQgaWYgc28sIHlv
dXIgb3BpbmlvbnM/IEknbSBpbnZlc3RpZ2F0aW5nIGFib3V0CnVzaW5nIGl0IGluIHNvbWUgcHJv
amVjdHMgb2YgbWluZSBidXQgaGF2ZW4ndCBoZWFyZCBtdWNoIGFib3V0IGl0IHlldC4KKFN0aWxs
IGxvb2tpbmcgZm9yIGEgZGVjZW50IExpbnV4IElERS4uLiBLRGV2ZWxvcCBhbmQgQW5qdXRhIGFy
ZSBhCm1lc3MsIGFuZCBDb2RlOjpCbG9ja3MgaXMgd2F5IG5vdCBtYXR1cmUgZW5vdWdoIG91dHNp
ZGUgb2YgV2luZG93cy4pCi0tCi0gU1IK