It sure would be nice... (iLogic Fomrs)

[chris]

It sure would be nice if there was more functionality built into the default iLogic Form editor.

Part of the fun in using the iLogic forms is being able to design a clean and efficient form that makes the end user experience easy and understandable.

Here's a simple example of just being able to add color to a group container. The model is set to a view rep that allows to the user to configure a support W Beam's Size and Length, Top Plate Size and Hole Pattern as well as the bottom Plate's size and hole pattern. I also need to add some flange and web hole groups for braces or connecting Beams

EDIT: Okay I found this code from a post in (2012), but what would I need to add to this so that when the form is launched this code is triggered?

Dim odoc As Document
Dim ocompdef As ComponentDefinition
odoc = ThisApplication.ActiveDocument
ocompdef = odoc.ComponentDefinition
Try
ocompdef.RepresentationsManager.DesignViewRepresentations.Item("Configurator").Activate
Catch
MessageBox.Show("This viewrep does not exist", "Error")
End Try

I was wondering if there was a way in iLogic that would change the models view rep state from "Default" to "Colored" if the Configuration form is launched. That way the user doesn't have to remember or even know how to change the view rep

[WCrihfield]

Hi @chris.  How is your form currently being launched?  It is almost always launched by an iLogic rule with something like iLogicForm.Show() or iLogicForm.ShowGlobal() method.  Why not have your code for changing view rep in that rule, just before it launches the form?  Or put something like iLogicVb.RunExternalRule() in there just before showing the form, to run another rule that will change the view rep, if you want to keep the code separated?  Just a thought.