Jan 14, 2014 at 7:49 PM
Edited Jan 14, 2014 at 8:26 PM
Is this a known issue or do I need to do something specific to fix this. We have been trying to get away from RDCMan for awhile now, but Terminals looks to have a bug with sub groups. I am using 3.4
Upon re-opening, I get:
What it actually looks like is happening is two things:
-When setting the Group ParentID in SQL is leaves it as blank, so I assume the groups are actually not being set at all beyond in memory.
-Secondly it looks like ParentID is never being looked at on the flipside, since if you manually change it in SQL it still does nothing.