This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Matrefeytontias
Pages: 1 ... 87 88 [89] 90 91 ... 133
1321
« on: March 01, 2013, 10:23:20 am »
Bump,
I got all of this working, except for one thing : I have a cosine LUT in my axiom situated directly inside the command using it, but when I try to access it with DB $7F RORG PC-1 ; I use mimas LD HL,CosineTable ; ... CosineTable: ; ... It returns weird values, but when I build the exact same LUT in my Axe program at saveSScreen and access it with LD HL,saveSScreen It works perfectly. I think there's a bug with REP_NEXT or something.
1322
« on: February 27, 2013, 08:20:51 am »
There's a very small chance I participate so, even if I already registered... I'm also disappointed : why always Nspires ?
1323
« on: February 27, 2013, 08:11:10 am »
I repeat that there are no other options that the two I told you some posts ago -_-
1324
« on: February 26, 2013, 07:56:04 pm »
You should say that the engine has been made by both t0xic_kitt3n and hoffa.
Also, could you post a screenie, since I don't own a Prizm ?
1325
« on: February 26, 2013, 12:20:26 pm »
I can't absorb the command since the command over-using it is not the only one using it. But I'll try with a loop.
1326
« on: February 26, 2013, 03:44:51 am »
There isn't any loop, but in many of the commands there are repetitive calls to other functions that are part of the axiom. For example, in a command I have 24 consecutive call sub_Axiom8, but the 8th command doesn't call any function at all. In an other function, I do many times call sub_Axiom4 which also doesn't call any function.
1327
« on: February 25, 2013, 05:05:25 pm »
3-bytes tokens are really a PITA to work with, and you won't be able to use the token hook with them.
Or maybe ... Let's have an example : say that the first token (which should be a 2-bytes one because rarely used) of a pack is det(. You would apply a token hook on det( to make it look like (for example, with a 3D renderer pack) "3Drender_". Then you could apply a token hook on other tokens which will be the actual commands. So for example the command det(Boxplot which is the first command of the command pack, would look like 3Drender_tri( with a token hook and F005 as hex (since det( is the prefix of all of the commands of the first command pack).
So with all of this, we can define the structure of a command pack :.dw prefixToken .dw command1token ; define everything related to a command .dw command2token ... .dw $4242 ; magic number which ends the command definition ; token hook Something you can do with it is dynamically assignating the F0 to FF token to the corresponding prefix. It would allow the use of multiple command packs without any problem.
What do you think of it ?
1328
« on: February 25, 2013, 04:40:19 pm »
I think that a 2-bytes command ID should be better, since with extensions and all the number of commands can easily go more than 255 (how do you say that correctly English ? )
1329
« on: February 25, 2013, 04:29:25 pm »
I think that appvars are the best file type for extensions. And about the format, I can't think of another one than the format used in Axe's axioms. It's so practical.
1330
« on: February 25, 2013, 03:33:53 pm »
Use the method I said so. Even if it's a PITA, I can't think of any other solution
1331
« on: February 25, 2013, 03:19:51 pm »
What's. The. Fuc cherry. Found a really weird bug.
I'm writing an axiom, and trying to include it in one of my program, the parser says INVALID AXIOM. I thought "ok, I might have made an error" but then it sends me at the very last line of the program, way after the #Axiom() line o_O
I can't post any code since 1) I don't have any computer and 2) this is a super-over-secret project I even shouldn't talk of it here (all that I can say is that the axiom is more than 4000 lines long).
BUT I report here the hex dump :
009DB7009E390441 A38FA38F00007F60 0842001D3F63A443 8B8068CB
Still using the same 2010 83+.fr with the same 1.19 OS.
1332
« on: February 25, 2013, 02:31:44 pm »
Nope, as far as I know there are only these two methods (only one involving programs and not apps). But maybe I'm wrong, so you'd better point thepenguin77 or Runer112 to this topic.
1333
« on: February 25, 2013, 02:26:09 pm »
There are two ways : a simple way that actually works, and a very hard one I just thought about so I'm not sure if it works. Simple way : follow the tutorial about my PageSwap axiom in the "Tutorials" sub-forum of Omnimaga. Yeah, I said "the easy way" And the very hard and experimental way : in the program where you define the function you want to use, follow these steps : - Create an appvar that will hold an address (one address for each function you want to use)
- Put in this appvar the addresses of each function (use the LLABEL function to have the address of a label) minus E9D93.
Then, run the program once, so the appvar holding the addresses is created. Back to your original program, follow these steps : - Access to the apppvar at the beginning of the program
- Access to the program containing the functions you want to use
- To call a function, add the corresponding address holded by the appvar to the origin of the program holding the functions, and call the resulting address. It *should* work
Here's a quick example of the last method : :.HOLDFUNC : :GetCalc("appvADDR",2)->A :LFunc1-E9D93->{A}r :.other code : :Return :Lbl Func1 :... :End
:.USEFUNC :Return!If GetCalc("appvADDR")->A :Return!If GetCalc("prgmHOLDADDR")->B : {{A}r+B}r)(parameters)I'm absolutely not sure about it working or not, I thought I got mad or something. If it actually works, I'll write a tutorial about it And please other members that are reading this thing (if any), please explain your opinions, I'll need them and it'll also help Nikitouzz
1334
« on: February 25, 2013, 01:44:33 pm »
And the question is ?
1335
« on: February 25, 2013, 11:59:13 am »
Yeaaah, it's really looking great ! But isn't the first level an entire and btw huge world ?
Pages: 1 ... 87 88 [89] 90 91 ... 133
|