Show Posts

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 - Runer112

Pages: 1 ... 45 46 [47] 48 49 ... 153
691
The Axe Parser Project / Re: Axe Parser
« on: February 01, 2013, 10:58:02 pm »
The string termination character is just a null (zero) byte. When string data is equated to a static pointer or used inline (like after a Disp or otherwise immediately used), this null terminator is automatically added. Otherwise it is not added. However, you can add it manually when you have lots of string data, like this:

Code: [Select]
"Easy"->Str11
"Medium"[00]
"Hard"[00]

692
The Axe Parser Project / Re: Axe Parser
« on: January 29, 2013, 01:57:58 pm »
Axe's link protocol is a little weird. I detailed it here about a year ago for someone else wanting to interact with it.

The tabs might have gotten eaten by the code box. You may be able to view it as it was intended by quoting the post, deleting the quote tags, and then previewing it.

693
Computer Programming / Re: Nullpointer exception
« on: January 25, 2013, 04:12:20 pm »
It's not possible to change the values of foxBA, foxMA, foxBP, and foxMLS through the array. Those four variables do not point to elements of the array, nor do the elements of the array point to the variables.


I think the least changes you could perform to make this work would be to change the array initializations to this:
Code: [Select]
JTextArea[] textFox = new JTextArea[4];
String[] label = {"Breeding Age: ", "Max Age: ", "Breeding Probability: ", "Max Litter Size: "};

Then perform your initialization code, and then initialize the individual variables:
Code: [Select]
JTextArea foxBA = textFox[0], foxMA = textFox[1], foxBP = textFox[2], foxMLS = textFox[3];



My object-oriented design teacher would probably yell at any student who used code like this in general, but that's a different matter. :P

694
Computer Programming / Re: Nullpointer exception
« on: January 25, 2013, 03:47:50 pm »
This line:

textFox = new JTextArea(1, 5);

is overwriting foxBA, foxMA, foxBP, and foxML in the array, not actually changing the values of them. If you want to be able to access each element of the array by named variables, perhaps set them equal to their appropriate array elements after the array has been initialized?

695
The Axe Parser Project / Re: Bug Reports
« on: January 25, 2013, 01:23:27 pm »
Oh, well in that case you should still be able to display the token fairly simply. Instead of using the variable itself, use the pointer of the variable holding the value, perhaps like:

Disp °T►Tok


And just to clarify, this behavior of ►Tok is not a bug, it does exactly what Commands.html says it should. :P

696
The Axe Parser Project / Re: Bug Reports
« on: January 25, 2013, 01:13:29 pm »
In what scenario are you trying to display this token? Usually tokens are displayed as part of a program or OS string, in which case you should have a pointer to the token. There isn't really much reason to be displaying a constant token, which I think should be the only time when you wouldn't have a pointer to it.

(If you're wondering why the command is like this, it's because there is a B_CALL to easily draw a token pointed to, but not one to draw a token itself.)

697
The Axe Parser Project / Re: Bug Reports
« on: January 25, 2013, 01:05:55 pm »
Just checking, you know that it displays the token pointed to, right?

http://axe.eeems.ca/Commands.html#textCommands

698
The Axe Parser Project / Re: Features Wishlist
« on: January 20, 2013, 04:34:07 pm »
ok, thanks for the info!
but I still think that it would be usefull to add.
Perhaps add an option to enable/disable it in the menu, so we can use Archived-editing hooks if we want?

If zStart exists on the calculator, that would still be used to edit the program from archive.

699
The Axe Parser Project / Re: Features Wishlist
« on: January 20, 2013, 11:59:22 am »
How about ++EXP? How many times has this been requested?

By EXP, I'm assuming you really mean {EXP}r? In which case, that's basically what {EXP}r++ is. The only difference is the return value, as this doesn't return either the old or new value of {EXP}r because it isn't optimal to do so.

700
The Axe Parser Project / Re: Features Wishlist
« on: January 20, 2013, 10:18:13 am »
I've got 2 new feature requets:
1) automatically unarchive the source code if there was found an error in it while compiling
2) making an automatic optimlisation for anything of the form {L1+CONSTANT}, I use that whole the time and I think it would comprimise tons.

Also, it would be nice to implement in the zip file, some links to handy sites, like this community and all kinds of export sites. I've found some, but it took me some time.
And just in case it hasn't been reported yet, in the commands HTML, there is a part of the site that will always be covered by the used header, so it is best to insert some new lines at the beginning.

1) I've been bothered by errors in archived programs a few times, so I see how this could be useful. I've added it to my to-do list.
2) The optimizer in general is a mysterious beast. I would love to add optimizations like that, I'm just not sure how easy it would be.

As for helpful links, agreed. And in regards to the commands file, what is being covered up? I see the header overlay, followed by a small amount of white space, followed by the first piece of actual content on the page (the System commands table).

701
F-Zero 83+ / Re: F-Zero Progress Thread
« on: January 19, 2013, 10:30:44 am »
Bump,

I just quote myself :P

Calc84maniac, I'd like to test the app corresponding to the latest screenshot, can you attach it or give a DL link for your fans pleaaase ? ;D
Also, why did I get a downrating for that ???

I'm guessing the reason calc84maniac hasn't provided a download for it already is because he doesn't feel that he's ready to. This is an extremely complicated and somewhat old project, so progress is probably slow. Posts like this pressure authors to work faster and push out a release, even if they don't feel prepared to.

702
The Axe Parser Project / Re: The BAD SIGNATURE error...
« on: January 16, 2013, 09:42:11 am »
Applications compiled with Axe are not signed on the calulator for reasons of signing complexity. To enable an application compiled by Axe to be sent freely to calculators, you need to sign it using a computer utility.

If you're on a Windows operating system, a utility to sign applications is included in the Axe download under Tools > Application Signing. Hopefully, it should be as simple as doing just what the batch file's name suggests.

If you're on a Unix operating system, the same base utility can be downloaded here, with which you will need to sign the application a bit more manually.

703
TI Z80 / Re: [Axe] KarRace
« on: December 29, 2012, 09:28:09 pm »
It looks like somehow the LCD's z-address got set to 1 (or is it 63?), which makes it so the whole screen is shifted down one row and the bottom one row wraps around to the top. Hopefully it was just caused by some random one-time thing, in which case you should be able to fix it by archiving anything you want to save and then clearing your RAM.

704
Axe / Re: Variable locations?
« on: December 27, 2012, 08:37:54 pm »
My bad, I had a parenthesis issue with the second one. That's one of the reasons why I'm still not happy that Axe allows you to leave parentheses unclosed like TI-BASIC, otherwise it would have thrown an error and I would have caught it more easily.

705
Axe / Re: Variable locations?
« on: December 27, 2012, 08:10:00 pm »
It seems to work fine when I run it; given Data(18,24,16,9,6,8,15,19)→S, I get:

  • C: 3
  • D: 3
  • E: 4
  • F: 4
  • G: 1
  • H: 3
  • I: 4
  • J: 1
  • K: 1
  • L: 1
  • M: 3
  • N: 1
  • O: 0
  • P: 3
  • Q: 4
  • R: 3

Are you sure you copied the code correctly? I can understand copying it incorrectly because the code is a little strange.

Pages: 1 ... 45 46 [47] 48 49 ... 153