LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: aop

I'm trying to create an external library of my own. I created a project in which I did put a couple of my own nodes. I saved the project to C:\Program Files (x86)\Lavastorm\LAE 4.6\lib\brain\brg which is a search path. Project name is lib.brg so I tried to add lib to base libraries in a new test project. BRE finds the file as I don't get any error message about that. However I don't see any nodes appearing. Is there some requirements for libraries in terms of some parameters or so or what could be missing from here?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

Hey,

This should work just fine.
I assume in your external library, you created the nodes in the library rather than the graph view right?
When you have included the library as a base library, and click on View->Dependent Libraries in BRE, is it pointing to the file in the path you are expecting?

Finally, the method by which the nodes are grouped into categories is based on the boxes within which they exist in the library.
If these are not in any box in the library, then they should appear in "All"->"Uncategorized" in the library.
You can configure which "library group" they will appear by default in (the "All" part from above) by creating a parameter "Suggested Library Grouping" within your library.
Alternatively, you can configure the library groups within Tools->Preferences->Library Groups.

The only reason why these should not appear in the palette in BRE is if you have a graph parameter "Private Library Nodes" set in your library and the name of your node is in that parameter.

Hope this helps,
Tim.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: aop

It seems my first problem was that I didn't create them in the library. So what I did now was that I selected the nodes in my library project and converted them to local library nodes. So I guess that was the idea?

1) Got the library grouping to work but not the category under the library group. My nodes are inside a box with a custom name but they still appear as Uncategorized. Any ideas?
2) One of the nodes in my library is basically set of nodes which I have hidden in a composite node to create a single node out of it. Now when I load the library in a project and put this node on the graph it asks me to give a name to it like BRE does when dragging a normal composite node on the canvas. How to avoid this?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

For 1:
Do you have a screenshot of the palette view and the library itself? It might be necessary to reload the library after saving the changes?
Is the "Uncategorized" part showing in the category, or sub-category (i.e. is it just <Library Group>->"Uncategorized", or <Library Group>-><Some Category>->"Uncategorized".
You can add sub categories by using the "/" character in the box to separate out the category and sub-category.

For 2:
Whether or not the popup to rename the node appears depends on the "DefaultAction" parameter set on the composite.
Essentially, if the "DefaultAction" is set to Open (which is the default for all composite nodes), then BRE will assume the composite is meant to appear and behave like a composite.
Since such nodes should generally be renamed on insert - to prevent confusion when looking at node names in logs etc, it will ask you to rename them.
If the composite node is meant to behave like a single node, then you set the "DefaultAction" parameter in the "Logistics" tab in the node editor to "Edit".
This way, the composite will generally behave and appear like a single node rather than a collection of nodes.
When someone double-clicks on the composite, the node editor will open.
Similarly, the rename node dialog will not appear when inserting an instance of the node.

Tim.