• Axe Parser 5 1
Currently:  

Author Topic: Axe Parser  (Read 387542 times)

0 Members and 1 Guest are viewing this topic.

Offline Matrefeytontias

  • Axe roxxor (kinda)
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1982
  • Rating: +310/-12
  • Axe roxxor
    • View Profile
    • RMV Pixel Engineers
Re: Axe Parser
« Reply #2175 on: January 29, 2013, 08:40:28 am »
Bump,

in fact it's not ok :P , can someone describe the protocol used by the Send() command ?

Also, still not changing the old poll ? ;D

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Axe Parser
« Reply #2176 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.
« Last Edit: January 29, 2013, 01:59:17 pm by Runer112 »

Offline GamerMX1248

  • LV1 Newcomer (Next: 20)
  • *
  • Posts: 5
  • Rating: +0/-0
    • View Profile
Re: Axe Parser
« Reply #2177 on: February 01, 2013, 10:06:10 pm »
Is there a way to split several strings without assigning several static variables.
Right now i have to do this:
Code: [Select]
"Easy"->Str11
"Medium"->Str12
"Hard"->Str13
So that when i want to irritate through several strings separated by a '0' using stdDev(, I reference Str11.
But i'd rather do something like
Code: [Select]
"Easy*Medium*Hard"->Str1 Where * is some kind of special character that is replaced by the string termination character.
Is there a way to do this in Axe, or some other easier work around to save on variable declarations and reduce typing time?
I've got a big project that will involve lots of irritating through sets of text, so how I'm currently doing it will take much longer than i'd like to invest in it.

Thanks in advance

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Axe Parser
« Reply #2178 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]
« Last Edit: February 01, 2013, 10:59:20 pm by Runer112 »

Offline GamerMX1248

  • LV1 Newcomer (Next: 20)
  • *
  • Posts: 5
  • Rating: +0/-0
    • View Profile
Re: Axe Parser
« Reply #2179 on: February 02, 2013, 02:19:14 pm »

Thank you. This will make my project so much easier

Offline DJ Omnimaga

  • Former TI programmer
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55927
  • Rating: +3152/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • DJ Omnimaga Music
Re: Axe Parser
« Reply #2180 on: February 10, 2013, 05:00:25 am »
I don't know if voting is over, but I wonder if Horiz and Vert would be confusing with the shift commands that already use Horizontal/Vertical? I was gonna vote using G-T and stuff, but then thought people might confuse Horiz and Horizontal, for example, so I would choose HLine and WLine. That said, source would be slightly larger due to the extra letter prefix. As for the other I guess letter modifiers or an extra argument would work, like xLIB. Disregard this if the update is already done, though.
« Last Edit: February 10, 2013, 05:01:48 am by DJ_O »


Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Axe Parser
« Reply #2181 on: October 29, 2013, 04:25:38 pm »
I made a small update to Axe 1.2.2, fixing a bug with the formatting of error dumps. It wasn't at all worth making a new major release for, but I did replace the Axe 1.2.2 download with the updated version.

If you don't plan on dumping any errors, don't even worry about this update. If you do, but a bit of weird formatting isn't a huge issue for you (the dump is still fine I think, it's just formatted oddly), don't worry about this update, either. But if you do want properly formatted error dumps, grab the fixed version in the latest updates thread.

Offline Matrefeytontias

  • Axe roxxor (kinda)
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1982
  • Rating: +310/-12
  • Axe roxxor
    • View Profile
    • RMV Pixel Engineers
Re: Axe Parser
« Reply #2182 on: October 29, 2013, 04:37:22 pm »
And about the app generation bug ? Is it still unresolved ?

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Axe Parser
« Reply #2183 on: October 29, 2013, 04:39:33 pm »
I'm of the opinion that your archive was just a bit messed up and that it wasn't Axe's fault. :P You should try Axe 1.2.2 again, and if it still doesn't work and you send over Calcsys as well, I can try to help debug it further.

Offline tpt1234567890

  • LV3 Member (Next: 100)
  • ***
  • Posts: 45
  • Rating: +0/-0
    • View Profile
Re: Axe Parser
« Reply #2184 on: October 29, 2013, 05:39:10 pm »
I'm of the opinion that your archive was just a bit messed up and that it wasn't Axe's fault. :P You should try Axe 1.2.2 again, and if it still doesn't work and you send over Calcsys as well, I can try to help debug it further.

Thanks for this! My archive messed up right after I read this, and it fixed it!

Offline nikitouzz

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 215
  • Rating: +22/-1
    • View Profile
Re: Axe Parser
« Reply #2185 on: November 09, 2013, 10:48:56 am »
Couldn't you keep the current line routine and add one that clips ? :) please !
« Last Edit: November 09, 2013, 10:55:12 am by nikitouzz »
mes records personels :

2x2x2 : 2.18 secondes / 2x2x2 une main : 21.15 secondes / 2x2x2 yeux band├ęs : 47.59
3x3x3 : 5.97 secondes / 3x3x3 une main : 49.86 secondes
4x4x4 : 1.49 minutes / 4x4x4 une main : 6.50 minutes
5x5x5 : 4.10 minutes / 5x5x5 une main : 18.02 minutes
6x6x6 : 8.10 minutes
7x7x7 : 16.03 minutes
9x9x9 : 58.26 minutes

megaminx : 5.59 minutes / pyraminx : 7.91 secondes / square-one : 1.07 minutes

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Axe Parser
« Reply #2186 on: November 09, 2013, 03:04:07 pm »
Clipped lines are tough (to do optimally in assembly, at least) and I've been dreading coding them forever. But I'll bump it up on my priority list and try to force myself to implement them sooner rather than later.
« Last Edit: November 09, 2013, 03:04:48 pm by Runer112 »

Offline Matrefeytontias

  • Axe roxxor (kinda)
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1982
  • Rating: +310/-12
  • Axe roxxor
    • View Profile
    • RMV Pixel Engineers
Re: Axe Parser
« Reply #2187 on: November 09, 2013, 03:31:53 pm »
I did a pretty fast and optimized line clipping in Axe, maybe I can try to port it in ASM.

Offline Streetwalrus

  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3821
  • Rating: +80/-8
    • View Profile
Re: Axe Parser
« Reply #2188 on: November 11, 2013, 07:08:02 am »
An idea would be to add a check whether or not you are on the screen while drawing. Though if you have a huge portion of the line off screen that'd be very slow. :/

Offline Matrefeytontias

  • Axe roxxor (kinda)
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1982
  • Rating: +310/-12
  • Axe roxxor
    • View Profile
    • RMV Pixel Engineers
Re: Axe Parser
« Reply #2189 on: November 11, 2013, 07:23:56 am »
The fastest line clipping code I saw in action actually took 2 coordinates, like a classical line routine, but then performs some mathematics based on cartesian equations to "keep" the points in the drawing window while not altering the "slope" of the line.

Sorry for the poor explanation, English is not my first language :/

This page will explain better than me : http://lodev.org/cgtutor/lineclipping.html .
« Last Edit: November 11, 2013, 07:24:11 am by Matrefeytontias »