The Global Archicad Community

Stay informed. Get help. Share your knowledge.

Modeling and drafting in Archicad. (Example: How can I model a Roof soffit/fascia?)

Moderators: Karl Ottenstein, LaszloNagy, ejrolon, Barry Kelly, gkmethy

Model View Options saving changes methodology

Keep as it is: changes are automatically saved
3
27%
Return to what it used to be: click 'Redefine' to make changes permanent
8
73%
Don't care
No votes
0%
User avatar
By Bruce
#309755
Since version 22, the Model View Options dialog was updated, so that any changes made would be automatically saved - similar to a Revit workflow. Although, throughout the years, I have liked all the changes introduced by Graphisoft, I think this one is not right.

A common workflow is to open the MVO dialog, make one change to quickly make an assessment - be it turning on beam centrelines; or seeing what happens when you change the door detail level; or a curtain wall option. The user has no desire to make this MVO change permanent - they just want to make one temporary change to the current settings.

Having a 'Working' MVO doesn't suffice, as it then has to be updated to match whatever the current MVO is. Temporarily changing the current MVO is dangerous, as one often forgets what it was before the change - or forgets to change it back. This problem is made worse in a Teamwork environment, as you also need to reserve the MVO settings first.

My question: what should Graphisoft do with the Model View Option updating methodology?
User avatar
By Barry Kelly
#309756
Bruce wrote:
Wed Apr 15, 2020 6:23 am
My question: what should Graphisoft do with the Model View Option updating methodology?

I completely agree with you - it needs the redefine button back (or an apply button).

Barry.
#309770
Barry Kelly wrote:
Wed Apr 15, 2020 6:42 am
Bruce wrote:
Wed Apr 15, 2020 6:23 am
My question: what should Graphisoft do with the Model View Option updating methodology?

I completely agree with you - it needs the redefine button back (or an apply button).

I also agree. This also applies to the 3D Styles dialog box. The changes should be purposeful, like the Layers dialog box.

David
By DGSketcher
#309811
I agree with the sentiments expressed here. However, the presentation option setting that really frustrates me is Project Preferences > Dimensions where you still have to change the style and then re-enter the exact same style name to overwrite the style. In comparison the "instant" update was a positive step. I have a feeling this is the only dialog that hasn't had an update to the save method.
User avatar
By Bruce
#309812
The update methodology is different seemingly for many things. In my opinion, the dialogs that need some revision are:
- Dimension styles
- 3D Styles
- MVOs
- Pen Sets


A consistent methodology across these would be great...but I thought I'd focus on just the one for now.
By DGSketcher
#309823
Bruce wrote:
Thu Apr 16, 2020 10:22 am
A consistent methodology across these would be great...
Sums up my feelings on a lot of the user interface just now. I don't understand how a software developer can fail to be using common code to consolidate the user interface. It would bring user appreciation and commercial benefits.
User avatar
By Erwin Edel
#309851
It took some getting used to, but we now have MVO for (most of) the type of views we need / use.

If I want to check stairs headroom, we have one for that.

We have them for door/window schedules.

Different design stages.

Special plan views like fire safety etc.

Not saying the change is ideal, but it becomes 'workable'.

An unified method would be preferred though! Also applies to things like Graphic Overrides and the rules that go with them. Very hard to export / import those.
User avatar
By mnguyen
#309982
Hi All,

I hope you are doing well during these trying times!

Thank you very much for creating this poll, and for those of you who voted to express their opinion.

I absolutely agree with you about the inconsistencies between various documenting options. Fortunately, this is an existing wish in our WishList database (please refer to it as Wish #11221). Hopefully, our Product Management team will consider changing this behavior in the future!

Thank you all once more, and I wish you a great day!

Best regards,
Minh