topic Re: Master Info Control Object in GDL

Master Info Control Object

MichaelIserief — Wed, 31 May 2023 07:56:51 GMT

I was hoping to create an object that could be used to control settings of other objects. (e.g set the Local Government Area which would update parameters across the title block, retaining wall matrix and driveway design matrix objects). I could have this happen with the MVO settings, however this poses a risk of editing the wrong MVO option set or redefining a view with the incorrect information.

Is there another way of achieving this else besides the MVO that I might be missing here?

Re: Master Info Control Object

Lingwisyer — Mon, 31 Oct 2022 03:40:15 GMT

Other than MVO, you could use the text I/O, but this will only refresh on object update.

https://gdl.Graphisoft.com/tips-and-tricks/how-to-read-and-write-text-files

Open your master object, make your changes, text out, refresh / reload all relevant objects.

Ling.

Re: Master Info Control Object

SenecaDesignLLC — Mon, 31 Oct 2022 04:55:38 GMT

I use MVO settings that read from a library master object so that I can have default settings for the project that just takes typing in the name of the master settings into my MVO settings so that they all read from the same place. It's also allows me to generate multiple options with exteriors that the labels change automatically with based on which default parameter I'm specifying the MVO to read to

Re: Master Info Control Object

Nathan Hildebrandt — Mon, 31 Oct 2022 12:32:20 GMT

A simple approach if you don't want to go down a database or MVO route, could be to have layer options within the objects themselves and you go into the object and change the Local Authority in settings which controls the layer view of the object and then they will display the different alternatives that you want to see.

Re: Master Info Control Object

DGSketcher — Mon, 31 Oct 2022 13:00:01 GMT

I know the problem and the consequences can be serious if the MVOs aren't consistent in my world. I actually only have one MVO to avoid the problem, but for many that isn't an option. It has been discussed before and a suggestion has been made that there should be a level above MVO that is project specific rather than view specific. Unfortunately I haven't seen any movement to suggest it is being considered yet.

Re: Master Info Control Object

Nathan Hildebrandt — Mon, 31 Oct 2022 13:03:42 GMT

We used to have MVO control for our Zone stamps and labels so we could label things differently depending on the view. It was a pretty powerful solution for 2013, and thankfully that solution isn't needed anymore. The challenge is making all workflows user proof. You need to design every single workflow to the lowest common denominator. The least capable person that may need to work in the file. It is hard but the time taken to assess and work through the different iterations more than makes up for the time that could be lost due to user errors.

Re: Master Info Control Object

DGSketcher — Mon, 31 Oct 2022 14:25:19 GMT

I am in a single user office, should I be worried? 😂

I have leveraged the MVO to the nth degree in my framed building system. It controls roof angles, frame sizes, setting out points etc in several GDL objects, any divergence between MVOs could result in a major **ck up from which I would not recover with the client.

Re: Master Info Control Object

MichaelIserief — Mon, 31 Oct 2022 20:41:00 GMT

Forgive me, I am "self taught" and while I impress those in my office I am far from an expert.

By layer options are you suggesting that there is a way to control the layer settings of views from within a GDL object or is this simply some logic to control the display based on a layer combination set within the view?

Re: Master Info Control Object

MichaelIserief — Mon, 31 Oct 2022 20:42:26 GMT

HAHA, if I was on my own I probably would do the same thing, unfortunately I have other techs that are not quite as versed in all the settings as I am and this would definitely result in the latter.

Re: Master Info Control Object

MichaelIserief — Mon, 31 Oct 2022 20:45:38 GMT

@Nathan Hildebrandt wrote:
The challenge is making all workflows user proof. You need to design every single workflow to the lowest common denominator.

I once heard a wise piece of advice, which may be a bit crass but it nails the sentiment

"just as you think you've made something idiot proof, BAM! the universe goes ahead and builds a bigger idiot"

Re: Master Info Control Object

SenecaDesignLLC — Mon, 31 Oct 2022 21:25:35 GMT

This is why I work alone lol even though I have 3 licenses

Re: Master Info Control Object

Nathan Hildebrandt — Mon, 31 Oct 2022 23:32:01 GMT

Don't be worried we are all self taught!

It isn't layer control as you imagine it. It is layers within a GDL object. Here is a screenshot of some code that we used at my old practice for displaying objects differently on each storey. This met our need for a specific application, but it isn't suitable for all uses. This was storey controlled, but you could apply a toggle in the object to switch between (layers/views/content). which can be a simple UI for team members that struggle with MVO etc.

Re: Master Info Control Object

MichaelIserief — Tue, 01 Nov 2022 02:20:18 GMT

I think I'm following. Essentially your code would work out which story it was being viewed from and adapt accordingly using the FRAGMENT command?

I was hoping that the settings of one object would affect multiple other objects and I cant seem to make the mental jump of how this might achieve that.

In all these discussions I also had the thought that you could incorporate some logic to essentially remove the settings and print an error if the MVO wasn't just right. Although that might be just as convoluted.

Re: Master Info Control Object

Nathan Hildebrandt — Tue, 01 Nov 2022 04:16:41 GMT

I didn't write the script for this, someone that is clever at GDL scripting did that part, I understand the workflow need component. It depends on how many sheets the objects you need to switch or change out. There could be a simple solution to even have it as a single object placed on a worksheet that has multiple views created from it (and placed throughout the layout book where you need them placed). And through changing a setting in the object the whole object changes all of the content out and then you update your views. So many ways to skin the cat in Archicad.