Cool VL Viewer forum

Right clicking and choosing edit from pie chart for objects owned by other users (such as alts) brings up a blank edit window in all recent versions of 1.26.4. You have to double click or already be in the edit window to not get an empty screen. Makes it impossible as far as I can tell to edit linked prims. I don't think it is WAD because behavior is not present in 1.26.9 for example. Log and version info below:

Cool VL Viewer 1.26.4 (82) Jul 20 2013 14:27:26 (Cool VL Viewer)
RestrainedLove viewer v2.08.03.29
Release Notes

You are at 287872.6, 275376.2, 803.9 in Estruda located at sim10462.agni.lindenlab.com (216.82.51.168:13015)
Second Life Server 13.07.19.278836
Release Notes

CPU: AMD FX(tm)-6100 Six-Core Processor (4138.9 MHz)
Memory: 8138 MB
OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
Memory manager: OS native
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: AMD Radeon HD 6800 Series
Windows Graphics Driver Version: 8.17.0010.1191
OpenGL Version: 4.2.12217 Compatibility Profile Context 12.104.0.0

libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
J2C Decoder Version: KDU
Audio Driver Version: FMOD Ex 4.44.17
Qt Webkit Version: 4.7.1 (version number hard-coded)
Packets Lost: 41/4796 (0.9%)

Built with MSVC version 1600

Compile flags used for this build:
-DNDEBUG -DLL_RELEASE=1 -DLL_RELEASE_FOR_DOWNLOAD=1 /O2 /Oi /arch:SSE2 /MD /MP /D_SECURE_SCL=0 /D_HAS_ITERATOR_DEBUGGING=0 /DWIN32 /D_WINDOWS /W3 /EHsc /GR /Oy- /GS /arch:SSE2 /fp:fast /TP /W2 /Zc:forScope /Zc:wchar_t- /c /nologo /DLL_WINDOWS=1 /DDOM_DYNAMIC /DUNICODE /D_UNICODE /DWINVER=0x0501 /D_WIN32_WINNT=0x0501 /DLL_USE_OLDFILESTREAMS=1 /DCARES_STATICLIB /DCARES_STATICLIB /DLIB_NDOF=1

Are you maybe trying to edit a locked item and have "select only movable objects" enabled?

No, I use multiple accounts to build. The objects are not locked and the problem is with any object not owned by the account I'm using at a given time. If you are running 1.26.4, let me know if you are experiencing the same issue.

Cannot reproduce here...

However, there is a probable explanation in the log:

It looks like your graphics driver doesn't like v1.26.4... Try v1.26.8, especially since your hardware is largely capable of running the newer render engine.

I run both, but I generally prefer the graphics with 1.26.4. The older rendering engine has always seemed sharper to me, but perhaps that's subjective. I'll test this over the weekend on a laptop and see if I have the same issue. Thanks very much for your response though Henri.