-
October 15th, 2020, 22:58 #1
- Join Date
- Sep 2018
- Posts
- 75
Modifing the Combat Tracker Frames
Hi,
I am trying to modify the frame_ctbox_host_header_toggles of the CoreRPG Combat Track (ct_host.xml) via layering.
I want to make it a bit wider:
Code:<frame_ctbox_host_header_toggles> <anchored to="headeranchor" height="35" width="120"/> </frame_ctbox_host_header_toggles>
Even <frame_ctbox_host_header_toggles merge="delete"/> seems to do nothing.
How can I modify this frame?
-
October 15th, 2020, 23:25 #2
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 20,541
Only controls with name attributes can be overriden.
Regards,
JPG
-
October 16th, 2020, 08:49 #3
- Join Date
- Sep 2018
- Posts
- 75
Hmm ok.
Why are there so many unnamed controls in CoreRPG, doenst this defeat the purpose of being a base layer which can be modified?
I tried to to build a new/addiitonal frame below the toggles with
Code:<frame_ctbox_host_header_toggles name="test" insertbefore="X" > <anchored to="headeranchor" height="35" width="120"/> </frame_ctbox_host_header_toggles>
Am I understanding insertbefore wrong?
-
October 16th, 2020, 14:34 #4
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 20,541
When the layers were originally built, I don’t believe there was merge of window classes; you just replaced the window class wholesale.
Insertbefore should insert in the display order before the named control specified. You might double check the original ordering.
If still having an issue, create a simple extension that just replaces the frame in CoreRPG and post it here.
Regards,
JPG
-
October 16th, 2020, 20:54 #5
- Join Date
- Sep 2018
- Posts
- 75
Here is the extension. It should draw a larger frame below the global toggles.
-
October 18th, 2020, 03:03 #6
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 20,541
Thanks for the simplified example. It helped me narrow down the issue fairly quickly. The issue is that the "display" component of a new control is always appended on the end; even though all the internal ordering and mouse click ordering was correct. This only affects FGU; and I'll push a fix in the next release build.
Regards,
JPG
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks