0 Members and 4 Guests are viewing this topic.
Quote from: Runer112 on January 15, 2014, 09:03:21 pm(A) While a full-screen update on the non-color calculators takes about 1/100th of a second and almost everything that uses it relies on it being fast, a full-screen update on the color calcs takes about 1/5th of a secondYeah but we could cheat with some frameskip and with the double-pixel trick. Moreover, some coders (like matref and I, or Builderboy and others) still have the possibility to trigger the 15MHz mode to get more speed on the CSE without losing any compatibility this time, so our programs of course will have speed issues, but also some speed gains.Also that depends on the program you are porting because I don't think AudaciTI will have too much issues with refreshing since nothing happens on the screen except menus
(A) While a full-screen update on the non-color calculators takes about 1/100th of a second and almost everything that uses it relies on it being fast, a full-screen update on the color calcs takes about 1/5th of a second
So with an 8 by 8 sprite you use Pt-Change() to draw it inverted. How do you do that with a 16 by 16?
Pt-Change(X,Y,Pic1)Pt-Change(X+8,Y,Pic1+8)Pt-Change(X,Y+8,Pic1+16)Pt-Change(X+8,Y+8,Pic1+24)
min(0,-1) .return 0 (0<65535)max(-1,0) .return -1
min(-1,5)r .return -1max(-8,9)r .return 9
.db REP_ABS .org $-1 ld hl, sub_axiom10 ld (someVar), hl
Does using #ExprOn in a program affect axiom too ?I mean, if an axiom use the axe multiplication and the program calling axiom command have #ExprOn, does the multiplication will be optimize for speed too ?
Isn't there a way to,simply call sub_mulFast instead of sub_mul ? Apparently axioms always compile in #ExprOff mode, no matter what the state of optimization is when they are parsed.