nwjsv0130rc1 border bug

0 favourites
  • 11 posts
From the Asset Store
Match same tiles with each other as fast as you can and earn more score during a limited time!
  • More inconsistencies from Nwjs

    The export window border is different than the preview border

    https://dl.dropboxusercontent.com/u/666 ... erbug.capx

    The capx is just a 640 x 480 layout: no events

    Steps to Reproduce Bug

    • Step 1 run preview
    • Step 2 note border
    • Step 3 export to nwjs
    • Step 4 note change in border

    Observed Result

    Unwanted extra pixels in export border

    Expected Result

    Export should look like a normal window for its os.

    Operating System and Service Pack

    w 10

    Construct 2 Version ID

    Beta Release (r224)

  • What export options for NW.js did you use?

    I just tried and only had the 'Window frame' option ticked, and it looks the same as the preview window to me.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • The same.

    Here's a screen of the 32 bit:


    Its not 640 x 480 even though the project is set to that size.

    A separate bug?


  • Just changed the size of the preview with my mouse to a much smaller size.

    Guess what the export showed up as...... yep, same as preview

    Ashley something in the preview is carrying over to the export.

  • Mind uploading the exported game (win32 please)? I want to take a look but I don't want to install the new NW.JS until these sorts of bugs are ironed out.

    If you open the exported game's package.nw file (it can be read as a zip file) and then open the package.json manifest (can be read as a txt file) you can see what the starting width and height of the game are set at. You can also add a maximum width and maximum height to that file.

  • Looks like someone here is having the same issue: https://github.com/nwjs/nw.js/issues/4493

  • https://dl.dropboxusercontent.com/u/666516/win32.zip

    I probably wont leave it up long.

    Its 46 mb's of nothing.

  • Does this still happen in NW.js 0.13.0-rc4? What about if you rename the project?

  • The preview now launches to a set size, as does the export.

    However, it is the wrong size. It looks as if it is making the window size, the layout size, with an additional few pixels of padding.

    Resizing the preview no longer affects the next preview, or the export.

    Renaming the project appears to do nothing.

    Note that the preview is resizable, but the export isn't. (with drag handlers)

  • As far as I can tell there was a change in how NW handles the windows when it migrated from 012 to 013. For my game I've just left a bit of extra padding in the window size compared to the view-port size, then stopped the window from being freely resizable.

  • Have you tried deleting the temp folder manually in "%WINDOWS_DRIVE%\Users\%USERNAME%\AppData\Local"?

    The folder will be named as your project.

    Some weird stuff happened to me in the past when I updated NW.js and that fixed it.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)