Changing Only The Frame Of An Existing CoreRPG Windowclass

Hi Guys,

A quick Q: if I just want to change the frame of a CoreRPG Windowclass in a child Ruleset, and renaming the source image is not an option, do I need to include the entire windowclass definition in the new Ruleset or is there someway I can use a "merge" technique (similar to templates) and only include the new frame code? Sample code follows:

Existing Code

Code:

---

<windowclass name="existingwindowclass">
        <frame>utilitybox2</frame>
        {Other Relevant Code Here}
</windowclass>

---

New Windowclass Code (I hope)

Code:

---

<windowclass name="existingwindowclass">
        <frame>utilitybox3</frame>
</windowclass>

---

Cheers

Quote:

---

Originally Posted by dulux-oz

Hi Guys,

A quick Q: if I just want to change the frame of a CoreRPG Windowclass in a child Ruleset, and renaming the source image is not an option, do I need to include the entire windowclass definition in the new Ruleset or is there someway I can use a "merge" technique (similar to templates) and only include the new frame code? Sample code follows:

Existing Code

Code:

---

<windowclass name="existingwindowclass">
    <frame>utilitybox2</frame>
    {Other Relevant Code Here}
</windowclass>

---

New Windowclass Code (I hope)

Code:

---

<windowclass name="existingwindowclass">
    <frame>utilitybox3</frame>
</windowclass>

---

Cheers

---

You can use join merge rule to do this:

Code:

---

<windowclass name="existingwindowclass" merge="join">
    <frame>utilitybox3</frame>
</windowclass>

---

no need to include anything else within the windwclass

Quote:

---

Originally Posted by Ikael

You can use join merge rule to do this:

Code:

---

<windowclass name="existingwindowclass" merge="join">
    <frame>utilitybox3</frame>
</windowclass>

---

no need to include anything else within the windwclass

---

So the Template join rules work with the Windowclass definitions as well? Excellent! That should save some coding size.

Thanks Ikael