What specifically are you talking about here?Regarding selection boxes, these are so small and communicate nothing
What specifically are you talking about here?Regarding selection boxes, these are so small and communicate nothing
Being a previous CATIAv5 user, I miss several things. 1) A graphic representation of assembly restraints. Sketches have it, but assemblies do not. 2) A manual control of mouse / space ball center. Catia allowed the user to select a feature and 3d rotate around it until another was chosen.Hey folks, we are beginning our UI overhaul. Almost none of this will be in v28 since we have a lot of overhaul to do and want to release it all simultaneously. However, before we put 6 months into this we want to be sure we're on the right track. So, here's our thoughts - let us know your feedback.
Paradigms
Currently our dialogs are all over the map, but they suffer a few common problems:
1. You can see info you can't use - think seeing a grayed out draft angle in the Extrude Boss dialog that you can't interact with until you click the checkmark.
2. Dialog flow is often wonky - some have 2 columns and you have to switch back and forth around the dialog to get what you want.
3. Spacing and styling has a lot of consistency problems
Our new paradigm aims to fix these issues. Let's jump into what it might look like:
View attachment 39724
From this you might notice a few things:
1. The flow is top to bottom.
2. You are not shown anything you cannot use - UI is exposed as you indicated you need more functionality. For example, if you click Draft, the Draft Angle checkbox is shown.
3. There is much more consistency with fonts, spacing
4. They are theme responsive.
From a higher level, these would be dockable in the work area - to the right hand side or to the right side of the Design Explorer. Or, you can drag them around and place them as you like, similar to what we have today.
We are considering some bits of customization, for example you might find the above examples to be easy on the eyes but you want things to be closer together - we might implement a "Compact Mode" that tightens the margins of the controls, for example, but we are unsure if people want things like that. Large dialogs will have a scroll bar, most likely.
Here are a few examples of some dialog mockups (we haven't coded this yet), some docked, some floating, in various states of expansion:
View attachment 39736
View attachment 39737
View attachment 39738
View attachment 39739
View attachment 39740
Let us know your thoughts and if there is anything else you can think of from a UI/UX perspective for this project that you think would make a positive impact.
You can add and set Rotation Points.2) A manual control of mouse / space ball center. Catia allowed the user to select a feature and 3d rotate around it until another was chosen.
++++++++++++++++++++++++++++++++++++++++++++++!!!2) A manual control of mouse / space ball center. Catia allowed the user to select a feature and 3d rotate around it until another was chosen.
YES !- Every sketch must have a dialogue box that allows users to select basic sketch parameter like plane (!!!), sketch name, sketch normal (overriding plane normal).
We won't, despite me really wanting to This is a case where I know it will invoke wraith.
That sounds like the old AutoCAD AME approach back with R11 and R12. The issue I had with it is there was no history and to make changes or edit you had to redo the boolean. Not Fun.What I'm used to is creating two solids and applying a boolean operation to them, be it union, difference or intersect. When I first got into 3D modeling tools and encountered that approach of acting on two of more solids it made perfect sense to me.
Global:
- All input boxes and/or feature/function windows need an 'apply' button. Most often the only way to see what one's input will achieve is to click back in another field or 'ok' the results only to have to reopen the window to make adjustments
No, IMHO the most user friendly way to do that is a short timer started/extended by TextBox keypress events, so the timer event fires a second or so after the last keypress, which then fires the validation preview event. The timer is stopped if the user leaves the TextBox. Preview should be stopped if the user enters more data. The TextBox control can be subclassed to make any changes universal across the program.- All input boxes and/or feature/function windows need an 'apply' button. Most often the only way to see what one's input will achieve is to click back in another field or 'ok' the results only to have to reopen the window to make adjustments.
No, I have had to use programs that work like that and one spends all ones time trying to stop the preview updates and/or waiting for preview updates to end. If you want to make several changes all the automatism just stands in your way. An update button does the job, it gives me the power.No, IMHO the most user friendly way to do that is a short timer started/extended by TextBox keypress events, so the timer event fires a second or so after the last keypress, which then fires the validation preview event. The timer is stopped if the user leaves the TextBox. Preview should be stopped if the user enters more data. The TextBox control can be subclassed to make any changes universal across the program.
THIS!No, I have had to use programs that work like that and one spends all ones time trying to stop the preview updates and/or waiting for preview updates to end. If you want to make several changes all the automatism just stands in your way. An update button does the job, it gives me the power.
It is no wonder that I don't use those programs any more (not even sure they still exist).