Community
Hi guys. I have never seen or heard of a way to edit the settings of more than one DVR (DesignViewRepresentation) at a time. I do not know of any Excel worksheet, table, or XML String type access to them where they could all be edited in one place, like ModelStates can. I do know about the DesignViewRepresentation.DesignViewInfo property, but that is ReadOnly, so no luck there. I would not want to have to edit XML code for something as seemingly simple as this anyways. Maybe this is something you could check in the Inventor Ideas forum for, and if no one else has posted about it, you could create a post in there about it. If DVR's had some sort of table (like ModelStateTable) type access, or more control over editing just one, multiple, or all at the same time (similar to edit scope), that could be pretty useful and efficient in various situations.
One efficiency trick I sometimes use when two DVR's share many identical settings, is to set the one the way I want it, then create (or Delete, then recreate) the second one using the Copy method, then switch to that second one, then change just the remainder of its settings the way I want. But that only effects to DVR's, and still involved activating both, so not really a solution. Taking advantage of the HideAll or ShowAll methods can sometimes help in situations where you only want one (or very few) components visible/invisible, but still must activate the DVR you want to edit.
Edit: I just created an Inventor Idea post for this ability, because it does sound super useful and should be a fairly popular topic. The link to that Idea post is below. The more people vote for it, the more likely it may be included in a future release of Inventor.
Wesley Crihfield
(Not an Autodesk Employee)
Hi guys. I have never seen or heard of a way to edit the settings of more than one DVR (DesignViewRepresentation) at a time. I do not know of any Excel worksheet, table, or XML String type access to them where they could all be edited in one place, like ModelStates can. I do know about the DesignViewRepresentation.DesignViewInfo property, but that is ReadOnly, so no luck there. I would not want to have to edit XML code for something as seemingly simple as this anyways. Maybe this is something you could check in the Inventor Ideas forum for, and if no one else has posted about it, you could create a post in there about it. If DVR's had some sort of table (like ModelStateTable) type access, or more control over editing just one, multiple, or all at the same time (similar to edit scope), that could be pretty useful and efficient in various situations.
One efficiency trick I sometimes use when two DVR's share many identical settings, is to set the one the way I want it, then create (or Delete, then recreate) the second one using the Copy method, then switch to that second one, then change just the remainder of its settings the way I want. But that only effects to DVR's, and still involved activating both, so not really a solution. Taking advantage of the HideAll or ShowAll methods can sometimes help in situations where you only want one (or very few) components visible/invisible, but still must activate the DVR you want to edit.
Edit: I just created an Inventor Idea post for this ability, because it does sound super useful and should be a fairly popular topic. The link to that Idea post is below. The more people vote for it, the more likely it may be included in a future release of Inventor.
Wesley Crihfield
(Not an Autodesk Employee)
Hi @ashSPTSS. This is another one that does not have a simple Yes/No answer. Yes, it would be possible to modify two different ModelState objects in the same way, at the same time...if those were the only two ModelStates present in the file, and we set the member edit scope to all members / factory scope. However, if there were more / other ModelStates present besides the two you want to edit, then there is 'technically' not a way to only edit two (out of more than two) ModelStates at the same time, without editing all of them. But, we can edit multiple of them by code in the same ways pretty quickly, such as in a loop / iteration. There are two main ways to edit multiple, but not all, ModelStates the same way by code. One way would be to get the collection of ModelStates, then iterate through them, check if each one is one you want to edit, and if so activate it, then make the edits you want while it is active, then advance to the next ModelState in the loop, and so on. Sometimes a document update may be needed between editing one before the next. The other main way to edit multiple, but not all ModelStates, is to do so through the ModelStateTable or Excel worksheet representation of that table. Yes, we can do that by code too, but of course it is a bit more complicated to do by code than it is to do manually. In this scenario, each row in the table represents another ModelState, then each column represents some detail or difference of each ModelState. As you would imagine, we would have to navigate this table by its rows & columns to access the individual cells that we want to change the values of, which can seem simple to say, but not always as simple to do, depending on what types of things you are trying to do / change. For instance, if you plan on changing the value of an iProperty in the table, then you must also know the name of the PropertySet that specific property belongs to, because that PropertySet name is often part of the text within the 'Header' of the column, within [] characters, right after the name of the property, like what you see when you manually open the ModelState table in Excel. However, before you can do either method of editing multiple ModelStates, you must first make sure you have a reference to the 'factory' document version of the file. This is just the Document that is associated with (under the control of) the ModelState that is currently active in that file.
Wesley Crihfield
(Not an Autodesk Employee)
Hi @ashSPTSS. This is another one that does not have a simple Yes/No answer. Yes, it would be possible to modify two different ModelState objects in the same way, at the same time...if those were the only two ModelStates present in the file, and we set the member edit scope to all members / factory scope. However, if there were more / other ModelStates present besides the two you want to edit, then there is 'technically' not a way to only edit two (out of more than two) ModelStates at the same time, without editing all of them. But, we can edit multiple of them by code in the same ways pretty quickly, such as in a loop / iteration. There are two main ways to edit multiple, but not all, ModelStates the same way by code. One way would be to get the collection of ModelStates, then iterate through them, check if each one is one you want to edit, and if so activate it, then make the edits you want while it is active, then advance to the next ModelState in the loop, and so on. Sometimes a document update may be needed between editing one before the next. The other main way to edit multiple, but not all ModelStates, is to do so through the ModelStateTable or Excel worksheet representation of that table. Yes, we can do that by code too, but of course it is a bit more complicated to do by code than it is to do manually. In this scenario, each row in the table represents another ModelState, then each column represents some detail or difference of each ModelState. As you would imagine, we would have to navigate this table by its rows & columns to access the individual cells that we want to change the values of, which can seem simple to say, but not always as simple to do, depending on what types of things you are trying to do / change. For instance, if you plan on changing the value of an iProperty in the table, then you must also know the name of the PropertySet that specific property belongs to, because that PropertySet name is often part of the text within the 'Header' of the column, within [] characters, right after the name of the property, like what you see when you manually open the ModelState table in Excel. However, before you can do either method of editing multiple ModelStates, you must first make sure you have a reference to the 'factory' document version of the file. This is just the Document that is associated with (under the control of) the ModelState that is currently active in that file.
Wesley Crihfield
(Not an Autodesk Employee)
Forums Links
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
