Jump to content

Anna Salyx

Resident
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

14 Good

About Anna Salyx

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. use llSetLinkPrimitiveParamsFast with the PRIM_SPECULAR flag. It is more complicated than a simple stand alone 'set specular' command, but it'll get the job done for you. edit: and on a reread you do state you are new on scripting. The set primitive params set of commands has a bit of a learning curve on the syntax needed to make it work, but it can get into some of the deeper parameters of a prim that can't be done with any of the stand alone commands, and, as a big pus, it can do several all at once. That can be very useful at times. Tinker and play with it.
  2. I'd be interested in reading up more on the specifics of flag value 8. Do you know off the top of your head the jira or release notes addressing this? Thanks.
  3. As a side note from the linden question, unless you have a compelling need to permanently close the account, I'd suggest rather than cancelling, simply change the account type from premium to free/basic (if applicable) and clear out any payment methods (again if applicable) for security reasons, and walk away. Your avatar and all it's current belongings will sit idle and if in the future you ever decided to peek back in, you won't start wholly from scratch. I get it if you need for personal reasons to make that hard line account closure to reduce/eliminate temptation in the short run, but for me personally I've come to appreciate the ability to go visit some old haunting grounds after years of being away and have been very glad that my accounts/persona's have remained. Sometimes I'll only drop in, say hi, remember why it was I left and go away gain. Sometimes though, I go back and find it was time to pick it up again making a new chapter in that particular experience. In any event, I do wish you safe travels away from here and may y our path lead to you what you need or seek and with luck both are the same.
  4. I"m not discounting that. The first recorded usage for the term is from 1887. However, the fact that the Harley stock ticker symbol is HOG, and in relation to motor cycles specifically the word hog has a very strong association with the Harley-Davidson brand specifically -- coming from multiple angles. Right or wrong, the usage of the term might be one of the flags for which that claim is being applied. That is all I'm saying as a point of conversation and contribution. I could very well be in error, but it's something to at least consider.
  5. Adding a bit to the conversation before it gets too far into the past. Harley-Davidson's stock ticker symbol is HOG. H.O.G is the acronym for Harley Owner's Group. The word hog has become fairly synonymous with the Harley-Davidson brand specifically, and I don't know if it's not a trademark or not, or how much it as a term is officially tied to the the brand beyond the ticker symbol. I did see at least one of the listings used the term hog motorcycle ("Road Hog"). I've not gone delving into any of the listings to see how common that term is being used but it might be a key word term that is being used to flag motorcycle type products as infringing. Just a thought added to the conversation.
  6. Business need to access SPI (sensitive personal information) is usually limited within a company to those who are directly customer facing, that is sales and customer service representatives. The company I work for, even then in most cases when a sales rep or CSR is working with a customer they will state "I need to access your account to proceed, do I have your permission". I work in billing operations and I have zero access to customer accounts. I don't have a business need. But I digress: to answer your question, access to your SPI is most likely going to be limited to only those people who have a direct immediate need for it at a given point in time. Employees will probably have to access your private data through an internal gated system that prevents the average worker from seeing it.
  7. Pity. I had just really learned about this feature change not long ago. I saw it as a niche thing with a very narrow application. But that said, I was kinda kicking around ideas on how it might be used within that niche scope. I'd not gotten nothing past the concept/idea phase so no big loss of time or effort though. But to be clear, it's only the title/role change part of that feature that has been taken away, not the general group change command, yes?
  8. As far as I have been able to tell in some quick playing around is: One of the things I can see that will be different from the still being sold version and the free version is the associated experience key. The sold version will continue to be done up under the AVSitter experience key. Users of the opens source version will have to obtain their own experience personal key if they can and associate it there -- That is there wont be a nice blanket AVSitter experience regardless of the who makes the final product. It's a small thing but it can be a significant thing in terms of trust. If I ever start making anything for more than personal use, it might be something that will give me some pause to think about.
  9. Replying to Ivan. Do you have anything that is RLV locked to your HUD space? This will cause the behavior you describe. Don't know why, but it does. If you do have a HUD that is RLV locked, simply unlock before you enter edit mode and you will be able to zoom way out again. If you don't have such an item, then, sorry, I have no other ideas. Luck.
  10. Another method if you want a slightly simpler solution is to use the get and reset time functions. They count the seconds since the script was started or since the last time the timer was reset. It's a useful set of commands. I like the timer multiplex solution listed above and use it and variants of it frequently but for some thing it's jut a bit much when when one is looking for small and simple. So to adapt your script in another way would be like this: integer touchActive = FALSE; default { touch_start(integer detected) { if (!touchActive) { llWhisper(0,"Timer started."); touchActive = TRUE; llSetTimerEvent(300); //5min llSetLinkColor(LINK_SET, <0.180, 0.800, 0.251>, ALL_SIDES); // green llResetTime(); } else { integer elapsedTime = (integer)llGetTime(); llWhisper(0, "Timer active, " + (string)(300 - elapsedTime) + " seconds remaining."); } } timer() { llWhisper(0, "Timer ended."); llSetTimerEvent(0); touchActive = FALSE; llSetLinkColor(LINK_SET, <0.694, 0.051, 0.788>, ALL_SIDES); // purple } } You could of course put in some code to manipulate the out put so it shows minutes + seconds remaining, or any number of things. But the llResetTime(), llGetTime(), and llGetAndResetTime() commands are handing for getting quick elapsed counts that don't require a whole lot of overhead for smaller and simpler scripts where a multiplex approach is not really justified.
  11. The link above to the doc API will help, but the critical step is the llSay or llShout,or llWhsisper or llRegionSay, and even llRegionSayTo. It must be on the standard RLV channel, including the UUID of the target AVI and the command and parameters. The target avi *has* to be wearying a RLV relay device of some sort that is turned on and in either auto accept or ask mode. That is where the magic happens. The relay listens on the RLV channel, looks to see if the command is directed to its owner and then parses the command. You might be able to around all that with experience keys on the land. But that is a different topic and discussion. Hope that helps
  12. Three...now, but I think I saw some shuffling behind me. Or it might be zombies. Hard to tell sometimes...... /shrugs.
  13. And really the thing to keep in mind in the future is that it costs nothing to let your account set idle. If you find you don't have time to play for a while and if you are on a reoccurring payment plan, simply change that back down to a free account and walk away for a while. When you think you have time again and want to come back again later sometime in the future, just install an updated client and voila, you're back where you were and won't have to go get all setup again. Good luck with the support case and getting your account all safe and running again.
×
×
  • Create New...