[r200] NWjs several folder bugs

Bugs will be moved here once resolved.

Post » Sun Apr 12, 2015 1:48 am

Problem Description
This contains 2 bugs with the NWjs Open folder dialog together with ChosenPath and ListAt.

1. Problem:
The open dialog doesn't return the path to a folder as stated in the manual.

Show folder dialog
Open a dialog allowing the user to pick a folder on their local system. If the user selects OK, On folder dialog OK triggers and the ChosenPath expression contains the selected folder.


Doing a simple test, I made a folder which I select with the open folder dialog. Instead of giving the path to the folder as stated in the manual. It gives a path to all the files in the folder.

Image

2. Problem
Since Open dialog doesn't return the folder, ListAt(index) doesn't work with chosen path.

Image

Replacing the chosenPath with a fixed path it works correctly.
Image

These problems ruins a huge part of the "Open folder dialog" and listAt, since they are not compatible.

Please fix these problems its really beyond just annoying, that there are so many lacks, bugs and problems with the NWjs functionality in general. :(
Even if the open dialog is working as intended please make it more solid, so NWjs is able to return what users actually need and not just some random stuff. (Drive, Folder, File and Complete path as separate options, that can then be used and combined as we need them.)

Attach a Capx
https://dl.dropboxusercontent.com/u/109921357/More%20nwjs%20bugs/Nwjs_bugs.capx

Description of Capx
Just open a folder to be used with the ListAt funtionality

Steps to Reproduce Bug
Use open folder dialog, ChosenPath and ListAt

Observed Result
Open dialog folder is unable to return the path to the folder.

Expected Result
Returns every single file and subfolder in the selected folder.

Affected Browsers
  • Chrome: (YES)
  • FireFox: (YES)
  • Internet Explorer: (YES)

Operating System and Service Pack
Windows 7

Construct 2 Version ID
r200
B
44
S
11
G
2
Posts: 1,182
Reputation: 6,848

Post » Tue Apr 14, 2015 1:47 pm

I can't reproduce either problem. It works correctly here with the latest NW.js (0.12.0).

Please only report one issue per post BTW, otherwise it can get very confusing what the status of the report is.
Scirra Founder
B
399
S
236
G
89
Posts: 24,530
Reputation: 195,402

Post » Tue Apr 14, 2015 7:46 pm

Sure Ill stick to one problem. Just thought it would be easier since in the example they are related. But im not sure which version of NW.js I use so ill get the newest version and do another test. And see if it have been fixed.

Would it be possible for you to make a link to it as well in the Download stable and beta release. Since I remember that its no longer part of the download right? Its not crucial but just thought it would be handy.
B
44
S
11
G
2
Posts: 1,182
Reputation: 6,848


Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 3 guests