When collapsing nodes in a macro, the subgraphs are put into the functions section unddy "My Blueprint.
When collapsing nodes in a function, the subgraphs are neatly cathegorized under the function. Meaning that you can expand the function like a cathegory and all the subgraphs are listed there. Sadly this fails when you cathegorize the function itself:
ShipDataSetChild is uncathegorized:
/storage/temp/38292-screen.png
ShipDataSetChild is cathegorized as "S ":
/storage/temp/38293-screen2.png
The “Collapse Nodes” functionality greatly improves readability of blueprints and is vastly superior to simple comments. This advantage is currently negated by the cathegory-spam that makes finding functions nearly impossible.
The workaround of adding ZZZ in front of every function looks ugly.
I believe this is probably known. However, on the off- that this somehow slipped, I just had to report this. In my opinion this feature is really important.
Have a nice day and thanks for this great engine,
Forgot to mention, i’m using version 4.7.5.
Hey ,
Are you demonstrating that when a collapsed category is clicked on and dragged, it doesn’t move into a different order under the functions window? I want to make sure I understand your bug report before entering it into the system.
I appreciate your assistance! 
Hello ,
that is not even close. Collapsed nodes created in a function are accessible in the function section. You can open the function containing them the same way you open cathegories. As soon as you set a cathegory for that function they are seperated.
As shown in picture 1:
- the function “ShipDataSetChild” has no cathegory
- the function “ShipDataSetChild” has a little triangle on the left side that can be clicked to view the collapsed nodes
As shown in picture 2:
- “Ship Data Set Child” contains the collapsed nodes of the function “ShipDataSetChild”
- cathegory of “ShipDataSetChild” was changed to “S” from “”
Hey ,
I do apologize for not originally understanding your question. I have investigated this a bit more and this is what I’ve found:
I have created functions with 3 different categories. I have been able to move functions between the categories without any problem. I’ve also created collapsed nodes within the functions which create their own category. I have been able to still move that original function between categories and there are no failures.
When the category is changed for the function, the collapsed node category originally created stays where it originally was as a category and the actual function moves to the correct category that was selected.
I believe that’s what you’re referring to. With that being said, I have submitted a bug report to our developers. If for any reason you need to reference this report in the future, please refer to: UE-13695
Thank you and have a great weekend!