aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/linden/indra/newview/lltoolbar.h
diff options
context:
space:
mode:
authorDavid Seikel2011-02-08 20:09:17 +1000
committerDavid Seikel2011-02-10 14:55:07 +1000
commit5eeb6e8848a171a2f001c236f0ce533db8a08a6f (patch)
treee5722d6646568140ceb9473216db067cfc82f3f6 /linden/indra/newview/lltoolbar.h
parentThe new height limit is not reflected in the max you can enter in the map TP ... (diff)
downloadmeta-impy-5eeb6e8848a171a2f001c236f0ce533db8a08a6f.zip
meta-impy-5eeb6e8848a171a2f001c236f0ce533db8a08a6f.tar.gz
meta-impy-5eeb6e8848a171a2f001c236f0ce533db8a08a6f.tar.bz2
meta-impy-5eeb6e8848a171a2f001c236f0ce533db8a08a6f.tar.xz
For meta7 - while LL reserves the first 5 estate numbers for it's own use, we never did that here in meta7.
This causes a problem, since LL based viewers react differently to those first 5 estates. In particular there are dire warnings and greyed out widgets in the estate access tools. In meta7 there are now 2 active estates with numbers in the 1 to 5 range that are just ordinary estates, but their owners can't unban residents. The server developers never gave me an answer about wether just renumbering the estates would cause any problems. So I'll fix this in the meta7 viewer. These sorts of things should be server side enforced policy anyway. This may break LL TPV, but meta7 does not care about some other grids policies.
Diffstat (limited to 'linden/indra/newview/lltoolbar.h')
0 files changed, 0 insertions, 0 deletions