Build tool value fields changed.
|
Ian Scott
Registered User
Join date: 21 May 2005
Posts: 8
|
07-23-2006 16:27
My building method relies heavily on typing in positions, sizes, etc into the build tool value fields on the object tab. In the past when you click on a value field it gets automatically highlighted (which it still does) and once you have typed in a value and hit enter it convienently selects the whole value again, so if you put in a value that didnt work for you, you could easily type in a new one, deleteing the previous one in the process without any extra effort on your part. This was such a great set up, very intuitive, very quick.
Now though, when you hit enter after entering in your value, the cursor stays right where it was in the value field with nothing selected. Which means that when 104.125 should have been 103.875, I now have to either use my mouse to select that whole value or hit back space and arrow keys a bunch of times to clear the field before I could just type 103.875 like I could have before.
Now I know for most of you, this may seem like I am just knit-picking; but I assure you, if you spent as much time as I do editing your builds in this fashion, this little change becomes an utter nightmare. Builds are now taking me several times longer because of this little itty bitty minor change.
|
Dnel DaSilva
Master Xessorizer
Join date: 22 May 2005
Posts: 781
|
07-23-2006 16:32
I sympathise and wholeheartedly agree that this should be changed back, annoys the hell out of me!
|
AusFox Walcott
Registered User
Join date: 5 Nov 2005
Posts: 32
|
07-23-2006 23:03
Annoying allright... and now in object properties etc Delete key no longer works either apparently O_o; Also a seemingly tiny problem, but its still annoying when your modifying something and you hit a key expecting it to work and nothing happens =(
|
Bitzer Balderdash
Dazed and Confused
Join date: 21 Dec 2005
Posts: 246
|
07-24-2006 01:45
Try using the TAB key instead of enter. For me, that commits the edited number, and moves to the next field
|
Jack Harker
Registered User
Join date: 4 May 2005
Posts: 552
|
07-24-2006 01:49
From: Ian Scott My building method relies heavily on typing in positions, sizes, etc into the build tool value fields on the object tab. In the past when you click on a value field it gets automatically highlighted (which it still does) and once you have typed in a value and hit enter it convienently selects the whole value again, so if you put in a value that didnt work for you, you could easily type in a new one, deleteing the previous one in the process without any extra effort on your part. This was such a great set up, very intuitive, very quick.
Now though, when you hit enter after entering in your value, the cursor stays right where it was in the value field with nothing selected. Which means that when 104.125 should have been 103.875, I now have to either use my mouse to select that whole value or hit back space and arrow keys a bunch of times to clear the field before I could just type 103.875 like I could have before.
Now I know for most of you, this may seem like I am just knit-picking; but I assure you, if you spent as much time as I do editing your builds in this fashion, this little change becomes an utter nightmare. Builds are now taking me several times longer because of this little itty bitty minor change. Not at all, I was doing some building work yesterday and whas having the same problems. It *is* a pain, and I don't see what they changed it. This whole update, aside from increasing the numbers on the ban list was just one big collection of bad changes to things that didn't need to be changed.
|
Haravikk Mistral
Registered User
Join date: 8 Oct 2005
Posts: 2,482
|
07-24-2006 03:02
From: Bitzer Balderdash Try using the TAB key instead of enter. For me, that commits the edited number, and moves to the next field Sometimes you don't want to move onto the next field though  Also as an aside, the delete key deletes objects, which is a VERY nasty problem, because with this highlighting nonsense being so unpredictable I've several times tried to use delete (not backspace) to remove a character in a field and ended up removing the object I'm editing instead. I don't like any of the interface behaviour changes, it was great the way it was, now it's a pain to do anything creative 
_____________________
Computer (Mac Pro): 2 x Quad Core 3.2ghz Xeon 10gb DDR2 800mhz FB-DIMMS 4 x 750gb, 32mb cache hard-drives (RAID-0/striped) NVidia GeForce 8800GT (512mb)
|
Bitzer Balderdash
Dazed and Confused
Join date: 21 Dec 2005
Posts: 246
|
07-24-2006 03:39
The focus changes in this verison are little short of insane. I still can't work out if I will be typing into chat, IM, movement, or a data entry box in an edit / notecard / script after any given keypress or mouseclick sometimes.....
And as for when you close a window..... good luck working out where the focus has gone now!
|
hurly Burleigh
Registered User
Join date: 19 Sep 2005
Posts: 167
|
07-24-2006 06:41
I am in full support of changing back to the previous controls. I have almost decided to quit building and possibly SL too as it is now a chore to build instead of a pleasure. Why do we have to have changes for change sake when there are things like editable hollow positions and extra cut options that would enhance the building process not stifle it. The option to stretch a texture across 2 prims would be a godsend!!
|
Ian Scott
Registered User
Join date: 21 May 2005
Posts: 8
|
07-24-2006 07:01
On the topic of value field changes, this one happened after the 1.10 release at some point and seems to have gotten worse with 1.11. All the value fields on the right column, such as the cuts and such, tend to never stay true. If I type in 0.45 for example, on most occassions now that value will become 0.449 or 0.451 after I unselect that prim and come back to it. This problem seems to be more frequent when you are cutting both ends instead of just one.
IMHO, things like cut should go out to at least the thousandth place (0.000) without any changes what so ever. the four most common values I put into cut are 0.125, 0.375, 0.625, and 0.875, these are the cut values you need to get cuts that are either parallel or perpendicular to the sides of a cube (and also to the axis system), since the cut starts in a corner or a diagonal position. It's been a long long time since those fields have excepted anything accurate to the thousandth place, and now that it can't even be depended on to stay true at the hundreth place, it's become quite frustrating for those of us who pride ourselves on highly accurate builds.
(on a side note, it wold be great if you allowed us to have position and size values that could go back out to the 5th decimal place again (0.00000) without having to use a script to do so.)
I'm a math builder and these things tend to always be my biggest pet peeves with the build tools.
To end on a positive note, I would like to say that I am very grateful for the negative taper added to the shapes that used to only have top taper before the 1.10 release, that was an awesome addition to the build tool kit. Anyway, hope this info helps to some day lead to a much more useful and responsive tool set for those of us who use it the hardest, hehe.
|
Richard Cerveau
Registered User
Join date: 31 Jan 2006
Posts: 11
|
07-27-2006 03:15
i make sphere avatars that use a modular design, where u can add things onto your existing sphere av by simply wearing the module...
now i dont know about the rest of u guys, but they took OUT the world grid mode for attatchment positioning and left us with nothing but local grids... which would be useless for the stuff people like me do... as my builds depend on the world grid mode to actually position them right on the avatar
i mean, is it too much to ask to be able to have a high prim object with a small invisisphere as a centre to be pointing forward as in infront of me?? not forward to itself which may be anywhere??
|