I tried your Primitives example from the Quesa wrappers, and got many
failed assertions like this, probably one per primitive:
Runtime Error 4: Failed Assertion
loaderX86.cpp: 282
Failure Condition: functionEntry
Could not resolve function 'Q3Error_Register' in Quesa
Compiled with 2007r1 Mac IDE, run with Win XP under Parallels on a
Intel iMac
But the RB3D based program I'm working on now runs under Windows
(without any Quesa declare), so the statement "RB3D just plain
doesn't work on Windows" is not true here, as well as the sentence
"Install Quesa an run any RB3D project - you get a blank display (at
least I do)" that I see in the feedback report.
I have to add that I'm unable to track a crash that later occurs in
my own app (only in Win32, not in Mac OS X): after closing all
windows I get a crash if I open a new one, with no way of falling
back to the remote debugger. Possibly a side effect of something
dirty related to your findings...
HTH
Franco
On Jan 30, 2007, at 10:43 PM, Frank Condello wrote:
On 26-Jan-07, at 5:07 PM, Frank Condello wrote:
I was recently made aware that my Quesa Wrappers failed to work on
Windows XP when compiled with RB2006r4 or RB2007r1 but worked fine
with 2006r3. A little digging revealed that creating an Object3D
no longer initializes Quesa (an implementation detailed my
wrappers rely on).
Errrm, this is an implementation detail RB3D relies on! RB3D just
plain doesn't work on Windows in my testing: <http://
www.realsoftware.com/feedback/viewreport.php?reportid=nbwdxvgr> The
"not a bug" evaluation was hasty at best... :/
Frank.
<http://developer.chaoticbox.com/>
<http://macgameblog.com/>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|