Dialogs don't work on Linux

[fasterthanlime]

Any of the following:

• New file
• Delete file
• Rename file
• Rename variable

Don't seem to work on Linux at all.

I'm on branch unstable (but the above all work on OSX at the exact same commit).

Here's hopefully relevant info:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 8.0 (jessie)
Release:    8.0
Codename:   jessie

$ npm -g ls nodewebkit
/usr/lib
└── nodewebkit@0.11.4 

Let me know if there's any tests I can run to help figure out what the problem is. I haven't seen anything obvious in the terminal output except:

[21410:1228/233458:ERROR:browser_main_loop.cc(162)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
libGL error: MESA-LOADER: could not create udev device for fd 13
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[21410:1228/233458:ERROR:nss_util.cc(821)] After loading Root Certs, loaded==false: NSS error code: -8018

...the rest of CATS works just fine (great work, btw!) and the nodewebkit devtools don't report anything at all, so I'm out of ideas at this point.

The easy workaround, of course, is to.. not use the rename refactor, and do file management purely from the console. But I like doing it from inside CATS now :)

Edit: I have to mention: Global preferences / Project settings dialogs do work - although sometimes they take a second or two to come up.

[jbaron]

That is strange behaviour indeed. Don’t the context menus appear at all with a right click or when you click on a item in the context menu nothing happens ?

On 28 Dec 2014, at 23:40, Amos Wenger notifications@github.com wrote:

Any of the following:

New file Delete file Rename file Rename variable Don't seem to work on Linux at all.

I'm on branch unstable (but the above all work on OSX at the exact same commit).

Here's hopefully relevant info:

$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.0 (jessie) Release: 8.0 Codename: jessie $ npm -g ls nodewebkit /usr/lib └── nodewebkit@0.11.4 Let me know if there's any tests I can run to help figure out what the problem is. I haven't seen anything obvious in the terminal output except:

[21410:1228/233458:ERROR:browser_main_loop.cc(162)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. libGL error: MESA-LOADER: could not create udev device for fd 13 ATTENTION: default value of option force_s3tc_enable overridden by environment. [21410:1228/233458:ERROR:nss_util.cc(821)] After loading Root Certs, loaded==false: NSS error code: -8018 ...the rest of CATS works just fine (great work, btw!) and the nodewebkit devtools don't report anything at all, so I'm out of ideas at this point.

The easy workaround, of course, is to.. not use the rename refactor, and do file management purely from the console. But I like doing it from inside CATS now :)

— Reply to this email directly or view it on GitHub https://github.com/jbaron/cats/issues/136.

[jbaron]

I think I found an open bug report on nodewebkit that explains this behaviour:

https://github.com/rogerwang/node-webkit/issues/2683

Essentially the alert and confirm dialog are not showing on Linux.

Perhaps a good time to start replacing these native dialogs with Qoodxoo windows. Also gives some more flexibility. Downside is that I have to make the code async (so a call back).

[fasterthanlime]

@jbaron that node-webkit issue would definitely explain it.

I think I could take a stab at it, if you want. How about a basic promptDialog class in src/cats/gui (modelled after configDialog but much simpler) which could replace usages of native prompt?

[jbaron]

That would be great and very much appreciated!!!

Just let me know if anything is unclear ( since there isn't much documentation :)

On 29 dec. 2014, at 17:49, Amos Wenger notifications@github.com wrote:

@jbaron that node-webkit issue would definitely explain it.

I think I could take a stab at it, if you want. How about a basic promptDialog class in src/cats/gui (modelled after configDialog but much simpler) which could replace usages of native prompt?

— Reply to this email directly or view it on GitHub.

[fasterthanlime]

Closed by #137.