[jeremyosborne]

By the way, I did notice something that others making UI changes might wish to know, so I'll just jot it here for archiving purposes.

Version I'm working with: 1.010

When I built said PartyMembers + PartyMemberN position relationships for my UI, I noticed that if I create the following sort of parent relationship in a single file, like so:

// This is a snippet from my partyMember1_override.mnu file
// A PartyMembers UI object is created in an external file
name PartyMember1

Widget
{
    // SNIP: This internalName would allow me to reference
    // PartyMember1::Container throughout the file, and it does
    //at load time
    internalName Container
    
    // This relationship, I believe because the widgets live in
    // different files and the files are read at different times does
    // not cause a "cannot find" error when using reloadMenus
    parentWidget PartyMembers::Container
}

Widget
{
    //SNIP:
    // Referencing a named widget within the same file will
    // cause a "cannot find" error when using the reloadMenus
    // command.
    parentWidget PartyMember1::Container
}

To repeat the code comments:

Relationships work fine at load time.

I had a problem with the reloadMenus console command giving me errors when using parentWidget and the associated parentLinked (snipped out of the code above) for positioning.

If reloadMenus doesn't seem to work and is returning errors, before giving up on the UI modifications, try quitting/restarting din's curse.