Difference between revisions of "Feature requests"

From Second Life Wiki
Jump to navigation Jump to search
(→‎Filing Feature Requests: llTrace(integer rule,list[parameters]))
(Merged content in to Category:Feature Requests)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{OSWikiContribBox}}
#redirect [[:Category:Feature Requests]]
 
boolean llTrace(integer rule,list[parameters])
 
 
Howdie! just a new function suggestion.....
 
 
returns trace filter function result TRUE or FALSE
 
 
integer rule:
sets the type of the trace function:
- TRACE_TRIGGER the trace function acts like a trigger when trace target argument is actually traced
- TRACE_INFO    the trace function returns the realtime output value of the trace target argument
- TRACE_SCRIPT(@SPOT)  the trace function will trace defined arguments at a precise state in the
                      script @SPOT, as does already the jump function in LSL.
               
 
paramaters:
 
- [integer TRACE_TYPE[list params],integer task,integer filter,string label,integer display]
 
  .integer task: its the string name of the trace target argument defined whatever type it is
                it can be a string a boolean... depending on the trace type integer value
                entered.
 
  .integer filter is the type of tracing:
  - TRACE_INPUT traces only input values of the defined argument
  - TRACE_OUTPUT traces only the output of the defined argument
  - TRACE_STREAM traces the entire value stream related to defined argument
 
  .string label is any string inputed that will display each time trace target argument will
  get filtered out, limited to 32 characters.
 
  .integer display opens,shuts or do not dispaly a window to trace defined trace target value streams
 
  DISPLAY_ON(integer width,integer height,float alpha,vector color,integer trim)
            -integer width:  size in pixel of the display output window width
            -integer height: size in pixel of the display output window height
            -float xwpos:  location x value of the upper trace window corner.
            -float ywpos:  location y value of the upper trace window corner.
            -float alpha:    alpha render value of the trace display window.
            -vector color:  alpha render value of the trace display window.
            -integer trim: will define if the window will keep a static size
              or if it will resize as stream data values feeds tracing window
            TRIM_HEAD window will show a single line filled with the last traced value
            TRIM_LIVE window will fit exact size to display output data stream values.
              ""  "" ,secondary arguments:
                      TRIM_OUTPUT window wont show output data stream.
                      TRIM_INPUT window wont show input data stream.
            TRIM_NONE window keeps defined size or default size.
 
 
 
  DISPLAY_OFF shuts any or do not display trace window at all.
  ##TRACE TYPE---------------------------------------------------------
 
- TRACE_STRING[string  str,boolean CS,vector color,integer lenght]
  string str: string value defined.
  boolean CS:(case sensitive) defines if trace filter is case sensitive FALSE disable input case      sensitive.
  vector color: string color defined for tracing or set to integer ZERO_VECTOR or 0.
  integer lenght: string lenght defined for tracing or value 255 for any string lenght input/output.
       
- TRACE_VECTOR[integer type,vector v,integer display]
  integer type:defines vector type to trace as follows:
  -VECTOR_LOCAL_POS traces local vector position type.
  -VECTOR_WORLD_POS traces world vector position type.
  -VECTOR_ATTACHMENT_POS(integer attach) integer attach defines the attachment location vector source position.
  -VECTOR_COLOR traces vector color type.
  -VECTOR_ROTATION traces rotation vector type.
  -VECTOR_SCALE traces scale vector type.
  -VECTOR_VELOCITY traces velocity vector type.
 
  vector v: vector tracing defined value.
  integer display: display parameters (see parameters description above)
 
 
- TRACE_BOOLEAN traces aimed boolean defined in integer task.
- TRACE_FLOAT  traces aimed float defined in integer task.
- TRACE_LINK(ineteger skip) traces aimed link defined in integer task and skip linknum defined by integer skip.
                            SKIP_THIS skips LINK_THIS link number integer.
                            SKIP_SET  skips LINK_SET link number integer.
                            SKIP_ALL_OTHERS skips LINK_ALL_OTHERS link number integer.
                            SKIP_NONE skip nothing.
                            SKIP_ALL  skip all link number.
 
                            - TRACE_CHANNEL(integer C#) traces defined C# chat channel number output.
- TRACE_EVENT traces defined event type, at_target,not_at_target,on_rez ect....all LSL event integer   
              input type, task integer is set with the integer num related to the event.
 
- TRACE_LIST  traces any list active or static in the running script.
              defined by the integer task.
- TRACE_AGENT traces agent key UUID or name defined by integer task.
- TRACE_LAND  traces land key UUID or name defined by integer task.
- TRACE_PERMS traces permission rules key UUID or name defined by integer task.
- TRACE_ANIMATION traces animation key UUID or name defined by integer task.
- TRACE_TEXTURE(integer face) traces texture key UUID or name of textured object name or key defined by integer task.
- TRACE RANKING traces the vote ranking of the target defined by integer task.
                this come with the idea to implementt a new function llVote(sring name,key id)
                to give a ranking to object made by residents.
               
- TRACE_KEY traces the key UUID of the target defined by integer task.
- TRACE TIME traces instant time(t) value when integer task value is TRUE.
- TRACE_LAND returns the general informations and rules of the land the script is in.
- TRACE_STATUS(integer type) traces the status of an object,primitive or agent defined by task integer.
              integer type:AGENT_STATUS will trace only agent related status like wlaking,sit,flying 
              ect...
                                          name or key UUID defined by integer task.
                            PRIM_STATUS  will trace only simple primitive status like physics,phantom                                     
                                          ect...
                                          name or key UUID defined by integer task.
                            LINKSET_STATUS will trace only objectname or key UUID status defined by   
                                          integer task.
                            WEATHER_STATUS will trace only local simulated weather status,
                                          task integer must be set to TRUE.
                            LAND_STATUS    will trace only land status the script is in,
                                          task integer must be set to TRUE.
                            LOCAL_TIME_STATUS will trace only local time in the the land the script 
                                              is in task integer must be set to TRUE.
                            EXCHANGE_STATUS  will trace commercial status of the name or key UUID 
                                              defined in task integer
-TRACE_EMAIL(string mail) traces any email sent to target email box defined by string mail by the
                          script  task integer must be set to TRUE.
-TRACE_LINDEN returns a string that is current general SL statistic, shown aswell on the client home
              menu.task integer must be set to TRUE.
-------------------------------------------------------------------------------------------
this new function would be mainly usefull for developers that handles pretty complicated scripts
involving a lot of different events and states as values, its sometimes a real pain to find out the
little problem that turns a script's output to unwanted result.
It would be also an alternative or to say a versatile way to obtain a result from a script without
using other functions that requires several lines of additional or optional parameters.
It would make a pretty good triggering device or static sensor by the same time 8-)
 
That's all, hope this is good idea....
 
== Refining Feature Requests ==
 
Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea.
 
See [[:Category:Feature Requests]] for pages in this category.

Latest revision as of 08:56, 19 June 2007

Redirect to:

Retrieved from "https://wiki.secondlife.com/w/index.php?title=Feature_requests&oldid=23803"