-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
The main page is not displayed in Windows7 system #6265
Comments
My package. Json has no problem, |
I try a simple test on Windows 7 x64 with nwjs-sdk-v0.26.2. It works fine. The transparent window displays.
I also try ExamManager.zip you provided in #6217 (comment), the screenshot is: |
The SDK I used was ‘nwjs-sdk-v0.26.2-win-ia32.zip’ |
@onlyou does it run on other 32 bit win7 system ? you might want to clean the nwjs appdata folder |
@jtg-gg I've cleaned up the appdata folder, it's not working |
@jtg-gg |
@onlyou can you test on win7 64bit using nwjs 32bit ? |
@jtg-gg |
@onlyou run with this arguments "--enable-logging --v=1" |
@jtg-gg |
hmm nothing in the log, are you sending the correct one ? |
@jtg-gg |
@onlyou I've just read the log, not much information in there regarding the window |
@jtg-gg |
@onlyou that enable logging is already the best, I'll need to debug on the machine to fix it |
@jtg-gg |
@jtg-gg |
@onlyou hmm you can try "--disable-gpu-compositing --force-cpu-draw" might work |
@jtg-gg |
@onlyou I manage to reproduce this on my other win 10 machine |
@onlyou can you try my sample app here: the sample app, runs as "show": false |
@jtg-gg |
@onlyou I've made a pull request nwjs/chromium.src#100 @rogerwang please accept it, and please also patch nw27 |
This is fixed in git and will be available in the next nightly build. |
NWJS Version :0.26.2
Operating System :
Windows7 32
Expected behavior
<!- What do you think should happen? ->
The main page is not displayed in Windows7 system
It can only be displayed in the toolbar
Actual behavior
It can be shown in 0.26.0 before the upgrade
It might be related to the bug I've been offering to fix, the code is #6217
<!- What actually happens? ->
How to reproduce
<!-
->
The text was updated successfully, but these errors were encountered: