Void Singer

I dunno about HULU, but netflix can get pretty close =X PS. this is exactly how the larger companies are intending to do an end run around net neutrality.... they'll offer up capped services, but then won't count their own towards your cap, and still charge you the same obscene prices

suspicisous activity alert, same two posts, posted to the same two boards, after the previous two were deleted, one of which had negative commentary (like this)

suspicisous activity alert, same two posts, posted to the same two boards, after the previous two were deleted, one of which had negative commentary (like this)

payment dialogs are controlled on a perviewer basis, which can be configured by each person.... in v2 those settings are preferences --> notifications --> tell me: [_] when I spend or recieve L$ (will turn them on or off completely) advanced --> debug --> UISndMoneyChangeThreshold (will control hom much money has to begiven or received at once to trigger a sound)

yup.... and if you want to cancel looking up or down, make sure to cancel the z component of those vectors.

Quinn Morani wrote: I don't think I've ever actually seen a live armadillo. Just roadkill. :smileyindifferent: come to think of it, I don't think I ever saw one live either when I lived there..... oppossums on the other hand... southern Alabama and Georgia are riddled with them (Mississippi and Lousiana , and north Florida too). they're what rats would be if infected with "rage" (28 Days Later) or T-Virus (Resident Evil)..... those suckers are meaner than badgers. and damn you furry felines, now I can't get out of my head

<p> the "target" is the frame relative (could be region for object roots, could be the root for child prims) direction you want the prim to face... for instance "north", so it's definitely counter intuitive for any use where you want it to track another object (because you first have to figure out what direction that object is from the prim that's calling it.</p>

I'm asuming the -Z axis is the same as the "point" on the heart? llEuler2Rot( <0.0, 0.0, 90.0> * DEG_TO_RAD ) * vRotAvatar; or more compactly, <0.0, 0.0, 0.7071067, 0.7071067> * vRotAvatar the singe axis formula for rotation is X,Y, or Z = sin( degrees / 2 ), and the unused two are set to 0.0. S = cos( degrees / 2 )

PeterCanessa Oh wrote: Void is particularly good at making things efficient although, for me, less readable so she might disagree with this but my recommended priorities for anything are: Make it work Make it clear Make it efficient actually no, I wholeheartedly agree with that, and only know of one exception to that list offhand.... and that's if it won't work unless it's efficient... and that really isn't much of an exception (it just combines 1 and 3) optimization is a funny thing, in that there are lots of things you can optimize for, and rarely do any of them go together.... speed, size, portability, readability, reusability... and chasing one often means ignoring another. my posts for this thread aren't aimed at OP really, but rather anyone reading.... the hopeful idea is to demo some structures and considerations that might be new to the reader, and get them more familiar and comfortable with them and how they work...

ingredients: Canadian Highway Canadian Rabbits Instructions: Wait for spring ... Seriously, they're worse than armadillo's in Texas, and apparently twice as dumb (the armadillo's at least have the excuse of being short legged and slow)

of course there's always the simple method of limiting chat to a particular table.... have the table use LLWhisper, and make sure other tables players are more than 10m away. the players can be detected for listening to them specifically by detecting when they sit.

another important distinction for loops is the order they do things in for: test run code modify test variable repeat do: run code test while: test run code repeat generally with the latter two the modification of the variable is done IN the test, or in the code, by default, and in for loops, it's done after the test and the code, which can make a difference in your counting logic. all three can be rewritten to mimic the others, by changing where the modification happens or adding wrapper code, but they'll be less efficient. do is technically the fastest loop type, but it's limited to cases where you know that you're going to have at least one valid test (the first one) while is the second fastest, only by merit of it being one test longer than do, assuming there are any valid tests (otherwise it's faster than do, because it doesn't run useles code) for is the slowest of the three, probably because of the extra declarations, but it is useful if you need to modify your test variable after the test AND code. it's also convenient (although more for languages that let you initialize the variable in the call) jump USED to be faster than all of them, but now seems to be in about third place generally, it requires an if test to be used as an exitable loop, although if you just jump with no test or exit clause, then the inffinite loop is faster than all the others.... there are also event loops, and event chain loops... the most notable one is calling a state change from state exit, which is blindingly fast for some reason. the same trick works for modifying a prim property from the changed event, or sending a link message to the local prim from the link message event, etc..... dataserver is the most common event to use this way, with notecard readers being the most obvious example. event chain loops are where one event triggers another one, in a daisy chain fashion, with the last in the chain triggering the first. they aren't very common, and the simplest example I can think of is an online indicator, where the timer event triggers the dataserver checking online status, and the dataserver changes the timer... although that's not a GOOD example. loops triggered outside of the script by interactions with the world or other scripts are considered to be "moderated" by their communications method, and are termed feedback loops (because they rely on external feedback) @Scion specifically: smaller is a quick indicator of speed, but not an absolute one. all the replacements I made are faster equivalents, based on knowledge, experience and testing, the suggestions on the other hand are based on knowledge of dealing with "unexpected" cases, some of which are actually expected if you are familiar with programming (because of knowledge of the basic action that can occur, but aren't always considered) and some are a result of unique "features" (mostly bugs and limits) of LSL, that have to be learned along the way (although we try to document them in the wiki.

the sad thing is I know exactly who you are talking about... just can't think of their name (ps, are you using an increased font size? because you signature images does not fit in the bounds of the default size)

good catch... the "1" should have been an "i" (I must have done that while I was adding all the color codes), I also double checked and caught a miscapitalized function call. but all are corrected and test now. (one day I'll learn to paste code into the viewer for a quick compile double check....) but good on you that you pulled the the line that error was on (I know we all wish more people that post would do that and/or understand what that means) PS the brackets are fine... do{ }while (); is an underused, but very useful loop construct (seems everyone like "for" better)

if you really care, flag it... you have your choice or "copy of delisted item" or "inflated price", both of which are disallowed practices.

pretty much the latter, or even a vehicle style AO... and it's never pretty... sad, but true

could be, I only have copies of the high rez basic clothing templates, and not the other specialty templates like the stripe guide, the normal maps, or the fake-n-bake templates.... I really wish I'd kept those as copies and not as links now =(

if anyones curious about how those wonderful skybox spheres are created, they use a particular type of panorama image, made with a fisheye lens, stitched together using hugin (usally, it's the only panorama stitching setup I know of that works for fisheye images.) with a finished image size ratio of 2:1 (they usually need some padding/editing at the top/bottom)... a good example can be seen here regular panorama images can be used but often require a lot more padding/editing at the top/bottom, especially if the depicted items are "near" the viewer, but mountain top, or high elevation scenes can often be reworked with little to no effort. once the image is completed, it's aplied to the inside of a hollow sphere (although a cut torus, or tube can work for some images)

that's why I like you Cerise... you find the cases I miss.... although, to be fair, it's not the loop causing that, but the flood of pending link_message events maxing out the event queue (which is only 64 deep)

PeterCanessa Oh wrote: @Void - [...] This is the temptation you earlier resisted, I take it? :-) [...] yup.... I had a feeling that it might go farther, and that it would be kept simple for OP (good things), so I didn't want to rush in before there was something to solid to build on. (I did that recently to Rolig, and I feel kinda bad about it, because it might leave the impression that I was trying to "one up" her)

PeterCanessa Oh wrote: I think I speak for most of us when I say that's more or less what we're here for :-) We all started programming, if not scripting, the same way. You are putting in enough effort and explaining your issues in enough detail that we aren't just doing it for you so, yes, we hope you and anyone else will learn from this. Continued good luck. seconded

those rules are designed for environments where the line count is much larger, and multiple programmers are looking at the same code, or there's a chance that the person who wrote it isn't going to be the same as the person who has to port it to a different language.... the idea is to make it as generic and easily modifiable as possible in those environments, to save time for other people so they don't have to back track the usage of a (supposedly) well understood variable before using it. those things can happen in LSL but are exceedingly unlikely compared to other languages, due to factors like size, ownership, and specificity.

there's one by chip midnight...... some where.... finding a still existing copy might be a quest though =( I'd try Robin Sojourners site first, but honestly I don't see it at a glance.... perhaps someone has a copy or a better link

Cerise wrote: Yes, attach() can be missed at rez time if the script was in the middle of a long loop when last saved. Independent confirmations are here and here. contrary evidence here. looks like we need to go and test use cases on this =/

according to some folks that type of parameter reuse is actually a violation of good practice. (and a step towards the REAL violation of good practice that Strife and I cooked up for those unsigned integer functions a while back) reason? because it doesn't let you just drop in other code that might look for the channel (for instance to send information back on the same channel), so it violates the expectation of what data is in that variable. technically the same is true if you use the do{ --num_detected; }while (num_detected); loop structure to process detection events, since it destroys your ability to know how many detections there were... to which I say, if you needed that you should have either A) processed that first (applies to both), or B) processed them inside the loop (applies to the seond only)