On Sunday 26 January 2014 18:53:42 Gregor Mi wrote:
> With another addition to qfiledialogtest in
> frameworks/frameworkintegration another potential bug can be exposed:
>
> Calling
>
> $ ./qfiledialogtest --nameFilter "c (*.cpp)" --nameFilter "h (*.h)"
> --selectNameFilter "h (*.h)"
>
> does no
On Tuesday 28 January 2014 15:05:30 Kevin Funk wrote:
> Am Sonntag, 26. Januar 2014, 18:53:42 schrieb Gregor Mi:
> > With another addition to qfiledialogtest in
> > frameworks/frameworkintegration another potential bug can be exposed:
> >
> > Calling
> >
> > $ ./qfiledialogtest --nameFilter "c (*
On Tuesday 28 January 2014 15:05:30 Kevin Funk wrote:
> Am Sonntag, 26. Januar 2014, 18:53:42 schrieb Gregor Mi:
> > With another addition to qfiledialogtest in
> > frameworks/frameworkintegration another potential bug can be exposed:
> >
> > Calling
> >
> > $ ./qfiledialogtest --nameFilter "c (*
On 28/01/14 15:05, Kevin Funk wrote:
> Am Sonntag, 26. Januar 2014, 18:53:42 schrieb Gregor Mi:
>> With another addition to qfiledialogtest in
>> frameworks/frameworkintegration another potential bug can be exposed:
>>
>> Calling
>>
>> $ ./qfiledialogtest --nameFilter "c (*.cpp)" --nameFilter "h
Am Sonntag, 26. Januar 2014, 18:53:42 schrieb Gregor Mi:
> With another addition to qfiledialogtest in
> frameworks/frameworkintegration another potential bug can be exposed:
>
> Calling
>
> $ ./qfiledialogtest --nameFilter "c (*.cpp)" --nameFilter "h (*.h)"
> --selectNameFilter "h (*.h)"
Works
With another addition to qfiledialogtest in
frameworks/frameworkintegration another potential bug can be exposed:
Calling
$ ./qfiledialogtest --nameFilter "c (*.cpp)" --nameFilter "h (*.h)"
--selectNameFilter "h (*.h)"
does not select the second filter. Can this be confirmed or maybe I am
using