Becka Aulder
-
Posts
13 -
Joined
-
Last visited
Content Type
Forums
Blogs
Knowledge Base
Posts posted by Becka Aulder
-
-
That is true enough. I agree that trying to anticpate all the ways a user can mess things up is an exercize in insanity. But we can try to anticpate the more obviouse ones -- the more common ones -- and take some proactive steps to take them into account.
As in your exmaple I have found that a simple trimming on both ends of the users input ( msg = llStringTrim(msg, STRING_TRIM); ) will take care of most things. It will remove the errant spaces at the beginning as well will removing any extra spaces at end of the user input along with the unwanted RETURN.
In this case, I do think that my input was constructive rather than nitpicky. Though in retrospect I should probably have done just a simple "trim all" in my example, but the original question was about securing just the first word with anything else on the line dropped onto the floor. I try, though, to point to the tools at hand let people explore further if they are curious to know more.
-
Rolig Loon wrote:Look for the first space?integer idx = llSubStringIndex(message, " ");string FirstWord = llGetSubString(message,0,idx);
One caveat about that bit of code. If your user decdies for whatever reason (including accidently) adds 1 or more spaces at the beginning, that routine will fail. The index of the first space will be zero so you will get a substring of zero to zero....which is nothing. You need to validate the entry if you have not already thought about it.
messge = llStringTrim(message, STRING_TRIM_HEAD);
//this will strip out all the white spaces at the beginning of the string
// then (and if you want to save a variable)
string firstWord = llGetSubString(message, 0, llSubstringIndex(message, " "));
-
A bit late of response to this one, but I second the suggestion to check out M.O.C.K Cosmetics. I find her work layers well with most skins and are reasonably priced (at least I feel they are). Hers is one of my favorite cosmetics in sl.
-
Yes, it is just 8 sliders. But my normal shape that I created when I first entered the world and have been happy with for several years is (according to the standard sizing): xS to S above the waist and M below the waist. When wearing separates it's not a usually an issue. A tiny tweak where needed soemtimes, sometimes an alpha (mainly on the bottom) and I'm good, and my look stays consistant. With a dress or ensemble piece I have to bite the bullet and go XS/S top to bottom. It's not a huge change but it is noticable and not a change I care for.
I really would like to see some method developed that will respect the sliders and we can do away with this standard sizing stuff. I stay away from a fair amount of mesh for because of this.
Also stuff needs the flexi component which mesh doesn't yet do. So for those 2 reasons for me it's not the end all thing.
-
A few of the sub processes don't want to cleanly exit and are still "running" even when the viewer isn't. I've had this error for different DLL's on various releases. Since the files are in use, they can't be opened for writing (or replacing as is the actual case) during the upgrade. Either fully reboot or open your task manager and manually kill anything in the processes list related to second life. (most often it'll start with "sl:" and in my case it's always SLVoice.exe Rerun the setup/install and it'll go smoothly.
Mainland Land Rights and Neighbors
in General Discussion
Posted
A bit late to the party, and I see a few have already done similar to this, but this is the sign I put out when I had a neighbor doing similar.
Granted the mesh came from a kit and so I never thought about trying to sell it on the cheap, but maybe I'll clean it up some, make the lettering look a bit more weathered, and do that.