Difference between revisions of "User:Fred Gandt/Scripts/Continued 6"

Revision as of 23:33, 1 November 2012

I get in-world very rarely these days. The knock-on effect of this, is that I am not in the best position to keep these scripts updated. Please message me in-world (forwarded to email) if you discover any bugs (that can't be simply fixed), and I'll do my best to find a solution.

My Contributions

If unsure about how to use these scripts

I have implemented a V# system to make it more obvious if a script is updated. The V# forms part of the title of each script.

If you have any comments about the content of this page please post them HERE

All my scripts are written for compilation as MONO

More Pages

Direct Links To All Individual Scripts

Free Scripts (content constantly updating)

More Free Scripts (content constantly updating)

Even More Free Scripts (content constantly updating)

Even More More Free Scripts (content constantly updating)

Even More More More Free Scripts (content constantly updating)

Even More More More More Free Scripts (content constantly updating)

Even More More More More More Free Scripts (this page)

Car Type Land Vehicle Scripts (Working on it...)

Functions For Specific Tasks

Legal Stuff

The legal stuff about contributing to this wiki. (worth reading)

PJIRA Issue Tracker

The issues I have filed on the PJIRA

Tuition

Tuition scripts, notes, videos and screenshots etc. (hardly any content yet)

Free Scripts

Menu Engine (Textures) ( V1 )

These scripts are set up to make hierarchical multi paged dialog menus for object contents simple. The whole system works from notecards (NCs). We start with a main NC containing any number of NC names that are the titles of sub menus. They in turn may contain names of further sub menus ad infinitum. Any number of cards and any number of eventual sub sectioned prim contents may be added. The following setup walkthrough should explain better.

These scripts are setup for texture display by menu but could simply be edited to rez objects or give items or both. The important bit is how simple it is to organize the menus.

STEP 1

Fill the prim with whatever contents you're using. For the sake of demonstration lets assume it is textures and there are hundreds of them. To make life easier drop the "Helper" script into the contents and wait for the names of the contents to be chatted to you. You can then copy paste all the names in one go to a NC for ease.

STEP 2

Decide how you want to arrange the textures into groups. If you feel like wading through page after page of uncategorized texture names you can simply copy the whole list of names to one card, save it and drop it in the prim with the "Engine" script and you're done. But to make using the menus far more pointed we can set up sub menus and sub sub menus.

So what we do is add the names of the textures in groups to separate NCs. We then name those NCs according to the category we choose. Again for the sake of simplicity lets say we have predominantly red, green and blue textures but, we also have cubist and swirly of each color.

IN EVERY NOTECARD WE ADD THE NAMES OF EITHER SUB MENU NOTECARD NAMES OR TEXTURE NAMES (contents) ONE PER NOTECARD LINE.

What we would have is:

Notecard Name: Textures (or whatever you choose) containing -

Cubist
Swirly

Then also

Notecard Name: Cubist containing -

Cubist Red
Cubist Green
Cubist Blue

And

Notecard Name: Swirly containing -

Swirly Red
Swirly Green
Swirly Blue

Then NCs named: Cubist Red, Cubist Green, Cubist Blue, Swirly Red, Swirly Green & Swirly Blue each containing a list of texture names that suit the selections on the menu that would logically lead you to those.

STEP 3

Save all the NCs and drop them into the prim with the engine script and the textures. Write the name of the primary NC into the script (at the top) and it's all done.

The user would see on the first page: "Cubist" & "Swirly"

Then on the next page if they chose "Cubist": "Cubist Red", "Cubist Green" & "Cubist Blue"

Or on the next page if they chose "Swirly": "Swirly Red", "Swirly Green" & "Swirly Blue"

When clicking on any of the choices that lead to a list of texture names (however many there are) the next choice they make will set the texture for display. As I said before the scripts could be simply modified to do some other thing. I may write some alternative solutions based on this engine later.

The limits of this system are effectively moot. You can have as many textures as you can save to as many NCs as you need and as many NCs as will fit in the object with the other contents. The number of sub categories can be as many as is practical.

Finally, there is a "RETURN" button on every page to go back a step. So if you don't like what you are seeing you can step back to the last page of categories and back again if you wish right to the start. Every page that needs them will have ">>" (forward) and "<<" (back) buttons for cycling through the selections of that category.

Helper

Drop this on your loaded prim/object to get a local chatted readout of every texture name in the prim/object. Makes the initial setting up slightly easier since you can just copy paste the chat to a notecard.

<lsl>// V1 //

default {

   state_entry()
   {
       string name = llGetObjectName();
       integer it = llGetInventoryNumber(INVENTORY_TEXTURE);
       while(it)
       {
           llSetObjectName(llGetInventoryName(INVENTORY_TEXTURE, (--it)));
           llOwnerSay("/me ");
           llSleep(0.01);
       }
       llSetObjectName(name);
       llRemoveInventory(llGetScriptName()); // Self deleting script.
   }

}</lsl>

The Engine

This is the main script for the menu system. Add it to the same prim that has the contents (textures and NCs). Add the name of the primary NC to the top of the script.

<lsl>// V1 //

string main = "Categories"; // Name of primary notecard. Contains the first categories.

integer channel = -56782348; // This should be a very negative number.

integer face = -1; // The face number to display the texture on. -1 means ALL_SIDES

/////////////////////////////////////////////////////////////////////////////////////// ////////////////DON'T EDIT BELOW HERE UNLESS YOU KNOW WHAT YOU'RE DOING//////////////// ///////////////////////////////////////////////////////////////////////////////////////

list multi_page = ["<<", "RETURN", ">>"];

key short_data_req;

key long_data_req;

list dialog_list;

integer nc_line;

string nc_name;

list data_list;

integer busy;

key nonl_req;

list choices;

integer nonl;

integer lis;

key agent;

ClearLists() {

   dialog_list = [];
   data_list = [];

}

Dialog(list l) {

   llListenRemove(lis);
   lis = llListen(channel, "", agent, "");
   llDialog(agent, ("\n\n" + nc_name), l, channel);
   llSetTimerEvent(30.0);

}

BuildList(string s) {

   dialog_list += [llGetSubString(s, 0, 23)];
   data_list += [s];

}