Surely I can’t be the only person bothered by this. Take a look at the following picture and hopefully you can see straight away what is wrong with it.
Why is the name of the call function (blue one) formatted differently to the name of the actual custom event (red one)?
It is not just that it adds spaces between the words, but if even changes the capitalization of the preposition “on.”
I have no problems with it doing this and actually don’t mind it. I just wish the custom event (red one) would do it too for consistency. By not having it consistent it means at times I have to thinking about which custom event I’m actually calling because the names aren’t quite the same at first glance.
I think there is a setting in the editor that if enabled, converts things to “friendly” names. I think it references variables specifically, cuz you’ll see similar behavior there. Not sure if it controls event names as well. Never disabled it myself. but you could try it
Yes, I know about that setting and it is actually on by default. The problem is that it is not formatting the custom event names on the blueprint graph the same way for consistency.
I dont understand how is that confusing, context menu search for all possible variants, if you create event named DeFF it would format call as De FF and you can access it from a context menu as “deff” “de ff” “def”. You can type stuff like “create m d i” and it would found “Create Dynamic Material Instance” for you (which is actually called as Material Instance Dynamic in documentation http://puu.sh/kCgbj.png)
I never said anything about it being confusing per se, and I understand how to search for nodes. I’m just simply saying that it’s aesthetically inconsistent on the graph.
)