-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error opening Text section in Inspector view #42
Comments
I cannot reproduce this error. Maybe it is related with the order the resources are fetched. The problem is that the Phaser docs file ( Please, replace the file: (Check you clear the browser cache) It should prints some debug messages like this:
Please, try to reproduce the error again and send me your console log. All the log, from the start to the end. Thanks. |
It'll be a few days before I can get back to the original affected computer I previously tested on. I've tried on a fresh Windows 10 1909 machine that never had PhaserEditor2D installed and using I have a hunch that the affected Windows machine I tested on may have had some strange asset caching going on, although using a private browsing window didn't help on the affected machine. I'll report back when I can test on the affected machine again, but a fresh install of 3.2.0 on a fresh computer works fine. |
Hi @drfuzzyness I am glad it is working to you now. I will keep this issue open for a while. I think it was probably a problem with caching or a missing file. Thanks for the help. |
(reported by a client)
I’m having trouble using the scene editor in the new Phaser Editor 2D v3.2.0 to edit the styles applied to a standard text object. Though I can edit the content through the Text Content inspector, the Text inspector does not show up (see attached image). The inspector I’m referring to is shown here: https://help.phasereditor2d.com/v3/scene-editor/text-object.html. As a workaround, editing the associated .scene json file to add text style does work and is rendered appropriately in-editor and in-game.
This can be replicated by:
I noticed a few errors in my Javascript console which I pasted here: https://gist.github.com/drfuzzyness/1e2a9d597374b39f5aefbe6043ce5d87
Update: This seems to be caused by the
--enable-advanced-js-editor
command line flag. Removing this restores the intended functionality.The text was updated successfully, but these errors were encountered: