1.8.2 (7) VICIOUS building bug

Forseti was kind enough to alert me to this one...if you build by the numbers, you may want to add your Bug Report to the queue to get this one fixed asap.

If you rez a prim and go to the Object tab, then go into the X size field, type an number, then hit Tab, you *should* go to the Y field. However this last update broke that - when you hit Tab, your cursor goes to the Chat window. You have to click back on the Edit window in the next field to enter in the Y numbers.

Oddly enough this doesn't seem to affect the Texture tab number fields.

Wow, I just noticed this. HUGE problem for builders, if you ask me.

MM

yes this is like carpal tunnel from hell, not to mention slow ... you have to go keyboard - mouse -- keyboard - mouse... aaaahhhH!

you used to be able to hit ENTER, and edit that same input box, or hit TAB, and edit the next one

bring it back please! lol

Crap!
Thought I had finally found a bug before anyone.

Oh well, I will add my voice to the others and say this makes building almost impossible or at least seriously screwed up!

Nooooo. Please preview test the next update

Sigh... am i the only one who has this? , use mouse wheel to change : cut begin and end , this happen ;

get : ment to be
0.04 (0.05)
0.09 (0.10)
0.14 (0.14)
0.19 (0.20)
0.25
0.29 (0.30)
ectectect

Been around quite awhile now, leaving tiny glitches all over the place very easy.

And yeah fix this xyz crap asap please -.- i build by numbers.

UGH I just noticed this when recubing, thanx for sending in your bug reports folks!

Yea, this is VERY annoying! I hate having to fix cut prims each time they're rezzed/copied! My smurf house looks like crap now!

No need to use the mousewheel either; just enter numbers in cut (and other fields) and they're rounded up, down, to odd decimal places (.46 will give .459), reset when other fields are altered, etc. Annoying--and it's not easy to duplicate at first--you have to dork with a prim enough and then it'll start screwing up cuts!

Everything (and I mean EVERYTHING, including: rotation, hollow, twist, dimple, top size, shear, advanced cut, taper, and revolutions!) should be allowable to at least thousandths place (.000)! I HATE floating point errors!

This is easily the crappiest UI bug to ever make it into a production build of SL.

Forseti found this one like 3 seconds after the grid came up Hope we get a quick fix.

Even the simplest software release for the smallest firm has a "smoke test" that a human being can start the release and do the most basic of tasks. It don't get much simpler than rezzing a cube and changing its size.

How anyone even got near the relevant code to bollox this one is astounding, how the buildmaster didn't catch that code miles away from the areas that should have changed is a mystery, that no one even bothered to test this is inexcusable.

I hope no one wonders why SL releases are deemed "scary".

Dont like the new update either I too type in the numbers and everytime have to double click on the next field or I start typeing in chat every time... alot of wasted time and soooo frustrateing on top of the way things look ...

The motion can't really explain it but kind of making me feel weird.. nausious like?? When said didnt need to update but should I was hmmm should I and something told me not to wished I would have listened to myself on that one and not done so.

But couldnt help but update the inital one and get the bad building bug Please fix fast!

This issue is seriously hampering my building atm.

I'm never a big fan of rollbacks, basically because they're impossible.
Reverting to a previous version of the client on a voluntary basis shouldn't be a problem though.

I would love to be able to reinstall the 1.8.2 (6) version again (with the graphics error i didn't have), to be able to have a functional building tool.
Providing it doesn't have the same issue. (I haven't used the version long enough to know).

Please be clear, i'm not asking for any rollback of the current client for those who don't want to. Just offer the 1.8.2 (6) for download for us who'd rather use that version.

Oh... nvm.
I found the previous version of the client in my local settings/temp folder, and reinstalled 1.8.2 (6). So advice for people: just check if you still have the 1.8.2 (6) version and reinstall.

I agree...the tab feature needs to return.

In general, the two major deteriorations in the client interface since 1.6 have been in edit and keyboard/mouse buffering.

My mouse now seems to require multiple or extended clicks before responding.

Also the keyboard buffer does not respond in sequence at all times, especially if there is any lag. In other words, if I type something and backspace before it displays in the line, the last character displayed gets erased, NOT the last character typed.

So if I type:

"HELLOP" and a backspace,

and the prompt only displays "HEL" before I hit the backspace key, the display becomes:
"HELOP"
instead of:
"HELLO"

Lastly...what is going on with the percentages in the edit window parameter boxes? They can't seem to hit the even increments anymore... too many times I get .49 instead of .5. Have the Lindens been taking programming lessons from Bill Gates?

~ V ~

Everybody who's noticed this - and I've been swearing at it all day - should file a bug report. I'm sure that way it will go back to normal in the next version. But one has to make a noise about these things.

For some reason, I have no problem with it... maybe my copy of SL is buggy or did they fix it?

Chiming in... this bug is a nuisance

Annoying !

I've mentioned this to Karen, she cares! Hope for more info soon.

And Bill Clinton was known for "feel[ing] your pain" which in itself, although rhetorically successful, was not particularly effective.

To paraphrase Lazarus Long: "Schedules are truthful. If a person speaks of her empathy, make her give you a release date".

He was a time traveller too, which makes perfect sense.

Great, the new update doesn't even address this.

So exhausted by this kind of stuff.

/invalid_link.html

Awww.

Agreed. I'll be making mention of this when we stop into LL on Wednesday.