Age | Commit message (Collapse) | Author |
|
A complete fix for a single cause of caching issues, does not solve all caching issues.
Fixes the issue of inventory links that were incorrectly being marked as broken.
Broken links get a second chance to see if their base objects exist in inventory now.
|
|
|
|
|
|
|
|
New --leap switch takes a quoted command line likely to contain spaces. Sloppy
handling of quoted arguments definitely gets us into trouble. Fix that.
|
|
|
|
previous settings exist from old viewer
only write back floater positioning information generated from legacy saved rect after reading any new
floater positioning info
|
|
- Set proper callback for buy button
- Removed dead code
- Fixed values for action combobox in object profile panel
|
|
|
|
|
|
|
|
|
|
against sculpt based crashers.
|
|
with "/".
Encountering such a mask will show a warning message and throw a debug assertion.
|
|
|
|
if object inspector is invoked for the same object.
|
|
using realtive coordinates
changed settings naming scheme for floater positioning so that related settings appear together in file
|
|
|
|
previous settings exist from old viewer
apply relative positioning to floaters that are loaded with rects specified from earlier viewer
|
|
made received items not auto resizable
save/restore received items height on collapse/expand
|
|
|
|
|
|
Every LEAP plugin gets its own LLLeapListener, managing its own collection of
listeners to various LLEventPumps. LLLeapListener's command LLEventPump now
has a UUID for a name, both for uniqueness and to make it tough for a plugin
to mess with any other.
|
|
not work)
Reason: Showing the confirmation dialog resets object selection, thus there is nothing to derez.
Fix: pass selection to the confirm_take, so that selection doesn't "die" after confirmation dialog is opened
|
|
|
|
|
|
toggling when default is INFO
|
|
|
|
computation found in the viewer.
|
|
Have to pump "mainloop" a few times to flush the buffer to the pipe, a
potentially risky strategy: we have to trust that whatever condition led to
the LL_ERRS fatal error didn't break anything that listens on "mainloop". But
the worst that could happen is that the plugin won't be notified -- just as if
we didn't try in the first place. In other words, no harm in trying.
|
|
Certain use cases need to know whether the WritePipe buffer has been flushed
to the pipe, or is still pending.
|
|
horizontal scroll bar hides last item in folder view.
Added a scroll container which provides the information about the height of currently displayed folder view contents. It is used for updating vertical scroll bar visibility in inventory panel.
|
|
|
|
image file to be loaded.
|
|
This test must not be subject to spurious environmental failures, else some
kind soul will disable it entirely. We observe that APR specifies a hard-coded
buffer size of 64Kbytes for pipe creation -- use that and cross fingers.
|
|
This code replaces the previous cleanup of DLLs loaded by APR.
|
|
relying on hacked computation based on width / height.
|
|
|
|
read latency
|
|
Nuance of command-line processing: when there's exactly one --leap switch, the
resulting LLSD is a scalar string rather than an array with one entry. Fix
processing code to handle either case.
|
|
|
|
changed stacking logic to attempt to stack against any floater that is cascade head
*or* in a cascade group
|
|
|
|
|
|
bad XUI
|
|
You can specify one or more instances of --leap 'command line'. Each such
command line is parsed using bash-like conventions, notably honoring double
quotes, e.g. --leap '"c:/Program Files/Something/something.exe" arg1 arg2'.
(Specifying such an argument in a Windows Command Prompt may be tricky.)
Such a program should read its stdin and write to its stdout using LLSD Event
API Plugin protocol: length:serialized_LLSD
where 'length' is the decimal integer count of bytes in serialized_LLSD,
':' is a literal colon character,
and 'serialized_LLSD' is notation-format LLSD.
A typical LLSD object is a map containing 'pump' and 'data' keys, where
'pump' is the name of the LLEventPump on which to send 'data' (or on which
'data' was received). In particular, the initial LLSD object on stdin mentions
the name of this plugin's reply LLEventPump: the LLEventPump that will send
every subsequent received event to the plugin's stdin.
Anything written to the plugin's stderr will be logged in the viewer log. In
addition to being generally useful, this helps debug problems with particular
plugins.
|
|
|
|
Sigh, the rejoicing was premature.
|
|
|
|
If in fact we've managed to fix the APR bug writing to a Windows named pipe,
it should no longer be necessary to try to work around it by testing with a
much smaller data volume on Windows!
|