2022-06-23 06:12 PM
Hi, I'm just exploring using Model View Options to change the parameters of a series of objects for a template. The main area to be changed is all the stylistic stuff - pens, fills, surfaces, etc.
As it's for a range of objects, this is resulting in a huge amount of calls with LIBRARYGLOBAL line. Is there any way I could condense a series of parameters into a single LIBRARYGLOBAL call? Or does it have to be one parameter at a time?
Solved! Go to Solution.
2022-06-24 11:39 AM
I am pretty sure you have to query each parameter separately.
Each parameter in the MVO has its own unique name.
And each will be different - pen numbers, line types, string values, numbers, lengths.
Barry.
2022-06-24 09:37 AM
Maybe @Ben Cohen can answer this, as he has done this sort of thing.
AC22-23 AUS 7000 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win10 | R5 2600 | 16GB | GTX1660 |
2022-06-24 11:07 AM
You have to have a separate LIBRARYGLOBAL query for each parameter in the MVO.
Those queries can go directly in your object - you don't have to CALL a macro for them.
But if you do CALL a macro, you can add more than one LIBRARYGLOBAL query in it and you can use RETURNED_PARAMETERS in the CALL to bring the values back to your object.
Barry.
2022-06-24 11:19 AM
Thanks Barry. My terminology was probably wrong in my query - I'm not using CALL at all - just the standard x=LIBRARYGLOBAL().
I was just wondering if instead of having 80 or so repeating lines, there was a way to condense all the info into something like an array and so only need to use the LIBRARYGLOBAL line once? It could then be unpacked in the script of the placeable object to get the useful parameters.
2022-06-24 11:39 AM
I am pretty sure you have to query each parameter separately.
Each parameter in the MVO has its own unique name.
And each will be different - pen numbers, line types, string values, numbers, lengths.
Barry.
2022-06-24 11:55 AM - edited 2022-06-24 11:57 AM
maybe including all parameter names in a array and the executing the LIBRARYGLOBAL call in a loop?
2022-06-24 11:58 AM
Yep, potentially. I guess I'm just assuming that repeated use of LIBRARYGLOBAL is inefficient but maybe there's no harm in repeating it lots anyway!