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 - E37
Pages: 1 ... 10 11 [12] 13 14 ... 24
166
« on: December 13, 2016, 06:27:33 pm »
Found another! (1.2.2a)
If you use the increment or decrement command on a single byte variable it returns odd values in hl.
0->A
Disp Ar++>Dec
This code displays a weird number. (NOT 1!)
It occurs with any one byte variable variables like {oA}--
The variable's value is changed correctly, only the value left in hl is wrong.
Edit: It turns out that it just returns the pointer instead of the value.
{Ar++} returns the expected value.
167
« on: December 06, 2016, 05:39:32 pm »
Ok. I think I have found another. (I'm not sure what's causing it)
I have found that recompiling a certain app causes flash corruption. I'm not 100% sure but it has happened 2 times in a row.
It does use hooks and inline assembly but I have used similar programs without mishap.
Since I need to reset my calc anyway I figured I will try to figure out what is causing it. (I'm sure it is Axe since I haven't been using assembly recently and I have been using the same apps for a year and they never showed any problems)
Oh, and it is 1.2.2a as always.
168
« on: October 24, 2016, 02:29:26 pm »
Thanks a lot! Both yours solutions seems to be working well, however apart from the conversion, is there a simple way to create a method which returns the string?
Right now I'm using Xeda112358's answer like this:
A:prgmFRAC:Ans->Str2
B:prgmFRAC:Ans->Str3
C:prgmFRAC:Ans->Str4
"X^("+Str2+"*2)*"+Str3+"="+Str4-->Str1
However the code has become messy, is there a way to do something like this?
"X^("+frac(A)+"*2)*"+frac(B)+"="+frac(C)-->Str1
Maybe creating some sort of hook
You can accomplish that with a parser hook, however that requires that the hook is an app. I would avoid that if at all possible. If your only problem is messy code, then that is not a good reason to fool with a parser hook. (If you do decide to use the hook, then I can't help you because it is beyond my level of skill currently)
169
« on: October 23, 2016, 01:12:17 pm »
I'm not sure why it won't compile. What is the first line of the the code that you are using Asm() on? @Giacomo Pigani As for converting it to a fraction, I would suggest doing it manually in basic. I assume you know the basic trick to convert a number into a string. I would: Count the numbers past the '.', then make that number (without the decimal) over 10* the numbers past the decimal point. and reduce as much as possible. The only problem would be repeating decimals, which would have to be dealt with some other way. If you are looking for an assembler solution, you can try: :clrhome :disp A>Frac :disp "" :delvar str1 : *assemblyCode* assemblyCode: ld hl,String rst 20h ld hl,16 B_CALL(_CreateString) inc de inc de ld hl,textshadow ld bc,16 ldir ret String: .db StrngObj,tVarStrng,tStr1,0,0 That should store the first line of the display to str1. If you had your fraction displayed there, it is now a string in str1. Str1 will hold the whole first line, so you may need to trim some spaces. It returns tokens instead of characters. That means that randM( will show up instead of spaces and QuartReg will be instead of a fraction bar. The hex code for it would be :21aa9de7211000ef27431313210885011000edb0c904aa000000
170
« on: September 29, 2016, 01:45:26 pm »
... And I'm back! With more bugs! As always, I am using 1.2.2a! @Runer112 The first one isn't really a bug but more of an unexpected feature. p2 found this one. Interrupts can occur in the middle of commands like Output(x,y,expr) and if that interrupt changes the location of the cursor, then the Output command will display at the end of where the interrupt left the cursor. I'm not sure if you want to do anything about it or just leave it. I found the other bug, and it is a bug for sure. Compiling :5 and {Y1}r will compile normally, but on zoom compile it will throw error: undocumented. The five can be replaced with any number and the 'and' can be replaced with any bit-wise command (including the 2 byte plot token ones). The file must have the r after it and be the second argument. In all of the cases normal compile will not error but zoom will.
171
« on: September 27, 2016, 05:25:20 pm »
Have you checked out this page? It's been a long time since I've used a menu hook.
Yes, but it wasn't much help on actually creating the hook. The structure was helpful but no "guts" was annoying. I have it close to working but I can't find a good way to tell the menus apart.
172
« on: September 24, 2016, 03:02:44 pm »
Since I haven't got any replies, can an admin delete this thread or tack it onto the end of random questions?
Thanks
173
« on: September 20, 2016, 04:57:18 pm »
General question: Does anyone know how to use the Menu hook? (and be willing to teach me how to use it) I am familiar with how to use other hooks (home screen and key) My current attempts have lead to some screwed up menus. (At least that much of the hook works) I mainly use Axe, but can easily enough hash out a solution to a problem in assembly. (I'm really just looking for some example code - I don't care if it is Axe or assembly and it doesn't even need to be commented!) Thanks for any help! 
174
« on: September 18, 2016, 09:36:51 am »
Sounds useful!
Do you use a custom stack or do you use the normal cpu stack (so that you need to push/pop correctly before returning)?
It uses a custom stack. (SP) like in assembly is where the current end of the stack is. I often use L4 for the stack.
175
« on: September 17, 2016, 07:23:28 pm »
I have an addition to made (or at least reference) I made the axiom STAXM which is really simple. It allows the user to pop and push variables just like assembly. Here's some example code: :.TEST
:#Axiom(STAXM)
:L1->(SP)
:5->A
:Push °A
:rand->A
:Pop °A
:Disp A>Dec
... which will display 5 for the value of A. All three tokens are found under math.
176
« on: September 17, 2016, 06:27:59 pm »
Got another one!  I'm not sure if this is Axe's fault though. When using zStart to compile from within a program (ON +sto/zoom/trace) and that program is archived AND has the same name output name, Axe throws UNKNOWN ERR and quits. It deletes the source code (that's in archive probably because it tried to compile, deleted the program with that output name and then errored) How to reproduce: (have zStart installed) prgmBOB: :.BOB : Then archive BOB. Edit it with zStart. Then press one of the compile key shortcuts. Axe will throw UNKNOWN ERR and quit. prgmBOB will be deleted. Again, I don't know who's fault this bug is, but it almost took a library file that I was creating. Any ideas @Runer112 ?
177
« on: September 17, 2016, 11:16:20 am »
I opened Axe with the text editor.
Then I downloaded BrandonW's FixInititalHex.
I got rabbitsign from inside the Axe download folder.
I looked on the second or third full line of hex and found Axe's name in ASCII hex. (You may need to look up a chart of the 84's version of ASCII - zStart's font editor shows the hex that corresponds with every character.)
I modified the name to what I wanted it to be. Note that space is $20 not $00 (so you can look for "2020202020" in the app's hex for the five spaces after Axe's name to help you find it).
Then I copied all but the LAST TWO HEX CHARACTERS into fixinitialhex and replaced the final two hex characters with the corrected checksum from fixinitialhex.
Save and exit.
Use rabbitsign to sign the app and you should be done!
178
« on: September 17, 2016, 11:03:41 am »
I like number 2! There is gonna be a Moose right?  The game looks awesome!
179
« on: September 16, 2016, 01:40:04 pm »
I don't think you need the ^r after the Mask in DrawChar.
(I think) that evaluates all of the arguments first and then saves them to r1-6.
You shouldn't need the curly braces around r1 in the first subroutine unless {GBD0} is the pointer to the sprite.
If GBD0 is the pointer to the sprite, there shouldn't need to be any curly braces.
180
« on: September 14, 2016, 04:27:46 pm »
Yes, it works, but I would like to know why?
The ram clear or sending the source code and compiling? I don't really know why either work but I have some guesses. The ram clear can remove any corrupt data. Compiling? I don't really know. If your calc has a lot of trouble sending/receiving files, back up all your data and reset all your memory. That helps for me. 
Pages: 1 ... 10 11 [12] 13 14 ... 24
|
Show Posts