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

Standalone GUI is only refreshed/drawn when moved beyond edge of the screen (on Windows 10 64bit) #245

Closed
DerAndere1 opened this issue Aug 10, 2020 · 4 comments

Comments

@DerAndere1
Copy link

DerAndere1 commented Aug 10, 2020

Version: source code (zynaddsubfx/zynaddsubfx@22a5f8d
OS: MS Windows 10 64 bit
Build: built natively in release mode on Windows 10 by copying the build repository from zynaddsubfx/zyn-fusion-build#43 or zynaddsubfx/zyn-fusion-build#39 and running build-mingw64.sh from the mingw64 shell of my MSYS2 installation.

Steps:

  1. run the zynaddsubfx.exe standalone
    -> a console window is opened and the last line printed is: [INFO:ZYN] zest_tick()
    Then a frame for the ZynFusion GUI is displayed but the content stays black.
  2. Drag the ZynFusion frame so that the GUI is (partially/completely) outside of the screen area
  3. Drag the ZynFusion frame back to the center of the screen
    -> additional log messages are printed to the console:
[INFO:Zyn] zest_open()
...
[INFO:Zyn] zest_setup()
[Debug:Zyn] setting up animation fps

-> GUI is drawn in those areas that were outside of the screen area in step 2
4. Interact with GUI using the mouse
-> GUI is not refreshed/redrawn
5. Repeat steps 2 + 3
->GUI is only refreshed in those areas that were outside of the screen area in step 2

@DerAndere1
Copy link
Author

I found this forum thread about a similar Issue with Qt: https://forum.qt.io/topic/51003/window-partially-refreshed/16

@fundamental
Copy link
Member

fundamental commented Aug 11, 2020 via email

@DerAndere1
Copy link
Author

DerAndere1 commented Aug 11, 2020

I can confirm that this bug is not present in my Zyn-Fusion build for Windows 64 bit from 29.04.2018 . So a new version of some component is indeed likely causing the issue.

@fundamental
Copy link
Member

Possibly fixed by mruby-zest/mruby-zest-build#30 if this doesn't resolve, feel free to reopen (we really ought to get around to an updated binary release at some point...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants