Skip to content
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

[bug} Settings and Compile menus make entire program stuck "on top" #1548

Closed
dromer opened this issue Apr 29, 2024 · 6 comments
Closed

[bug} Settings and Compile menus make entire program stuck "on top" #1548

dromer opened this issue Apr 29, 2024 · 6 comments
Labels
bug Something isn't working gui

Comments

@dromer
Copy link
Contributor

dromer commented Apr 29, 2024

These always stay on the very top of the rendering which means file dialogs etc are completely obscured.

@dromer
Copy link
Contributor Author

dromer commented Apr 30, 2024

Example of file dialogs being covered:

2024-04-30_13-15

@timothyschoen
Copy link
Collaborator

It shouldn't be stuck on top anymore, though there are still some small other issues. Dragging the window by a dialog toolbar is not working for example.

@dromer
Copy link
Contributor Author

dromer commented May 1, 2024

yes, much better!

although it's still weird how you can move around the "composited" compile or settings dialog:

2024-05-01_17-41

@dromer dromer closed this as completed May 21, 2024
@dromer
Copy link
Contributor Author

dromer commented Jun 3, 2024

This is still a problem for the plugin version!

2024-06-03_07-26

@dromer dromer reopened this Jun 3, 2024
@dromer
Copy link
Contributor Author

dromer commented Jun 12, 2024

Can even get the menu behind the main window:
2024-06-12_14-22

@alcomposer alcomposer added bug Something isn't working gui labels Jul 2, 2024
@timothyschoen
Copy link
Collaborator

timothyschoen commented Aug 15, 2024

All dialog crap should be fixed now!

When dialogs are shown, we render openGL/Metal content off-screen, and copy it into a JUCE image which is displayed (and updated live) behind the dialog. It's a bit of a workaround, but it works!

The reason we can't use nanovg for all rendering is that it's text rendering isn't good enough (nor fast enough). Someday we could write our own text rendering system for nanovg, but that's a bit much for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working gui
Projects
None yet
Development

No branches or pull requests

3 participants