Cannot click on Font Data inner resource after integrating with wwise about wwise-godot-integration

[alessandrofama]

Seems like this is the result of a mistake I made in the waapi-picker addon. It doesn't affect only these font fields, but all "nested" properties.

In waapi_picker.gd, replace:

func handles(object):
    return true 

with:

func handles(object):
    return object.get_class() == "Spatial"

Restart the editor after that.

This fix will be added to the next release.

[jontopielski]

@alessandrofama thank you!

[alessandrofama]

Hi Jon,

thanks for the report. I can't reproduce the issue. Could you share more details about your setup and project?

• What exact Godot version and OS are you using?
• Do you get any errors or warning at all?
• Does the problem occur on a new project without Wwise integrated?
• Does it only occur after you have integrated Wwise?
• If the problem occurs only on a project with Wwise integrated, can you share a minimal reproduction project?

Wondering if this might have something to do with the way wwise applies custom nodes / resources to the project.

We don't use Fonts and the custom nodes shouldn't interfere with such a thing. I doubt that this problem is caused by the integration, but you never know. So please let me know if you have more information.

[jontopielski]

• What exact Godot version and OS are you using?

• Godot Engine 3.2.stable.official
• Mac OS Catalina 10.15.6

• Do you get any errors or warning at all?

Nope

• Does the problem occur on a new project without Wwise integrated?

No. Here is what it looks like before wwise integration:

• Does it only occur after you have integrated Wwise?

Yes, here are the steps I went through.

After installing, here is what trying to edit FontData looks like:

• If the problem occurs only on a project with Wwise integrated, can you share a minimal reproduction project?

https://github.com/jontopielski/wwise-debug (note: did not include the binaries in wwise/bin)

Thank you for taking a look!

[alessandrofama]

Thank you for the details, much appreciated. Well...that is a weird problem 🤔. I will look into it and come back to you.