file-dialog | upload file dialog directly from your code | File Upload library

Electron doesn't allow windows with webSecurity: true to load files. You could simply set it to false and get rid of the error but it would make your app unsafe to use.

Instead, what you have to do is to create a custom protocol and then use that for loading files.

The dialog API has been modified with the release of Electron 6.

dialog.showOpenDialog() and other dialog functions now return promises and no longer take callback functions. There also are synchronous counterparts which return the selection result in a blocking fashion, e.g. dialog.showOpenDialogSync().

Example usage (in renderer process)

You can use the emit event in profile dialog for pass event so that you know that form is submitted or not and use persistent so that User cannot dismiss Dialog if clicking outside of it or hitting ESC key; Also, an app route change won't dismiss it.

After chatting and seeing your entire code it seems that the container with the child you try to access is not yet generated on screen because of an *ngFor condition, it is important to note that you can only access a child with @viewChild if it is already generated. Happy to help!

Tkinter runs in a single thread, and the .mainloop() method starts up the thread, which is actually an infinite loop till the user/another event closes the window.

This means that if you create all the widgets that should run in your window and you do not invoke .mainloop(), your code will run but the window will not come up as there is no mainloop() to begin the root Tk loop.

The problem was with Apache POI library which was included as .jar file from /libs directory. This .jar contained empty /META-INF directory which was the cause of the problem.

Deleting this empty directory from .jar file resolved the problem. If /META-INF is not empty it also works ok. With Gradle plugin 2.3.3 building .apk works smoothly even with empty /META_INF directory.

So, the combination of Gradle plugin 3.0.0 and empty /META_INF directory in .jar creates the problem.

UPDATE 27.11.2017 This bug has been fixed in the current version

After staring at the documentation for quite a while I noticed the problem. It was very subtle. Here's the important part from the documentation:

Oops! The properties value is openFile not openFiles.

The red herring was the fact that this did work properly (with the wrong property value) on Linux and Win10.

Here is the fixed code:

The problem probably resides on the different event timings of both hide and show events: I suppose that, until the open function returns, Qt has not yet "registered" the child as a window that will check against the QApplication.quitOnLastWindowClosed() option, meaning that even if the child window is shown for a fraction of time, it still "thinks" that there is only one window (the parent).

According to your requirements there are two possibilities:

• use setQuitOnLastWindowClosed(False) on the application instance, remembering to call quit in the CloseEvent of the parent window (or any other window for which you want to quit on close);
• use a QTimer.singleShot(1, self.hide), which should delay the hiding enough to avoid this problem;

The first solution is usually better and I strongly suggest you to use it.
I'm not even sure that using a one-ms delay would be actually enough to allow the "a new window exists" notification to the application: it might be necessary a higher amount, and that value could also be arbitrary, depending on various conditions (including platform implementation).
According to the source code, as soon as a top level widget is closed it checks against all QApplication.topLevelWidgets(), but according to my tests the list is not immediately updated: the ChildWindow usually "appears" some time after show(), but sometimes (usually <2 ms after) it does not appear in the list at all.

As stated in this AI community posting this is not directly possible. But there is a workaround to accomplish it:

In order to customize permissions for Application Folder\myApp.ini created using the INI File Dialog, create a new physical file with the same name in your filesystem (e.g. c:\installer\myApp\myApp.ini).

In AdvancedInstaller add that file to the same folder where your myApp.ini already resides in: Application Folder in this case. Skip the INI import functionality.

Now it should look like you have two myApp.ini files in your Application Folder and you can edit all the file access permissions on the imported myApp.ini just like you do on any other files or folders. These customizations will be applied to the installed myApp.ini on the target machine.