D&D Official Theme, various issues after the last update

After the last update the D&D Official Theme shows alignment issues and errors in the console.

The following screenshots have been taken from a clean campaign, using the 5E ruleset and only the D&D Official Theme, no other extension:
https://www.fantasygrounds.com/forum...1&d=1693384597
https://www.fantasygrounds.com/forum...1&d=1693384606
https://www.fantasygrounds.com/forum...1&d=1693384612

Also, when trying to create a new note both DM and players get the following errors:

Code:

---

[8/30/2023 9:32:13 AM] [ERROR]  window: No vertical anchor defined for control (separator) in windowclass (note_header)
[8/30/2023 9:32:13 AM] [ERROR]  window: No vertical anchor defined for control (separator) in windowclass (note_header)
[8/30/2023 9:32:13 AM] [ERROR]  window: No vertical anchor defined for control (separator) in windowclass (note_header)

---

I've also attached the compiled logs with the errors.

Quote:

---

Originally Posted by Lo Zeno

After the last update the D&D Official Theme shows alignment issues and errors in the console.

The following screenshots have been taken from a clean campaign, using the 5E ruleset and only the D&D Official Theme, no other extension:
https://www.fantasygrounds.com/forum...1&d=1693384597
https://www.fantasygrounds.com/forum...1&d=1693384606
https://www.fantasygrounds.com/forum...1&d=1693384612

Also, when trying to create a new note both DM and players get the following errors:

Code:

---

[8/30/2023 9:32:13 AM] [ERROR]  window: No vertical anchor defined for control (separator) in windowclass (note_header)
[8/30/2023 9:32:13 AM] [ERROR]  window: No vertical anchor defined for control (separator) in windowclass (note_header)
[8/30/2023 9:32:13 AM] [ERROR]  window: No vertical anchor defined for control (separator) in windowclass (note_header)

---

I've also attached the compiled logs with the errors.

---

I'm using the Pathfinder 1e rule set and also have a number of display problems. The text for hot keys has changed to an ugly and difficult to read mustard yellow colour. The icons and text for the Assets tab icons are now a bright neon light blue against a white background. The chat bar is an ugly grey colour that clashes with the rest of the theme. I am assuming these are all errors and have reported and provided my compiled logs already.

Quote:

---

Originally Posted by Nemesis Unbound

I'm using the Pathfinder 1e rule set and also have a number of display problems. The text for hot keys has changed to an ugly and difficult to read mustard yellow colour. The icons and text for the Assets tab icons are now a bright neon light blue against a white background. The chat bar is an ugly grey colour that clashes with the rest of the theme. I am assuming these are all errors and have reported and provided my compiled logs already.

---

This type of behavior usually happens when you have more than one theme loaded. In a new campaign with no extensions do you see this behavior?

Quote:

---

Originally Posted by LordEntrails

This type of behavior usually happens when you have more than one theme loaded. In a new campaign with no extensions do you see this behavior?

---

I still see the same problems with a new campaign, no extensions. Double checked my existing campaign and there is only one theme active. The only extensions are the Feature: Advanced Bestiary and the Golarion Languages and Fonts FGU.

Same problem to me. Seems that something broke since last update.

Nemesis and John, Please provide details such as Lo Zeno did in the OP. That will help the developers find and resolve the issues much more quickly. Thanks!

Here is my log and a couple of screenshots.

Just pushed several fixes for general themes, including the D&D Official theme.
I plan to look at and update the Pathfinder Official theme later today.

Regards,
JPG

I can reproduce this as well; both the theme shenanigans and the error when creating a new note. All you need to do is open a campaign with the theme and click on new note.

Edit: Moon Wizard was clearly already on the case.

Sorry for that. Here we go all the info.Attachment 58691