Jump to content

Anna Salyx

Resident
  • Content Count

    54
  • Joined

  • Last visited

Community Reputation

58 Excellent

About Anna Salyx

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. The key detail that was missing on the first comment, and the following example is: Yes, the permission to attach/detach is automatically granted in this type of situation w/out generating a permission prompt, but you still have to ask for it before you try otherwise the system complains (throws an error).
  2. This tagged a memory I'd forgotten all about -- a list from sometime in the late 80's that grew out of the tongue-in-cheek satire about how real men don't eat quiche. Someone, or several someones contributed to a list of the characteristics of 'real programmers' and what they do and don't do. It's own tongue-in-cheek spotlight on some of the toxic attitudes in programming circles. One of the lines seems to have be come the mantra of the person in question: Real programmers don't comment their code. If it was hard to write, it should be hard to understand and harder to modify.
  3. If you are on Firestorm, (and probably other RLV enabled viewers) if you put items into a folder that is/has a hud position name (top, bottom, etc) when you wear or add that item by double click it will attach to the HUD. This is so that if a RLV command is used to dress you, the viewer knows where to put it. And for various reasons, this also happens even when RLV is not enabled. If you rename the folder, or move the item out of the folder with the 'special' name, since the object remembers the last attach position you have to manually point it to a valid spot on the body itself the
  4. Good to know. I learned something new, so today is a good day Thank you.
  5. I don't know photoshop, but in gimp when I export to TGA or PNG formats, the program wants to add compression during the save. Then when you upload to SL, it's further compressed by the import process. So I always try to remember to disable compression on export saves that I intend to import into SL. So. If you are not already doing so, you might check your export save settings and turn off any initial compression pass that might be happening.
  6. it's very wise to be careful on things like that. One thing that I do in similar situation is go to a public "no-script" sandbox (I like Alethia Island Public Sandbox (not affiliated)) and step into a no-script area (they are clearly marked) and rez things (don't attach - attaching might still be dangerous but simple ground rezzing isn't). any malicious scripts won't run and it gives you a fairly safe place to examine something and make a better, more informed, decision.
  7. I think wishlists are very cool, and in a very general they are for friends/family to know what you might be interested in. I do publish mine on my profile but only with a tag: here is my wish list <link>. There is, on mine, never a demand or even a polite request (beyond the tacit one that is associated with simply pointing to it that is). I figure there are nice people who like to do nice things for people. Kind of a 'Pay It Forward" personality/mentality. I know I'm one of them. And have to believe there are others in the world. So wishlists, and pointing them out, is
  8. So A trick you can do for testing is apply the local texture to a box and get the temp UUID from there Then plug that UUID into an applier and apply it the tattoo layer for you body. this way you can see how it will look when you finally upload it for BOM. I do this, have done this, for maitreya, but I'm sure it'll work for any of the mesh bodies that have applier kits. it's been a while since I've done this, so I don't remember if when you make changes in Photoshop and reexport if it will update on the layer automatically or if you need to activate the applier again,
  9. lol. For a long time there wasn't. Just a favorites.. I'm not sure when they added the public wish list, but it's a nice feature. I don't have much in mine, truth be told, but I added mine to my profile just in case any profile surfers out there want to be extra nice
  10. What I do when I need multiple timers is a global variable to set the 'end time' for the timer tick against unix time. then compare the current unix time against the variable on each timer event. This works for me as it helps me keep straight (if I use good var names) to know what's fireing on what intervals. Now granted most of my timer needs are at intervals of more than 1 second, usually a minimum of 10 seconds, so I'm not sure how accurate it would be on fast pulse, but I don't really see why it wouldn't . You could also reset the variable after the 'do stuff' is finished sim
  11. "As a security measure, parcel owner, estate owner, and estate managers can not have their objects returned by this method, except when the object returns itself. " I"m thinking that since you own the object being returned you cannot use this method to return it. So going back to your original question, I'm not sure if there is a good solution.
  12. I think of Elsie till this very day I remember how she´d turned to me and say: "What good is sitting all alone in your room? Come hear the music play Life is a cabaret, old chum! Come to the cabaret!"
  13. You defined "my_list" as a global in the header section but you also redefine "my_list" with the list keyword in the touch_start event. That second time that "my_list" is defined in the event creates a local version of the list that is limited solely to the event and does not get passed to the function when it's called. So when you try to set the "end" variable in the function with the call to get list length it's using the empty global "my_list" and is set to zero. The for loop does its first check and since i equals end (both zero) the for loop exits immediately and the function exits norm
×
×
  • Create New...