[Qgis-developer] Native file dialog bugs and the new Save As Vector functionality.

[John C. Tull]

Hi Borys,

You've made some good points. Seems likely something that the broader community should weigh in on.

From my perspective, I agree that the multi-dialog window thing is unusual. On the other hand, the problems that are created from the qt dialogs on my OS are more annoying. Perhaps this needs to be a user-configurable option. Have both types of dialog available based on a choice in the application options. Is this feasible?

John

On Mar 19, 2010, at 12:59 PM, Borys Jurgiel wrote:

> Dnia piątek, 19 marca 2010 o 16:53:27 John C. Tull napisał(a):
>> Hi Borys,
>> 
>> On OS X, the native dialog seems to do what it should. Saving a layer to an
>> ogr format brings that same format as the default the next time you choose
>> save as. I am not sure of other problems that you are experiencing on kde,
>> but things seem fine on OS X.
> 
> Hi John,
> 
> I'm pretty sure it's related only to the KDE4 native dialog. Other problems 
> are: the last used directory is set as the initial file name, instead of 
> entering into it and the save button is labeled "Open".
> 
>> I would recommend any change away from the native dialog be specific to
>> kde. The non-native dialogs on OS X are very awkward and clunky. In fact,
>> it would be great to make  an effort to bring native dialog support to all
>> existing ui elements (native in the application as well as plugins).
> 
> The KDE problem has just provoked me to think about choosing one of them. 
> I admit the native dialogs are far prettier, but are less usable. The main 
> problem is native dialogs can't contain encoding and CRS selectors. The 
> present two-step saving is very inconvenient for me (I assume in most cases 
> you don't change the layer CRS) and there is an urgent need of implementing 
> some kind of encoding selector. Adding a third step wolud be quite ridiculous, 
> but for non-English users a possibility of switching between utf and cp 
> encoding is essential.
> 
> The same problem is with opening a vector layer - I hate that additional 
> dialog (forgive mi guys :D ). 
> 
> I believe we should stick with the encodingFileDialog at least as long as ESRI 
> uses cp encodings :( I know we use the native dialogs in a few places, but it 
> is one of the most painful problems my users meet. It makes QGIS just 
> incompatible with shapefiles from ESRI.
> 
> B.