LSL-Editor

Can I suggest you check http://www.lsleditor.org/help/knownissues.htm.
I think this is covered there.

had no idea about the link. thanks.

I'm using the well documented method of calling a state from a global function, something like

MyFunction(integer condition)
{
     if (condition)
     {
          state newstate;
     }
}

However the LSL compiler complains with the error message:
'state(string)' is a 'method' but is used like a 'type'

This compiles perfectly fine in the SL editor in world and executes as expected. I saw another post about this but it really didn't say much about what to do about it. Is there a work around to get to to work in the LSL Editor? My actual function contains more code and is called from several places, so I would rather not have to expand this everywhere it is called since the script is already pushing memory limits. If it works in SL it should not be rejected in the LSL Editor.

Interestingly if you change newstate to default you get a different error.

As the wiki on State states:

Q: Can I switch states within a user-defined function?
A: For all intents and purposes, no. There is a way to do it, though it is officially unsupported and may be broken at any time in the future.

Thats the main reason I don't fix it in LSLEditor.

The error is not a nice one, it just coughs up some internal thing, that can be improved, refering to the reason why it is not fixed..... good idea.

But the error keeps me from debugging the program and therefore I can't use LSL editor any time I use a state change in this way. Is there a way to just ignore it?

NOPE

While scripting & testing just put your if test and state change in the event itself instead of calling out the global. Once everything is up and running then you will just have to uncomment a handfull of lines and comment out the if test and state change in the event.

//test()
//{
//	state other;
//}

default
{
	state_entry()
	{
		llSay(0, "Hello, Avatar!");
	}
	touch_start(integer total_number)
	{
		//		test();
		state other;
	}
}

state other
{
	state_entry()
	{
		llSay(0, "Touched: ");
	}
}

Thanks Jesse. I'd like to suggest a change to LSL Editor that would allow the user to ignore non-critical errors like this and still be able to step through the debugger. This would involve defining a set of such "errors" or warnings and allowing the user an option like "Disregard Warnings".

I would like to second that especially the bit about stepping through the code.

As of today release 2.28 of LSL-Editor can be downloaded (or let the auto update do the job).

LSL-Editor: is a standalone Windows "Editor / Compiler / Debugger / Syntax checker / Runtime environment" for Second Life scripts, based on .NET framework. Because it does not need Second Life grid nor viewer, it is very useful when the grid is down for maintenance, or when you are not connected to it. It can compile and execute many LSL scripts, but also the code completion, features make it a "must have". An HTML Help LSLWiki can be downloaded and used within LSLEditor to make this a true offline working environment.

This update has new implementations of llHTTPRequest, llGetWallclock and llGetGMTclock, fixed some crash problems, cleaned some code to pass more of the "LSL_Language_Test", this is not finished, but it is more equal to the in-world output. And a few minor changes to the editor such as INS/OVR and a total char counter on the status bar.

Thanks to all the beta testers and special thanks to the people who made donations to the project. It is really appreciated. All remarks on this thread are noted.

I am testing a forum on the LSLEditor website. Everyone is invited. Have a look at: http://www.lsleditor.org/forum/

Happy programming.

Just downloaded and used LSLEditor and tried out my Vendor script. It is fabulous and thank you for leading me to it; this will be a huge asset. I had a couple of questions in using it and would appreciate the help:

1. My script uses the llSameGroup function. This works great in SL; but in LSLEditor, it says user "unkown"; how do I get LSLEditor to simulate a different avi (other than myself) that triggered the event, and how do I set the avi to have the same or different group as the object in which the script will reside? Likewise, how do I assign the group (in LSLEditor) to which the object holding the script will be set in SL?

2. LSLEditor settings, in the Options for Debugging, am I supposed to place MY Avatar name, key, RegionName and RegionFPS (since I am the owner of the object), or am I supposed to enter the information of the avi that is "simulating" triggering the script/event?

3. Likewise, for the Options for Debugging, SMTP - do I put in MY information, or that of the avi that is "simulating" using the script?

4. I assume the Debugging, External options refer to my computer (if applicable); it wouldn't make sense for it to be anyone else's info.

Thank you.

@Amor: LSLEditor's compliance to LSL isn't perfect, especially when it comes to the functions that interact with the world.

But since you've posted about this deficiency, Alphons will likely come up with a way to solve it.

So I see in the preferences this enticing section on version control with a place to fill in the path to a subversion client . . . but it's all inactive. Is this feature on its way in or on its way out?

Just adding my pretty, pretty Please to this request
I already use my Pocket PC for joting down script snippets whilst im on the road, If i had even a partial implimentation of LSLeditor on it too, the posabilitys would be incredible.
I could even use my PocketPC to control inworld objects via scripts instead of email as I do now


Keep up the great work, and don't forget to take time off for christmas, only 1 week to go.

The version control is on it's way in, according to Alphons' earlier posting, so what you see is a precursor to it's implementation in the future.

Greetings All,

Just spent 2 hours tearing my hair out over a silly mistake on my part, as it used to work, and still does in world, but not in LSEditor I thought I had beter warn others

this code:

// www.lsleditor.org by Alphons van der Heijden (SL: Alphons Jano)
list tstlst;
default
{
state_entry()
{
llListen(PUBLIC_CHANNEL,"",NULL_KEY,"";
}
listen(integer channel, string name, key id, string message)
{
llOwnerSay(message);
tstlst=llParseString2List(message,[" "],[""]);
llOwnerSay(llList2CSV(tstlst));
}
}

fails silently when run, however, removing the null-string works fine.

i.e. tstlst=llParseString2List(message,[" "],[]);

ok, now back to my scripting

Thanks Very Keynes for finding the bug on llParseString2List. It looped the function when feeding empty strings. It is solved in the next release.

As of today release 2.30 of LSL-Editor can be downloaded
(or let the auto update do the job).
This will be the last announcement on this forum on the LSLEditor project.

All future LSLEditor related information is available on the official LSLEditor forum
which was in beta test the last few weeks. Thanks to the beta testers. The new forum can do bbcode (which is turned off on this forum for almost 1 year now!) Also code is presented more or less as lsl highlighted code, without the 'php' flag. Everyone is invited to register and join in. Suggestion are welcome.

Main lsleditor website is still at:

http://www.lsleditor.org/

And the new forum is located at:

http://www.lsleditor.org/forum/


Thanks to all beta-testers of LSLEditor the last year. And special thanks to the people who donated to the project which keeps my site up-and-running in 2008.

Happy programming!

-Alphons.

YAY!

It doesn't support the "print" keyword.
https://wiki.secondlife.com/wiki/print

Problems in integer land... again.

default
{
    state_entry()
    {//You would think that both numbers output by the llOwnerSay would be the same, you would be wrong.
        integer a = 0xEFBFBD00;
        integer b = (integer)"0xEFBFBD00";
        llOwnerSay(llList2CSV([a, b]));
    }
}

I'm just interested.
How did you discover this error?

For fun I program. I mostly do functions that deal with encoding and decoding. I have written about a half dozen hash/encryption libraries.

This specific one I discovered while porting an Escape & Unescape functions from LSL. You see LSLEditors core functions aren't 100% compliant and in some cases fail horribly. Incidentally I have a small swath of encoding and decoding functions I had written for my encryption libraries so I reimplemented one of the broken core functions (llUnescapeURL, which incidentally didn't work any better because llBase64ToString is equally impaired when it comes to UTF-8 characters). As a result of trying to port those two functions I have discovered 7 unique bugs (and a 8th bug I found while working on an unrelated function).

I agree it is fun to program. At the present count I have a smattering of knowledge of about 7 or 8 different languages. 1 or 2 in depth the rest for interest and comparison.
Scripting for SL gives me the opportunity to let others try my creations (breaking them in the process from which I learn).
I am sure that you have reported these variious failings to Alphons and he will be working hard to correct them. Incidentally did you know about the new forums he supports at www.lsleditor.org?

Yep, I posted the bug thread just after posting my previous message here. I use BlindWanderer there.