flat assembler
Message board for the users of flat assembler.
![]() |
Author |
|
vid
just tried to download during your updating
![]() |
|||
![]() |
|
vid
it crashed for me. I couldn't find more info about error because of fullscreen.
great to see some error checking, but doesn't these return error too? Code: ;set clip rectangle of Directdraw commands invoke DDSetClipRectangles, screenrect, 1 invoke DDSetSoftClipRegion, 0, 0, SCREENWIDTH, SCREENHEIGHT invoke DDSetDrawMode8, 0 ;load in tile graphics invoke DDCreatePlainFromBmp, TILESURFACE, "Tiles.bmp", DDVIDEOSURFACE, 0 invoke DDFillBack, 0 invoke DDFlipNV invoke DDFillBack, 0 ;DDCreateNewFont required for fonts not in the Windows font folder invoke DDCreateNewFont, 0, FW_SEMIBOLD, 32, 64, 0, 0, "Black Chancery" |
|||
![]() |
|
madmatt
I'll put in better error checking, should have done this before I uploaded!
|
|||
![]() |
|
LocoDelAssembly
Worked for me.
|
|||
![]() |
|
madmatt
Thanks, locodelassembly, by the way is anyone using Windows Vista yet?
|
|||
![]() |
|
cubeoid
i have a 32bit version
EDIT: and it runs fine |
|||
![]() |
|
madmatt
Thanks cubeoid, so far so good. Is it still crashing on your system vid?
|
|||
![]() |
|
vid
1. if i delete ttf, app still runs and look little weird...
2. if i delete bmp, app crashes. (that was probably the original reason - i tried without bmp) madmatt: you must check error after EVERY procedure which can return error (including ReadFile, CloseFile, etc... ALL), and if you are in procedure, return the error. Also you then check error after every call of such procedure. |
|||
![]() |
|
madmatt
vid, what OS/Directx version are you using?
|
|||
![]() |
|
vid
winXP, no idea about directX version.
i said: app crashes, if i delete BMP. Problem is in DDCreatePlainFromBMP, exactly the one i stated before: Quote: Also you then check error after every call of such procedure. In your case, it's the call of first function (don't know it's name) in "DDCreatePlainFromBMP", which returns -1 if file doesn't exist. This goes unchecked. Following function calls are all unchecked too. again: go through entire your sources, and check EVERY call there that can return error. I bet 96% of them do. PS: Sorry to reverse your DLL. |
|||
![]() |
|
madmatt
Wow, figured all that out be reversing my dll?
Quote: PS: Sorry to reverse your DLL. No problem. Wow, figured all that out by reversing my dll, your dangerous! ![]() Your not supposed to delete the bmp, does it work if you don't? also added a 15bit and 16bit version. I'm not able to test the 15bit version so let me know if this works. I'll take care of all the error checking in the next update, right now have other things to do. |
|||
![]() |
|
rugxulo
vid wrote: winXP, no idea about directX version. Start ... Run ... dxdiag.exe Quote:
I hear that DirectX 10 will be exclusive to Vista (dunno why, though). EDIT: I didn't test this because I didn't think you'd need testing on such a common machine as my P4/2.52 Ghz Win XP Home SP2 DirectX 9.0c cpu. (Tell me if I'm wrong, though!) |
|||
![]() |
|
vid
Quote: Wow, figured all that out be reversing my dll? EDIT: yes, with BMP it works. But i keep seeing windows's "hourglass" cursor, too much cooperative mode?. |
|||
![]() |
|
madmatt
rugxulo: go ahead, the more reports the better.
vid: Look's like i forgot to make the cursor disapear. It uses exclusive mode which is full speed ahead, but also set the "allow_reboot" flag. I'm working on V2.0 that will fix all of these problems, and more. |
|||
![]() |
|
f0dder
rugxulo wrote:
Other people will probably say "because it's new architecture omg!!!", but the real reason is of course that MS needs a selling point for Vista. |
|||
![]() |
|
pabloreda
in 15bits color not work
16 and 32 work OK NVidia Gforce MX440 directx9.0c win98 |
|||
![]() |
|
madmatt
fodder: found this interesting bit of info from: www.firingsquad.com
Quote: The one thing that Microsoft has done with Vista is incorporate a subsystem that will comply with DirectX 9.0 graphics hardware due to the population of users that still own DX9-compliant hardware. This subsystem will be named none other than DirectX 9.0L. So, in short, if you have DirectX 9 hardware, you will be using DirectX 9.0L as your API in Windows Vista. pabloreda: Thanks. Only very old cards use 15-bit graphics now. 16-bit is the norm now. |
|||
![]() |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2020, Tomasz Grysztar. Also on GitHub, YouTube, Twitter.
Website powered by rwasa.