History Tree 'invert option'

As you pointed out, this is an open forum, so I will write what I want, where I want :slight_smile:

2 Likes

For me, it would be great if the scroll position stayed where I left it.

Sure thats what they call User Preference. I prefer the top, my reason because utilizing Variables I want to see last item I manipulated at the top close to be the variables, maybe I need reverse the order, reverse it again back and forth!

Many will have other various reasons, so things like this is User Preference.

1 Like

I’m not against ā€œUser preferenceā€. I’ve noticed that S3D team don’t like to add any custom preferences. It seems they trying to find one interface for everyone.

I don’t know why people think I’m protecting S3D, taking into account that I wrote feature request about history inversion even before HBPM was introduced to most users :slight_smile:

Edit:

Impact :red_exclamation_mark:: Many tools are controlled using settings placed with the history tree. For example, changing a revolve to adjust angle and elevation requires the user to scroll to the bottom of the tree to retrospectively add.

So the reason why people make feature requests. Feature request is made by the user for user’s own good. I could honestly care less about what S3D team prefer, if I care about that why make any feature requests.

Because introduction of variables it requires at least for me more options to organize the way it’s more beneficial for me so I can be more productive.

1 Like

What can I say? My feature request, which also contained ā€˜history reverse,’ was noticed by Istvan. He stated that it was a good idea. That was two years ago, and as you can see, we still have to scroll through the list :smiley:

You should be clamoring for these updates, did you give up?

I’m not. I started writing my requests in another place, where our opinions have a little bit more value :slight_smile:

And yet, last year there was information that this modification was not on the priority list.
This year, I started reaching out to them again, we’ll see what they say.

Hope not, and hope you do your job documenting what we are requesting.

That kinda rude.

It was not said with the intention to offend, it’s just my observation. I wrote here just like everyone else.

Moreover, I noticed that a year ago this forum was much more active. Istvan often participated in discussions.

ā€œI’m not an S3D worker, if that’s what you thought, but just a user who never closes the app. It is literally always open, and I use it dozens of times throughout the day. So yeah, I’m as interested in improvements as everyone else. However, I think there are many things that need to be done even before ā€˜history inversion’ :)ā€ On the other hand, as a software developer, I have to agree that this change wouldn’t take them too much time.

If I could make a polite suggestion, I think you should stop replying to them now. Your previous contributions to this thread have been fantastic to the point a member of the team replied.

However their replies are just muddying this thread with unnecessary comments and tend to never support fellow users. Further to which they are clearly superior to us mere mortals they have already raised this issue ā€˜two years ago’ and were ā€˜noticed by Istvan’ and have access to ā€˜another place’ because their opinions have ā€˜more value’.

1 Like

Thanks for that clarification, since it’s not your job and you have better access to the Shapr3d Staff, I recommend you document our requests and share it with them since your method has more value. :sweat_smile:

2 Likes

No joke, this is exactly what I do from time to time.

I said ā€œlittle bitā€ keyword was ā€˜little’ :slight_smile:

Like Steve Jobs philosophy, and then we had to hack our way around every setting. Remember when the Mover was introduced?

I think the S3D team does an excellent job, but it seems that as soon as a new release functions sufficiently, the desire to add or change anything to make it ideal disappears.

Display a reversed history as an option. If the user scrolls from the most recent addition, the new position will be maintained until the user scrolls back to last or clicks a last-icon.

Thank you, Kyun and Alex. Even when disagreeing with my views, I do value all of your thoughtful remarks. :slight_smile: Food for Thought!

Yeah. What is interesting I became Apple user only after Steve passed away… today I have almost all their devices at home.

That is the simplest they can do.

I agree on 100%

What can I say, all developers are lazy people, I’m not an exception.

OT, Sorry, I can’t resist;

Office mainframe backup (to the rigth)

(That actually still works with 4MB maxed RAM and a serial hard drive of 20MB)

Regretfully, I have an obsession with perfection.

I was working on these kind of machines too… long time ago :slight_smile:

Me too. That’s why zombies in my head always fighting :slight_smile:

Reminder of feature request:

The problem that this feature will solve:

Currently, every time you add a new modelling step, you have to scroll to the bottom of the history tree every time you want to configure the step. For example, when revolving a sketch and you want to change its angle and elevation you have to repeatedly scroll to the bottom of the tree. This is really unintuitive as if your tree is especially long, it is frustrating to have to keep scrolling to the bottom of the list.

Brief description of the outcomes that you expect from this feature:

Please provide a ā€˜sort’ option for the history tree. The option to invert the order of the history tree so that new modelling steps are placed at the top of the tree rather than the bottom. The current default of having new modelling steps automatically going to the bottom of the tree makes little sense and is not intuitive at all. Providing an option to invert the tree meaning new modelling steps added are placed at the top of the tree would be a dramatic quality of life improvement.

What can’t you achieve without this feature?

It’s an ergonomic nightmare having to scroll to the bottom of the tree every time you want to change a setting within a new modelling step. It slows workflow dramatically and is not intuitive. A ā€˜tree’ grows UP not down!

The sort option could be added within the menu seen below. The existing menu symbol even looks like a ā€˜sort list’ option anyway! This makes the current symbol confusing!

3 Likes