Jump to content

Rolig Loon

Resident
  • Content Count

    40,225
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Rolig Loon

  1. Not hard at all. You read the card in a dataserver event that is built around code like this. list temp = llParseString2List(msg,["="],[]); if (llToLower(llStringTrim(llList2String(temp,0),STRING_TRIM)) == "product") { gProducts += [llStringTrim(llList2String(temp,1),STRING_TRIM)]; } else if (llToLower(llStringTrim(llList2String(temp,0),STRING_TRIM)) == "price") { gPrices += [(integer)llStringTrim(llList2String(temp,1),STRING_TRIM)]; } And so forth. When you reach EOF, go on to read the next card. When you're all done, you have the product names, prices, and everything else in parallel global lists. When you need to get the price of something, look for its name, find its position in the gProducts list, and then use the same index to find the price in gPrices.
  2. This is a resident-supported Answer site. If you'd like to start a discussion, please try the General Discussion forum.
  3. This is a resident forum. There are no Lindens here. If you have a suggestion that could improve SL, the best way to submit it is to create a case at http://jira.secondlife.com. In the upper right corner of that site, check the +Create Issue link and then select Project: Second Life Service, Issue Type : New Feature.
  4. You'll have to talk with someone in LL's billing office to figure out what's the matter: Toll-Free (US/Canada) 800.294.1067 Long-Distance 703.286.6277 LL's Billing team is available 24 hours a day, seven days a week. Local Toll-Free numbers * France: 0805.101.490 * Germany: 0800.664.5510 * Japan: 0066.33.132.830 * Portugal: 800.814.450 * Spain: 800.300.560 * UK: 0800.048.4646 * Support is in English Only
  5. Try again. That's the number listed on LL's support page (https://support.secondlife.com/billing-support/), and other people have been getting through.
  6. You don't need a mesh-enabled viewer. If you use Phoenix, you just need to go into Preferences and enable the 64m-prim option. Some other viewers may also have that option built in. Regardless of which viewer you are using, however, you can also change prim sizes with a script like this one .... vector gSize;default{ state_entry() { gSize = llGetScale(); llListen(34,"",llGetOwner(),""); } listen(integer channel, string name, key id, string msg) { integer idx = llSubStringIndex(msg,"="); if (~idx) { string Axis = llToLower(llStringTrim(llGetSubString(msg,0,idx-1),STRING_TRIM)); integer ChAxis = llListFindList(["x","y","z"],[Axis]); float Dim = (float)llStringTrim(llGetSubString(msg,idx+1,-1),STRING_TRIM); if(ChAxis == 0) { gSize.x = Dim; } else if (ChAxis == 1) { gSize.y = Dim; } else if (ChAxis == 2) { gSize.z = Dim; } else { llOwnerSay("Error: Axis not recognized. Your message must be in the format \"X = 50.0\"."); } } else { llOwnerSay("Error: There must be a \"=\" sign between the axis label and the dimension."); } } touch_start(integer total_number) { llSetScale(gSize); llOwnerSay("The prim's size has been reset to " + (string) gSize); llSetTimerEvent(300.0); } timer() { llOwnerSay("Resizing is complete. Cleaning up now."); llRemoveInventory(llGetScriptName()); } changed (integer change) { if(change & CHANGED_OWNER) { llResetScript(); } }} Just drop it into a single prim that you want to resize. Then type new dimensions in chat in the form /34 X = 50.2 or /34 Y = 22.9 or /34 Z = 38.7. Click on the prim to resize it to your chosen dimensions, up to 64m in any direction. The script will remove itself after 5 minutes.
  7. See >>> http://community.secondlife.com/t5/Technical/Why-does-shiny-new-Viewer-3-install-with-an-icon-that-says-quot/qaq-p/1056603
  8. If you have already paid for the items, it may be easiest to send the merchants a polite message explaining what happened and ask for redelivery. Most merchants will be sympathetic. Don't be surprised if it takes a day or two, or if you have to send a gentle reminder later. Not everyone comes in world every day, and it is summertime.
  9. Si vous avez été seulement suspendu de SL pour une courte période, le message e-mail de LL devrait avoir expliqué quand vous serez autorisé à rentrer (14 jours?). Ne soyez pas surpris si cela prend un peu plus longtemps. Vous pouvez envoyer un ticket au support avec une question poli si vous n'avez pas entendu dans les quelques jours de plus.
  10. Take a look at this article on the Phoenix wiki >>> http://wiki.phoenixviewer.com/doku.php?id=fs_media&s[]=webkit . It gives the best set of instructions I have seen for dealing with the Webkit error.
  11. Oh, my. We get one or two people a month who have been robbed by this scheme. It's been around since the beginning of SL. Unfortunately, there's not much hope that you will get your L$ back. You can file an Abuse Report, of course, and provide as much information as possible. As you noted, the person who took your money has apparently left SL, but he had to have given the money to someone else to cash out, because there's no way to export the money in less than a few days. LL may be able to track the transactions. The big problem is that if you look in your own transaction history it will probably be recorded as a gift of L$24,000, and each step in the crook's money laundering will mix your "gift" in with other funds. It can be very hard to figure out what was stolen from whom. LL didn't take your money, BTW, so don't expect them to reimburse you unless they can get it out of the crook. For the future..... Nobody can take your L$ without your permission. When you rez an object that wants to take money from you, it always pops up a yellow box that asks if you want to give XYZ person permission to debit your account. If you don't know XYZ person or don't understand why s/he wants your money, don't click the Permission Granted button. Delete the object and delete all copies of it in your inventory so you don't inadvertently pass it along to someone else.
  12. Make a free phone call to the billing office. They'll help you straighten it out. Toll-Free (US/Canada) 800.294.1067 Long-Distance 703.286.6277 LL's Billing team is available 24 hours a day, seven days a week. Local Toll-Free numbers * France: 0805.101.490 * Germany: 0800.664.5510 * Japan: 0066.33.132.830 * Portugal: 800.814.450 * Spain: 800.300.560 * UK: 0800.048.4646 * Support is in English Only
  13. True..... mirroring the list would be the simplest solution. Didn't think of that. Hehe.
  14. If you want to play a game in SL, use the Search function in your viewer to find one. Open Search and click on Events in the list on the left side of the window. When the detail window opens, select Games/Contests. (You could so the same thing with Sports, if that's the kind of game you are after.) You can refine your search by clicking "Happening Now" or by specifying a start time. The Search function will give you a list of all the places where games or contests are being held that meet your criteria. You'll usually find plenty of people at places where there's a game of some kind.
  15. See? I knew it could be more compact. :smileytongue: I still like your trick of reusing the channel number as a flag. BTW, the OP's script reads list a forwards and then in reverse, then pauses for a bit to rinse and then recycle. I missed the forward and reverse behavior myself at first.
  16. Yup. And using llGetTime works too. I couldn't see any good reason for using multiple states in the OP's original script, though. Doing it that way means duplicating some events in the extra states, and IMHO they can look clunky. A script with tighter logic is more efficient, easier to read, and prettier. The OP's script also created extra global variables by unpacking list a in the state_entry event. There are several ways to look at this. If list a were long and complicated, he might do better to unpack it one time, in a setup state. Here, however, it makes more sense to read from the list each time around, but do it in the timer event. That not only saves making the extra global variables, it also lets you choose which single element to read each time the timer event is triggered, instead of having to read every one each time around.
  17. Or try this way, which is much shorter and gets rid of the state changes and several variables .... list a = ["a","b","c","d","e"];integer chan = 1;integer UP;integer count;float nwait = 3.0;float lwait = 10.0;default { state_entry() { llOwnerSay("Starting"); llListen(chan, "", llGetOwner(), ""); UP = TRUE; llSetTimerEvent(nwait); llSay(0,"I am ON"); } listen( integer channel, string name, key id, string message ) { if(llToLower(message) =="off") { llSetTimerEvent(0.0); llSay(0,"I am OFF"); count = 0; UP = TRUE; } else if (llToLower(message) == "on") { llSetTimerEvent(nwait); llSay(0,"I am ON"); } } timer() { llSetTimerEvent(nwait); if (count < 4 && UP) { llSay(0,llList2String(a,++count)); } else { UP = FALSE; llSay(0,llList2String(a,--count)); if (!count) { UP = TRUE; llSetTimerEvent(lwait); llSay(0,"Pause...pause....pause"); } } } } Yes, I know it could still be made more compact. EDIT: I forgot that you wanted it to restart the cycle when you toggle it OFF. Fixed above.
  18. See Cinn's answer on your identical, original post >>> http://community.secondlife.com/t5/Everything-Else/please-check-it-out-very-supprised-your-infomation/qaq-p/1061847
  19. I had exactly the same experience several months ago and had forgotten about it until I saw your question. I still do not know what caused it, and would love to hear a technical explanation from someone with more experience in SL photography. Unfortunately, I also not not know what cleared it up. I have just tried taking a series of test pics in PNG, JPG, and BMP formats, enabling and disabling the usual suspects in Preferences >> Graphics (VBO, HTTP Textures, anti-aliasing, anisotropic filtering) and I can't reproduce the waterless, skyless error again. All I can suggest to you is that some of your user settings files may have been borked. You can try deleting some or all of them and forcing your viewer to rebuild them when you relog next time. See >>> http://wiki.secondlife.com/wiki/User_settings . You might also try simply clearing your cache manually to see if that helps.
  20. We are not Linden employees here. This is a public forum and we are all SL residents like you. If you have a billing problem, the smartest thing to to is to telephone the LL Billing Office. If you are seeing small withdrawals from your account, I suspect that you belong to one or more groups in SL that charge you a share of their expenses. You can find out who you are paying money to by going to your Dashboard at http://secondlife.com and then checking Account >> Transaction History. The records there will tell you where your money has gone for the past 30 days. Toll-Free (US/Canada) 800.294.1067 Long-Distance 703.286.6277 LL's Billing team is available 24 hours a day, seven days a week. Local Toll-Free numbers * France: 0805.101.490 * Germany: 0800.664.5510 * Japan: 0066.33.132.830 * Portugal: 800.814.450 * Spain: 800.300.560 * UK: 0800.048.4646 * Support is in English Only
  21. The easiest way to get money in SL is to buy it. You can earn money a lot faster in RL than you can in SL, and you won't be spending your in-world time doing it. Once you have L$, walk into any shop in SL and buy what you want.
  22. You have to do that yourself. See >> https://secondlife.com/my/account/cancel.php?lang=en-US
  23. Stand in your home and open the World menu at the top of the screen. Select Set Home Here. After that, any time you want to go home, all you have to do is type CTRL + Shift + H. Once you have done the Set Home Here thing, you can also designate that spot as your default login location in Preferences >> General .
  24. LL has been doing a lot of work on servers for the past day or two, and they just rolled out their new viewer version too. We're likely to see odd behavior for the next couple of days until things settle down. I'm seeing slow rez times and script compilation times too. Patience.
  25. There are way too many possible reasons, given just that small amount of information. All graphics cards are not created equal. Some are better suited for SL than others. All CPUs are not created equal either. You might be using a wireless connection, which gives a lot of people trouble. You might have other programs running in the background (antivirus, e-mail, browser, ...) that are using processor time and memory. You could have a slow internet connection. You could be carrying too many scripted objects on your avatar. You could have your draw distance set way too high. You could be spending your time in crowded sims with loads of textures (a mall will do that). See >>> http://wiki.secondlife.com/wiki/Lag
×
×
  • Create New...