Re: Non-native dialog

On 18/09/2018 19:24, Jürgen Spitzmüller wrote: Am Dienstag, den 18.09.2018, 19:06 +0200 schrieb Daniel: Maybe, I am not sure. The screenshot you send is an all purpose purpose widget for opening files and creating new ones from templates. But what you have in mind seems to be restricted to

Re: Non-native dialog

Am Dienstag, den 18.09.2018, 19:06 +0200 schrieb Daniel: > Maybe, I am not sure. The screenshot you send is an all purpose > purpose > widget for opening files and creating new ones from templates. But > what > you have in mind seems to be restricted to templates only. Templates, examples, UI

Re: Non-native dialog

On 18/09/2018 17:34, Jürgen Spitzmüller wrote: Am Di., 18. Sep. 2018 um 13:26 Uhr schrieb Daniel >: I thought the widget is opened via the menu and then from within the widget one can open the native file dialog. But maybe I misunderstood. In the widget, you

Re: Non-native dialog

Am Di., 18. Sep. 2018 um 13:26 Uhr schrieb Daniel : > I thought the widget is opened via the menu and then from within the > widget one can open the native file dialog. But maybe I misunderstood. > In the widget, you can directly click on a file, which is then opened. Alternatively, you can

Re: Non-native dialog

On 18/09/2018 15:13, Jean-Marc Lasgouttes wrote: Le 18/09/2018 à 15:06, Daniel a écrit : On 18/09/2018 08:45, Jean-Marc Lasgouttes wrote: Le 17/09/2018 à 19:34, Jürgen Spitzmüller a écrit : I wonder if a better solution is a widget that collects (and maybe categorizes) files from given paths

Re: Non-native dialog

Le 18/09/2018 à 15:06, Daniel a écrit : On 18/09/2018 08:45, Jean-Marc Lasgouttes wrote: Le 17/09/2018 à 19:34, Jürgen Spitzmüller a écrit : I wonder if a better solution is a widget that collects (and maybe categorizes) files from given paths and let you click on it. Like LibreOffice has it

Re: Non-native dialog

On 18/09/2018 08:45, Jean-Marc Lasgouttes wrote: Le 17/09/2018 à 19:34, Jürgen Spitzmüller a écrit : I wonder if a better solution is a widget that collects (and maybe categorizes) files from given paths and let you click on it. Like LibreOffice has it (see attachment, although LyX's definitely

Re: Non-native dialog

On 18/09/2018 08:18, Jürgen Spitzmüller wrote: Am Montag, den 17.09.2018, 21:28 +0200 schrieb Daniel: I am wondering why the templates from the library directory are not copied to the templates directory in the user directory. Is there a specific reason for this? If we copied those, then we

Re: Non-native dialog

Le 17/09/2018 à 19:34, Jürgen Spitzmüller a écrit : I wonder if a better solution is a widget that collects (and maybe categorizes) files from given paths and let you click on it. Like LibreOffice has it (see attachment, although LyX's definitely would look different). This would open fro the

Re: Non-native dialog

Am Montag, den 17.09.2018, 21:28 +0200 schrieb Daniel: > I am wondering why the templates from the library directory are not > copied to the templates directory in the user directory. Is there a > specific reason for this? If we copied those, then we effectively abandon the system directory.

Re: Non-native dialog

On 17/09/2018 21:28, Daniel wrote: On 17/09/2018 19:34, Jürgen Spitzmüller wrote: Am Montag, den 17.09.2018, 10:37 +0200 schrieb Daniel: I am sorry if I have not overlooked it, but I couldn't find *any* argument in the ticket (other than it's "horrible UI", which seems question begging). I

Re: Non-native dialog

On 17/09/2018 19:34, Jürgen Spitzmüller wrote: Am Montag, den 17.09.2018, 10:37 +0200 schrieb Daniel: I am sorry if I have not overlooked it, but I couldn't find *any* argument in the ticket (other than it's "horrible UI", which seems question begging). I have to try to find the mail

Re: Non-native dialog

On 17/09/2018 18:06, Daniel wrote: On 17/09/2018 09:32, Jürgen Spitzmüller wrote: Am Montag, den 17.09.2018, 09:12 +0200 schrieb Daniel: Hi, FYI, on Windows 10 the non-native file dialog, activated with \use_native_filedialog false, causes a severe reduction in functionality. In particular,

Re: Non-native dialog

On 17/09/2018 09:32, Jürgen Spitzmüller wrote: Am Montag, den 17.09.2018, 09:12 +0200 schrieb Daniel: Hi, FYI, on Windows 10 the non-native file dialog, activated with \use_native_filedialog false, causes a severe reduction in functionality. In particular, it does not show the custom quick

Re: Non-native dialog

On 17/09/2018 10:37, Daniel wrote: I am sorry if I have not overlooked it ps. Should be "I am sorry if I have overlooked it" of course.

Re: Non-native dialog

On 17/09/2018 09:32, Jürgen Spitzmüller wrote: Am Montag, den 17.09.2018, 09:12 +0200 schrieb Daniel: Hi, FYI, on Windows 10 the non-native file dialog, activated with \use_native_filedialog false, causes a severe reduction in functionality. In particular, it does not show the custom quick

Re: Non-native dialog

Am Montag, den 17.09.2018, 09:12 +0200 schrieb Daniel: > Hi, > > FYI, on Windows 10 the non-native file dialog, activated with > > \use_native_filedialog false, > > causes a severe reduction in functionality. In particular, it does > not > show the custom quick access folders. I guess that is

Non-native dialog

Hi, FYI, on Windows 10 the non-native file dialog, activated with \use_native_filedialog false, causes a severe reduction in functionality. In particular, it does not show the custom quick access folders. I guess that is why it is not turned on by default and might never be so. However, I