From: Old Television
Seems like your defending the UI without actually testing it.
First, I'm not defending anything. My goal here was to help provide solutions. That's it.
The closest thing I did to "defense" was to point out that it's unfair to call the entire system counter-intuitive, simply because one key sequence has changed. I'd call that more of a reality check, and a call to keep things in perspective, than any kind of attempt at protection. I don't own any stake in the SL interface. I have no reason to defend it.
Second, I did test. As I said, testing the specific sequence of enter->delete didn't occur to me, since all the original post said was " you can no longer hit delete to remove a number," but I did test everthing I posted. Upon reading the original post, the first thing I did was log into SL, rez a prim, positon the cursor between two digits the editor (by clicking), and press delete. The number immediately to the right of the cursor was deleted, exactly as it should have been. So, I responded here with "Delete key works fine on my end" because in that instance, it WAS working just fine.
Had the original post said "enter->delete no longer works", I would have tested that, but it didn't. When a follow-up poster mentioned that sequence, I again immediately logged into SL, checked the sequence, and discovered it was in fact malfunctioning. I then told that person she was correct, and I offered a simple work-around.
How exactly does any of that constitute "not testing"?
From: Old Television
First you say delete function was not broken the way the poster said it was without testing it,
Uh, no I didn't. See above.
From: Old Television
now you say use tab and shift-tab instead. However if you have been using the tools lately, you would know that they also screwed up the tab order among other things.
Now who's not testing? The only tab order that has changed is on the texture tab, which unless I missed something, was never a part of this discussion. We've been talking about position the whole time, which is entirely on the object tab. The tab order/behavior on the object hasn't changed in any way. It's still a single tab between each filed within each catagory, just as it always was.
From: Old Television
There are quite a few changes they have made with this UI update that require two or three clicks to do what used to be available in one single click.
You mean keystrokes, not clicks, right? There's nothing on the editor that requires more than one click, anywhere.
From: Old Television
There is nothing that I have seen that has been made easier or less clicks at all.
Assuming you do mean keystrokes, again, there's nothing that has changed except on the texture tab. The tab sequence now lands on the flip check boxes and on the apply button, where it didn't used to. This new behavior has in fact added functionality since you can now trigger the checkboxes and the button with the enter key, whereas before you couldn't.
From: Old Television
It's pretty easy to see that overall function has been decreased by these changes and the build system has taken a step backwards in general. While the posters above are getting a bit wild about the frustration they have experienced, they are actually right and you are wrong.
It is? They are? I am?
That's certainly news to me. As I've been writing this, I've tested and retested everything I've said, and it all works. Perhaps you should do some testing of your own.
If you are in fact seeing something different than I am, then that's a big issue. I'll tell you what, test what exactly what I've said, and it doesn't work for you, record whatever behavior you're seeing in a Fraps video. I'll do the same, and I'll even provide the webspace to host both videos so anyone who wants to can compare them. I find it extremely unlikely that there are two different sets of behaviors going on, but if there are, I'm sure LL would be grateful to know about it.
From: Old Television
It's not helpful to be so quick to defend something before you actually look into it, and just because they are upset, doesn't mean you have to be nasty back to them. They have a right to be upset.
For the umpteenth time now, I did look into it, exactly as I described.
As far as being nasty, I wasn't. Someone quoted my first post in this thread, and then laid out a bombastic, angry attack at LL, which I have to assume was also aimed at me since there was no other reason to quote me. My response to that was a whimsical "settle down, Beavis", which wasn't anything I considered to be mean, and then I offered help to that person by providing a simple workaround to her problem.
In my next response I suggested that people do something more productive than complain. The problem exists, and that's that. Complaining accomplishes absolutely nothing, but learning the simple work-around, and getting back to work accomplishes a great deal.
Now, did I express some mild frustration that a few people seemed to be ignoring the workaround in favor of complaining? Sure, I did. I'd hardly call anything I said "nasty" though. Quite the opposite, actually, I considered my posting here to be quite positive. I still do. Everything I've said here has been with the intent of providing people solutions to their problems. That's hardly the mark of nastiness. I'm sorry if you feel that anything short of comisery equals an attack, but I believe in providing answers, not in wallowing in negativity.
Old, you'd do well before you go accusing people of "not testing", to do some testing yourself, and before you accuse anyone of being "nasty", you take a good hard look at exactly what's been said and why.
