https://bugs.winehq.org/show_bug.cgi?id=57676
Bug ID: 57676 Summary: Dn-FamiTracker 0.5.1.1: most of instrument editor is blank Product: Wine Version: 10.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: wine@pineight.com Distribution: ---
When opening an instrument for editing, most controls in the instrument editor don't get drawn, leaving a blank space where they should be.
Wine version: 10.0-rc5 from dl.winehq.org repository Distribution: Xubuntu 24.04 amd64 Graphics: X.Org X Window System 7.7+23ubuntu3, Mesa Intel(R) HD Graphics 5500 (BDW GT2), Mesa 24.0.9-0ubuntu0.3
Program identifiers Download page: https://github.com/Dn-Programming-Core-Management/Dn-FamiTracker/releases/ta... SHA-1 hashes: 97024e66beed59c61580ea4a23bea25185440323 /<redacted>/Dn-FamiTracker_v0511_x64_Release.7z 201990bcb93c72d47061fe69eb3fc6599518d5e1 /<redacted>/Dn-FamiTracker.exe
Steps to reproduce: 1. Download Dn-FamiTracker_v0511_x64_Release.7z and extract it to a new folder. 2. Open Dn-FamiTracker.exe. 3. At top right is a list of instruments that begins with "[2A03] 00 -". Double-click the "00 -" to open the instrument editor. 4. The "Instrument editor" floating window appears. It has two panes, with tabs "2A03 settings" and "DPCM samples".
Behavior on Windows and Wine 9.x: To the left side is an "Instrument settings" group containing a list of effects "Volume, Arpeggio, Pitch, Hi-pitch, Duty / Noise", button "Select next empty slot", and a combo box labeled "Sequence #". To the right is a "Sequence editor" group with a graph, "Size: [-] 0 [+]" and a text input to enter a volume sequence as numbers. At bottom is a piano keyboard.
Behavior on Wine 10.0-rc5: Everything in pane "2A03 settings" other than the graph and the piano keyboard is blank. Switching to pane "DPCM samples" and back to pane "2A03 settings" reveals the hidden controls.
https://bugs.winehq.org/show_bug.cgi?id=57676
--- Comment #1 from Damian Yerrick wine@pineight.com --- Workaround: Dn-FamiTracker has different instrument types, which apply to different expansion chips selected in Module > Module Properties.
1. "2A03" and "N163" have two tabs. The workaround is to switch back and forth between tabs before editing an instrument. 2. "VRC6" and "Sunsoft 5B" instrument editors have one tab. The workaround to force other controls on the page to be drawn is more complicated. First hold the Tab key to focus "Select next empty slot", the Sequence # combo box, and the sequence text input. Then tab to "Volume" again and press Down to focus the other effects to cause them to be drawn. Then place the pointer over where the "Effect name" heading, and size control would be to cause them to be drawn. 3. "FDS" and "VRC7" instrument editors appear unaffected by this defect.
AppDB note: Dn-FamiTracker is actively maintained yet not in AppDB. It is the successor to FamiTracker, which is in AppDB but has not produced a stable release in roughly a decade.
Console log and screenshots of the instrument editor are forthcoming.
https://bugs.winehq.org/show_bug.cgi?id=57676
--- Comment #2 from Damian Yerrick wine@pineight.com --- Created attachment 77856 --> https://bugs.winehq.org/attachment.cgi?id=77856 Console log (wine Dn-FamiTracker.exe &> log.txt) while viewing the instrument editor
https://bugs.winehq.org/show_bug.cgi?id=57676
--- Comment #3 from Damian Yerrick wine@pineight.com --- Created attachment 77857 --> https://bugs.winehq.org/attachment.cgi?id=77857 Controls not drawn after opening the instrument editor
https://bugs.winehq.org/show_bug.cgi?id=57676
--- Comment #4 from Damian Yerrick wine@pineight.com --- Created attachment 77858 --> https://bugs.winehq.org/attachment.cgi?id=77858 Controls drawn after switching back and forth between panes
https://bugs.winehq.org/show_bug.cgi?id=57676
Béla Gyebrószki gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://github.com/Dn-Progr | |amming-Core-Management/Dn-F | |amiTracker/releases/tag/Dn0 | |.5.1.1 Keywords| |download, regression Regression SHA1| |51b16963f6e0e8df43118deac63 | |f640aee4698b7 CC| |gyebro69@gmail.com, | |rbernon@codeweavers.com
--- Comment #5 from Béla Gyebrószki gyebro69@gmail.com --- I can reproduce the problem but only in Wine's fullscreen mode and not in virtual desktop mode.
The regression was caused by commit 51b16963f6e0e8df43118deac63f640aee4698b7 win32u: Always update the surface regions in apply_window_pos.
The patch from bug #57665 fixes the problem in this application too.
wine-10.0-rc5-13-gf1b2e2ca1bb XFCE 4.20 X.Org 1.21.1.15 Nvidia 565.77
https://bugs.winehq.org/show_bug.cgi?id=57676
Damian Yerrick wine@pineight.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|10.0-rc5 |10.0-rc6
--- Comment #6 from Damian Yerrick wine@pineight.com --- Wine 10.0-rc6 still shows the misbehavior.
https://bugs.winehq.org/show_bug.cgi?id=57676
--- Comment #7 from Rémi Bernon rbernon@codeweavers.com --- Created attachment 77894 --> https://bugs.winehq.org/attachment.cgi?id=77894 Tentative fix
I don't reproduce the issue, but if you can does the attached patch helps? It fixes bug 57665 for me.
https://bugs.winehq.org/show_bug.cgi?id=57676
--- Comment #8 from Béla Gyebrószki gyebro69@gmail.com --- (In reply to Rémi Bernon from comment #7)
Created attachment 77894 [details] Tentative fix
I don't reproduce the issue,
In winecfg Graphics tab enable the option <Allow the window manager to control the window>. That's the way I reproduced the problem (but only in Wine's fullscreen mode). The problem doesn't occur in virtual desktop mode for me.
but if you can does the attached patch helps? It fixes bug 57665 for me.
I got inconsistent results with the patch: seems to fix the problem when <No theme> is selected in winecfg, but the problem remains with the <Light> theme. Actually, every second attempt to run the application with your patch applied resulted in the normal behavior so I'm lost here..
This was tested on XFCE4.20, XOrg and Nvidia binary drivers. The bug reporter may have a different outcome though.
https://bugs.winehq.org/show_bug.cgi?id=57676
--- Comment #9 from Damian Yerrick wine@pineight.com --- Would I need to learn to build Wine from source code in order to provide useful feedback for this bug?
https://bugs.winehq.org/show_bug.cgi?id=57676
--- Comment #10 from Damian Yerrick wine@pineight.com --- wine-10.0 still shows misbehavior
https://bugs.winehq.org/show_bug.cgi?id=57676
--- Comment #11 from Damian Yerrick wine@pineight.com --- wine-10.1 still shows misbehavior
-
WineHQ Bugzilla