No menu bar in Windows 10 #305
Comments
|
I see this same issue on windows 10. |
|
I have the same problem as francbenoit and would like to add that running it in compatibility mode does not work, nor does installing it in compatibility mode. |
|
I've been recently contributing to this project and I finally took the time to conduct a Windows build (see #326). I've been using mingw-w64 and Qt 6. I cannot reproduce the issue with my build, at least not when launching it via WINE. When I'm on a Windows system again I'll check how it behaves natively. I conducted that build on a custom branch with some additional commits (see https://github.com/Martchus/PianoBooster/commits/custom) as a few changes were required to make it work. If you'd like to test my build yourself, you can find it here. Note that my build requires Windows 10 or later (64-bit). |
|
I've just tested the build mentioned in my previous comment under Windows 11 and the menu bar appears normally. Maybe this has simply been fixed since you've created the ticket (or rather since the build you've been using has been created). |
|
I just went here:
https://www.pianobooster.org/download.html#windows
and downloaded the latest stable version, which is marked as 1.0.0
I installed it on Windows 10.
I ran Piano Booster. It comes up with no menu. Screenshot attached.
[image: image.png]
…On Sun, Jan 22, 2023 at 2:32 PM Martchus ***@***.***> wrote:
I've just tested the build mentioned in my previous comment under Windows
11 and the menu bar appears normally. Maybe this has simply been fixed
since you've created the ticket (or rather since the build you've been
using has been created).
—
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC3E6SPWKFHEX2DUIRGWKX3WTWYRDANCNFSM5EUCGUWA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
That's a build from 2020. I recommend checking against the latest version, e.g. using my build or by creating your own build. (As per discussion in #317 (comment) it would be great to know whether the current "development state" works before making a new release.) |
|
Sure, although I'm not confident In building my own installation. If it
doesn't work it could be my build is faulty.
If you are interested in whether your set up can see the bug you might want
to install the released installable version that has the bug.
…On Mon, Jan 23, 2023 at 1:05 AM Martchus ***@***.***> wrote:
That's a build from 2020. I recommend checking against the latest version,
e.g. using my build or by creating your own build.
(As per discussion in #317 (comment)
<#317 (comment)>
it would be great to know whether the current "development state" works
*before* making a new release.)
—
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC3E6SPQ6HFK3UOBN35IESLWTZCUJANCNFSM5EUCGUWA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
If it doesn't work it likely won't work at all. That's easy to distinguish from the issue we're discussing here. You could also try my build (https://martchus.no-ip.biz/repo/win/pianobooster-x86_64-w64-mingw32-custom-1316-96d8165eb2910d4a7a9030fef69930f84929696b.zip).
Right, I can try that as well when I'm on Windows again. However, I trust you guys that the issue is real and I don't think there's any special setting in Windows itself that triggers this bug. (The most likely hypothesis is that this bug has simply already been fixed.) |
|
Thanks.
I downloaded your build and ran it, but it doesn't work.
This time I get no GUI, it simply starts to run, looks like it is going to
create a window and then vanishes.
…On Mon, Jan 23, 2023 at 1:27 PM Martchus ***@***.***> wrote:
Sure, although I'm not confident In building my own installation. If it
doesn't work it could be my build is faulty.
If it doesn't work it likely won't work at all. That's easy to distinguish
from the issue we're discussing here. You could also try my build (
https://martchus.no-ip.biz/repo/win/pianobooster-x86_64-w64-mingw32-custom-1316-96d8165eb2910d4a7a9030fef69930f84929696b.zip
).
If you are interested in whether your set up can see the bug you might want
to install the released installable version that has the bug.
Right, I can try that as well when I'm on Windows again. However, I trust
you guys that the issue is real and I don't think there's any special
setting in Windows itself that triggers this bug. (The most likely
hypothesis is that this bug has simply already been fixed.)
—
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC3E6SLRMKNQCKTDM6BQ4WTWT3ZSJANCNFSM5EUCGUWA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Strange. Not even the usual message from Windows when an application crashes? For me it worked in WINE and Windows 11. I'll try Windows 10 later. Note that older versions than Windows 10 won't work (because Qt 6 dropped support for them). |
|
For me it works just fine on Windows 10 as well. |
|
Ok. well, I guess something is incompatible. If you can't reproduce it, you
can't fix it. Thanks for trying.
…On Tue, Jan 24, 2023 at 1:12 PM Martchus ***@***.***> wrote:
For me it works just fine on Windows 10 as well.
—
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC3E6SNTH5UCTAPJL47ARH3WUBASLANCNFSM5EUCGUWA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hello
I installed the application on Windows 10 and i don't have the menu bar to select the files.
thanks
Benoit
The text was updated successfully, but these errors were encountered: