Howdy fellow Ferrengi Haters
I have been taking a break from staring at Delphi code all day and started to stare at some TWX Script Code.

I hope with this post to start a collection of TWXProxy Script snippets

So here is a little snippet of code that someone might find of use
All it does is "parse" a line of text and returns the first word in the text.
Simple isn't it... well it really does more than that as it removes the word it just found from the line so you can use it in
a loop to loop through the words in the line.

Requirements :
$String Line of space delimited whatever.... numbers and or words
Label named done:
Returns
$Word LeftMost word of $String
---------------------------------


an example would be

setvar $String "0 1 2 3"
gosub ParseString:
Echo $Word # will echo 0
gosub ParseString:
Echo $Word # will echo 1

Hopefully someone can find a use for this like I did...
I had some sectors that I needed to warp to and needed to script it so I developed this little snippet.

If you have any little tricks and or code snippets that might help someone please share

Maybe having more than 1 set of eyes on the code will result in an improvement or possibly a bug fix.

Neat snippet, why did you choose to cycle through the words instead of grabbing a specific word for your script? Did your sector number display vary? I don't really have anything to contribute that is not specific to a script, though I think getstats routines, etc would be of value here as a point of referance. I remember EP at one point did a getstats contest to see who could get the smallest working routine. I think something along those lines for a snippet that is used all the time is fun and interesting.

A quick and honest answer to why I cycled through them... My brain has seen too much alcohol.

I didn't want to have to keep track or even know in advance how many sectors were in the string.


EDIT....

I would prefer that this doesn't evolve in to a I can do that function in X lines....
Maybe I am old fashioned but I prefer readability over so called efficiency
Are there better ways of doing what I posted I sure as Hell hope so but I believe that this is
readable and someone can look at the code and see what I am trying to do.

Perhaps striptext is of limited value in a sector list..say a bubble list from swath.

setvar $string 1234 12345
striptext $string 1234

whats left is 5.

grab the length of the first word and cuttext from there to the end of the string

cuttext $string $temp $length 99999
setvar $string $temp
repeat

of course cuttext is a pain in the butt because you will have to test for zero etc. but its what u get for free.

Perhaps striptext is of limited value in a sector list..say a bubble list from swath.

setvar $string 1234 12345
striptext $string 1234
IIRC
no what's left is 12345 as we removed 1234 from the 1234 12345 string

whats left is 5.

and I avoid that by taking out the first word so I am stripping from the beginning to the
first space after the word...





grab the length of the first word and cuttext from there to the end of the string

cuttext $string $temp $length 99999
setvar $string $temp
repeat

of course cuttext is a pain in the butt because you will have to test for zero etc. but its what u get for free.

OK
What would you like to see as a replacement ?
Mean sincerely as this is what I need for possible new functionality.

Cuttext is a very nice command to have, and I haven't had any issues with it when I use it correctly. I don't use SWATH's bubble list at all since I wrote the bubble script (somewhere on here should be the source), so I really don't know the issues with that.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Any list of sectors or other info in a string as oppossed to a list (one piece of info per line)
take ck's supg's or rammer's fig list for example.
Bubbles are not the issue. Parsing the list is the issue.



Hmm...I dont think anyone has issues with anything when used correctly.



This will test your snippet and you will see the issue.
I will post something as soon as I get something working.

Hmm...I dont think anyone has issues with anything when used correctly.



This will test your snippet and you will see the issue.
I will post something as soon as I get something working.

Doh.... striptext will strip all of the matched word in the string.

Nice catch there... Course helps if you have a Birds-eye view of things.

I actually like "improve my code" conversations. Some of my best code snippets happen on the fly, with that random ICQ help request.

Anyway, I like your idea of sharing code snippets. I might try to do the same thing, only make it a "improve my code" thread. But since that is not what you are after, I'll just contribute my own code snippet.

keepalive - Sends ESC every 3 mins, which doesn't cause sector displays, etc.

fig refresh - small, efficient routine that populates $figGrid[sector] with deployed fig qty.
There is a slightly more efficient way to write that, but I think this way gives a better example of effective trigger usage, esp. where multiple triggers execute the same routine. For fool-proof scripting, you might add a delay trigger before any waitOn triggers, to regain control in case something goes awry.

Regards,
+EP+

Here is one I wrote a while back. It's seen several iterations, but here it is in it's most basic form:


It tries to fill your ship from sector fighters. I was just tired of doing it by hand.
I have a version of it tied to a hot-key as we speak

You can fix the striptext issue by using a leading and trailing space after the string, then simply replacing items delineated by the leading and trailing spaces.

One of my own favorite code snips I use in various forms: