ellestones

agree with @Tari Landar @Derekmate try not to get caught in between at the outset. Can easily end up on a road to everywhere leading to nowhere. Pick one road or the other. When you get to the end of that road, then like Tari says you can always travel the other road

what i said was a factual statement. How we feel about factual statements is also what makes us human. How we feel can also guide our guess work look at again please at what Samantha said. It would be unfair if we couldn't Samantha's qualified her feelings with: 'if we couldn't.' Samantha in so saying is aware that this is a potential future which she doesn't want to happen which is were I came in. Better to complain about a future before it happens, than after it happens millenium snowflake? really Alwin, seriously

that we feel is fundamental to being human. Expressing our feelings is also fundamental. That another people's expression of their feelings is seen as inconsequential whining, is how you feel

hmm! paraphrasing Edgar Howe: "Complaining is the politest form of fighting for what we would we like" i agree with @SamanthaPrater that last name changes be open to all residents. I would prefer not to complain about it afterwards, should this not happen. I prefer that it be complained about and fought for beforehand

a court-like group dance machine. Where you change partners during the dance i think about making this sometimes. It just keeps slipping down my list of everything yet to make. So if anyone else is up to making this (if it hasn't been already) then it would be good. As I think it may help to ameliorate the shy wallflower effect

suggest that you file a support ticket. It may be that your access flag is set wrong. LL support will sort it out for you

yes it makes sense in constructing (word arrangement and punctuation) your grandmother's spoken words then I suggest that you visualise her speaking to you. When she spoke where did she pause i think in this case it is more about how your grandmother spoke, her own use of grammar, as you remember it, than it is about anyone elses' grammar. Be true to your grandmother as best you can and all will be well. Even when the world has now changed and will be different for you for ever more

as a reason this makes sense. Why this is the reason may not make sense today from an actionable user pov, it made sense on a previous day from a database administrator pov. Database normalisation and all that i add on here a please-linden if lastnames are to be once more be picked from a pre-defined available name list then after entering our first name can we please get a paged list of all last names available. Not a random subset of available last names as was done previously. Having to refresh a random list is not good when searching for a particular last name. I get that web tech in a previous day made paged lists problematic. Today not so much if at all

knowing the circumstance, I get what you want to impart i would suggest to avoid using the words not and but. Examples: "in your final moments, you are, to me, who you have always been" "in our final moments, we are as we have always been"

@Animats and @Ana Stubbs is true it can be painful when a creator disappears from SL i think the problem issue is that even when a person cancels an account, they can still come back at some future date and resurrect/reopen the account. LL has a provision for us to do this. Am not sure what the outcome might be if a person did reopen and found the permissions of their created stuff changed unilaterally by LL

thats how SL works normally. If you (or your script) can't see another person, then you can't see what they are wearing if you want to see what your friend is wearing who is not within your (or your scripts) view then you will need your friend to wear a script (or use a custom-made viewer) that communicates with an external-to-SL server that you own and/or have access to edit add: just to be complete. The custom-made viewer and/or script that the friend is wearing can alternatively communicate info via Instant Message, obviating the need for an external server

if what you are looking to do is create a dialog menu system for your app then you might be better off looking at an existing complete dialog menu code, and retrofit/mod it into your app is a few of them available. A good one to get started with is here:

if you are going to use multiple list variables then you're stuck with 'if else' clauses, as LSL doesn't allow us to use pointers to keep your code tidy then I suggest wrapping all the 'if else' clauses in a function. Example: list getListByName(string listname) { if (listname == "List1") return List1; else if (listname == "List2") return List2; else if (msg == "List3") return List3; else return []; } listen (integer chan, string name, key id, string msg) { list m = getListByName(msg); // do something with list 'm' if (m != []) llOwnerSay("[" + llDumpList2String(m, ",") + "]"); } edit: is a typo in code snippet: msg == "List3" should be listname == ...

how much data in the lists ? if you can fit it all in to 1 list then can look at it as a strided list: http://wiki.secondlife.com/wiki/LlList2ListStrided if you get stuck then give an example of what your list length might be and we can help work out what approaches are open to you add also are List1, List2, List3 of equal length, do the elements of each seperate list constitute a data record ?

the listen parameter 'msg' contains the string caption of the dialog button pressed in your case, you will need an 'if else' clause. Example: listen (integer chan, string name, key id, string msg) { list m; if (msg == "List1") m = List1; else if (msg == "List2") m = List2; else if (msg == "List3") m = List3; // do something with list 'm' if (m != []) llOwnerSay("[" + llDumpList2String(m, ",") + "]"); }

if you can guarantee 40-50 customers tipping me 200-500L each per set then sign me up

making my 200th post

hardstyle doesn't have a wide following in SL. Is a few people into it tho, in the same way there a few people into southie rap or death metal or any other tight scene this said. When crafting your club parcel description use descriptors that you know people who are into hardstyle will know. What people know is what they search on the other big thing is to make a group and engage yourself in the group chat. Use the group chat as a chat channel, both for yourself and the group members. Not just about club or scene activities, for general chat as well. Get friendly

i don't get this line of reasoning if it's true for last name selection, it's also true for first name selection

idea loading... please wait love it

my approach to integrating RLV and/or AVSitter with an Experience i use the Experience KVP to provide LSL-accessible gameplay levels that we can't access in standard groups for example: A room/space of devices controlled by a sign-in/out board (touch or collide to sign in/out). Sign-in to the board and choose your level. Play on the devices as dom, sub, either. Anyone can join me. Only those I invite, etc. My level is red (full-on adult) or white (neutral PG-ish), etc scripting-wise I use either RLV, or AvSitter or own custom Experience for the actual play on the devices. I tend not to mix them together in the same device. It can get messy when not careful. I prefer to compartmentalise as often as possible, where ever possible for AVSitter beyond G, I tend toward using the opensource repository. Customising these scripts as/if needed edit add: Just to make it clear 1) Person has to join the Experience 2) Person also has to join the room/space experience by signing in to the controller board this allows different levels of experiences within the Experience

what you @Phorumites raised I think was worth exploring as a topic. Am always interested in what could be, what might be, if so how could it be done, if not then why not and what might the alternatives be if any particularly when something isn't working as well as hoped. Mainland occupancy in this case. LL have decided to try a more comprehensive auction system at this time. It may help, it may not. Should it not then your idea of LL selling mainland parcels for 1L per may eventuate an alternative future could also be: a LL declaration that the existing no-covenant mainland will not be extended. What there is, is all there is and it will stay that way (after a little tidy up on some edges of existing continents - Sharp continent for example). A declaration that from hereon the only new LL-owned mainland continents introduced to the grid will be covenanted continents (Linden Homes - Horizons model) targeted solely at growing the premium membership when the existing no-covenanted mainland is not extended (and never will be) then like realworld land it becomes a limited resource. Limited resources can have value in and of themselves

i don't have group, display or account names visible in my view i just think its weird to want to immediately know the names of people in my view. If I do want to know then I cursor over them. Which I don't do often as I usually don't have any reason to want to know in most of the situations I am in i get tho that is lots of situations where over head name tags are useful. For hosts, greeters, teachers, performers, event organisers, landlords, etc

or you arrive, Object Entry is allowed, but the sun god has banlines up

another parcel management supply tool is differential tiers/rates/rents. Private estates do use this tool. The rent for water edge parcels is typically higher than the rent for interior parcels on the large estates should LL do this also on mainland ? if so then this would be a further radical change