GraySprite32_OR(0,0,32,up1,up2,GrayGetPlane(LIGHT_PLANE),GrayGetPlane(DARK_PLANE));
what is wrong with this? nothing happens when i use it
-jordan
what is wrong with this? nothing happens when i use it
-jordan
- TIGCC Programming
- TIGCC Tools Suite & eBook Generator
- FAT Engine and Related Stuff
- Bug Reports (TICT Software)
- Suggestions
- Custom Beta Tests
- Off Topics - Misc. Stuff
- TIGCC Programming Archive (XX/2003-XX/2006)
- TIGCC Programming Archive (XX/2003)
- TIGCC Programming Archive (01/2003-12/2003)
- TIGCC Programming Archive (05/2002-01/2003)
- TIGCC Programming Archive (10/2001-05/2002)
- TIGCC Programming Archive (04/2001-09/2001)
- TIGCC Programming Archive (09/2000-04/2001)
- Off Topics Archive
extgraph: GraySprite32_OR
| Author | Comment | ||
|---|---|---|---|
 jmank88 |
extgraph: GraySprite32_OR |
Lead | |
|
Posts: 260 (2004-02-07 21:40:02) |
|
||
|
Lionel Debroux |
Re: extgraph: GraySprite32_OR | ||
|
Posts: 3059 (2004-02-08 22:20:41) Former Admin |
Which ExtGraph version are you using ? Which TIGCC version are you using ?
By the way, this board is not the most appropriate one to talk about ExtGraph (it's currently Custom Beta Tests). |
||
|
jmank88 |
Re: extgraph: GraySprite32_OR | ||
|
Posts: 260 (2004-02-08 23:51:42) |
TIGCC-0.95 beta 5
ExtGraph-2.00 beta 1 |
||
|
Lionel Debroux |
Re: extgraph: GraySprite32_OR | ||
|
Posts: 3059 (2004-02-09 14:29:17) Former Admin |
I've seen what is the problem: two movea.l %d3,%a0 and movea.l %d3,%a1 instead of movea.w.
You can work around this by fixing GraySprite32_OR.s and including it in your project (the next beta of ExtGraph won't come too soon). |
||
|
jackiechan |
Re: extgraph: GraySprite32_OR | ||
|
Posts: 291 (2004-02-12 15:06:08) |
I looked at the other GraySprite32_MODE routines and they are all buggies.
We will correct this bug for the next beta. But why don't you use the _R functions (ie GraySprite32_OR_R in your case) ?? |
||
|
jmank88 |
_regparm_ | ||
|
Posts: 260 (2004-02-12 22:54:30) |
whats the advantage of using _R(_regparm)?
-jordan |
||
|
Kevin Kofler |
Re: _regparm_ | ||
|
Posts: 7049 (2004-02-12 23:52:35) Admin |
It is more efficient (in both size and speed).
|
||
|
jmank88 |
oh | ||
|
Posts: 260 (2004-02-14 01:59:24) |
i guess that makes sense then
are the old routines just there for backwards comptibility then? |
||
|
jackiechan |
Re: oh | ||
|
Posts: 291 (2004-02-14 02:05:36) |
Yes, you're right
|
||
|
Lionel Debroux |
Re: oh | ||
|
Posts: 3059 (2004-02-14 21:56:18) Former Admin |
Unlike TI and some other programmers, we care about backwards compatibility...
Most brand-new routines do not exist in __stkparm__ mode, we'll never make __stkparm__ versions of them. |
||
|
Sebastian Reichelt |
Re: oh | ||
|
Posts: 1980 (2004-02-26 16:37:43) Admin |
This is asked for so often, so I don't understand why you don't turn the non-suffixed versions of the functions into macros that are replaced by the regparm versions.
|
||
|
Lionel Debroux |
Re: oh | ||
|
Posts: 3059 (2004-02-26 18:26:12) Former Admin |
That might break ASM programs using ExtGraph 1.02. There are very few of them, if any.
|
||
|
Fisch2 |
Re: oh | ||
|
Posts: 548 (2004-02-26 18:44:32) |
I think the compatibility issues are going to be mainly with people who have not been programming that long and are not as experienced of programmers. People, if any, who have used ExtGraph in ASM programs are probably going to be more experienced (due to the fact that they program in assembly) and will be able to easily change the names of a few functions.
You will probably get many more questions like the one above than you will by experienced assembly programmers who will have to update the names of their ExtGraph functions. |
||
|
jackiechan |
Re: oh | ||
|
Posts: 291 (2004-02-28 23:36:54) |
> That might break ASM programs using ExtGraph 1.02. There are very few of them, if any.
But ASM programs shouldn't use C header, should they ? |
||
|
Sebastian Reichelt |
Re: oh | ||
|
Posts: 1980 (2004-03-01 13:03:41) Admin |
jackiechan: That's the point. Unless they do (which is very uncommon), they will not see the #defines.
|
||
- TIGCC Programming
- TIGCC Tools Suite & eBook Generator
- FAT Engine and Related Stuff
- Bug Reports (TICT Software)
- Suggestions
- Custom Beta Tests
- Off Topics - Misc. Stuff
- TIGCC Programming Archive (XX/2003-XX/2006)
- TIGCC Programming Archive (XX/2003)
- TIGCC Programming Archive (01/2003-12/2003)
- TIGCC Programming Archive (05/2002-01/2003)
- TIGCC Programming Archive (10/2001-05/2002)
- TIGCC Programming Archive (04/2001-09/2001)
- TIGCC Programming Archive (09/2000-04/2001)
- Off Topics Archive
