Jump to content

UI flip flopping and inconsistencies.


CaithLynnSayes
 Share

You are about to reply to a thread that has been inactive for 1001 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Hi there.

Caith with a rant. Strap in kids...

(Kind of an open letter to LL...?)

So, as the vast majority of your users, i am also a Firestorm user. Because it's just better. today they released 6.4.21.64531. I had the pleasure to test drive this version a couple of days before release. I have no issues with it. Typically these people are great at what they do and i support them. I understand that they take base code from you and add their own changes and improvements to it as they release new versions of the Firestorm viewer.

 

I've heard that you (LL) are making changes to the general look and feel of the viewer's UI and some of these changes do get copied into the Firestorm viewer. On the surface this is absolutely fine if it wasn't for one tiny little massive annoyance you guys seem to be taking a liking to lately.

 

A year ago when EEP was released, i shared my thoughts on it on @Willow Wilder's post in these forums announcing its release in Firestorm. In my reply to that i also addressed the way the save button works. It worked unexpectedly and still does to my knowledge. For some reason you guys seem to divert from the normal use of a "split button" like is used in the appearances window. (And in general programming and UI building.) The end user clicks the edge to get more options, in this case it's a save button that has a secondary function to "save as". Everybody knows to click that edge of this button to have the save as function.

Shown here:

 150508240_Appearance1.png.4e27188c78996b03f1c9163bcb575da2.png

With the release of EEP you decided to use a split button here. Appropriate in my opinion. However, you decide to make it function differently. Here you decide this split function should also change the main function. So click the edge, pick what you think is save as, but instead it just changes the main function to "Save As" and then the end user has to click the button.... again. Because reasons?

Shown here:

EEP-save-save-as.gif.020aab6a51e6fb3243798e4dad1f8f23.gif

So now you had 2 identical Split buttons within your application/program/viewer. One in the Appearances window and one in the EEP settings, yet they function differently. The logic behind that is something i'm still searching for to this day. This is confusing to your end users. I've never heard of or seen a program with a type of button presented in different windows/dialog boxes that looks identical, yet functions differently depending on what window it's presented in. I'm a programmer RL, I believe i've said this before. In my office we have one rule, and i think other programmers reading this will know this too: People/end users are stupid. The majority of them are stupid. so, KISS (i hope you know what that means) So, why are you making it needlessly complicated and difficult for your end users? It honestly baffles me, AND worries me.

 

 

It looks like you heard my rant on that a year ago and decided to change the Split button in the Appearances window some time ago. (I can't exactly pin down when since i don't use your viewer. Changes made by you will only be visible to me once Firestorm updates.)

You decided to do away with the Split button in the Appearances window and put 2 seperate "Save" and "Save As" buttons next to each other. Not sure why, but i want you to look at the next  2 pictures for at least a solid minute.

 

A:

1752845052_Appearance3.png.360c87a8f50e9436ce3dbe2fa21770a9.png

B:

948943829_Appearance2.png.6c305b1b1e9790e871a74802c51535d3.png

 

Can you tell me if you see anything potentially dangerous here? Keep in mind that this viewer is nearly 20 years old and a good chunk of that time this viewer had this Split button in the Appearances window... You have long term users for nearly that same length of time...

 

You don't see it? Allow me to help you. Picture A is a screenshot of the Appearances window while editing Avatar Physics and has the button "Save As" on the far left. Picture B is a screenshot of your recently refreshed Appearances window where you did away with the Split button and has "Save" as the first button on the far left... Also, keep in mind that the latter used to be a Split button...

Do you still not see an issue with this? I've nearly overwritten an outfit i was editing because i was so used throughout the years that there is a Split button but you replaced that with a full "Save" button. To keep the confusion real, you left the "Save As" button for editing Physics on that same location. Simply amazing...

 

Dear Lindenlab. I am fully aware of the fact that i can sound very demeaning and degrading, but i want you to know this is not my intend. However, I ask you. How well do you think things through before you implement changes? This is a sincere question and i'd like you to answer me this. I guarantee you that users will overwrite existing Outfits because of muscle memory and they will hit the edge of your newly placed full Save button knowing from the past that it was a split button.

I understand you want to simplify your UI, i'm all for that and more power to you for it. But i ask you, please think things through before you make changes. Think for example of how long a function/button is there for, does it cause issues? Is it misplaced and have a lot of people asked for it to change. In this case i see none of that. Its a real sad shame that people grid wide talk about these things when LL changed something again when nobody asked for it. And in this example you've set yourself up for user frustration. I promise you, you will have people overwriting outfits and they will complain. Eventually i will do it as well and i'll be cursing in my  native language and feel lucky you won't be able to hear it or understand it. It's F*ing nasty.

 

Recap: You added a button last year with the same look of a previous one, yet the new one acts differently. you removed the first (years old) button and put its 2 functions in separate buttons where the save button is now overlapping a space in your program where muske memory lies, where users are used to click to get the save as button (edge of the Split button) opening up the potential for outfits to be overwritten without warning. You made sure the confusion stays by keeping a Save As button in the same place when editing Physics using the same window. If i do such things in my RL job, i will get away with it once, and my company will have to release a patch to fix my f*ck-up. Next time i do this, i will be looking through the job applications...

 

Caith Out.

 

 

 

 

 

 

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 1001 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...