Sorry Rémi, I was anticipating.
This is harcoded right now and the option does not exists yet. I'm unsure
if adding an option can be backported to QGIS 3.4 unfortunately.
Bes regards
Régis
Le ven. 22 mars 2019 à 15:29, Régis Haubourg a
écrit :
> Hi Rémi,
> you can use the global settings ini f
Salut Régis,
Thanks for your answer and link.
I'm already shipping QGIS with custom INI file, what I'm looking for is the
parameter to set the default project format. And then put it in my
QGIS3.ini.
Or did I miss something in your link?
Rémi
--
Sent from: http://osgeo-org.1560.x6.nabble.com
Hi Rémi,
you can use the global settings ini file to override default option for
QGIS.
There is an option to start QGIS with another default setting file
--globalsettingsfile
https://docs.qgis.org/testing/en/docs/user_manual/introduction/qgis_configuration.html#running-qgis-with-advanced-settings
Hi all,
Matthias Kuhn 🌍 wrote
> Currently I'm inclined to prefer Andreas' proposal to have a
> (well-hidden advanced) setting to let power-users and admins switch the
> default format.
I would like to know if this possiblity of using a setting to set default
format has been implemented?
I'm cur
Hi Nyall,
On 22/01/19 02:28, Nyall Dawson wrote:
> Right, fixed:
> https://github.com/qgis/QGIS/pull/8932
you hero. thanks.
--
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
QGIS-Developer
On Tue, 22 Jan 2019 at 08:51, Nyall Dawson wrote:
>
> On Tue, 22 Jan 2019 at 01:13, Régis Haubourg wrote:
> >
> > Hi Paolo,
> > I think you issue list is a bit pessimistic. Looking a issues mentionning
> > qgz in the subject, we find only 3-4 issues:
> >
> > - One with user account names on wind
That's good news, thanks.
Il 21 gennaio 2019 23:51:38 CET, Nyall Dawson ha
scritto:
>On Tue, 22 Jan 2019 at 01:13, Régis Haubourg
>wrote:
>>
>> Hi Paolo,
>> I think you issue list is a bit pessimistic. Looking a issues
>mentionning qgz in the subject, we find only 3-4 issues:
>>
>> - One with u
On Tue, 22 Jan 2019 at 01:13, Régis Haubourg wrote:
>
> Hi Paolo,
> I think you issue list is a bit pessimistic. Looking a issues mentionning qgz
> in the subject, we find only 3-4 issues:
>
> - One with user account names on windows with special characters #20562
> - probably to related to spec
On Mon, 21 Jan 2019 at 23:57, Matthias Kuhn wrote:
> >> - give up qgz and bet on another option to offer a container (geopackage )
> -1, I think we shouldn't turn into a road where we'll wonder how to
> embed shapefiles and friends into a sqlite based format ;P
Agreed, I'm very much against a sw
Hi Richard,
Feel free to write something!
We need people able to take advantage of the *.qgz format. As Matthias
said, I like the *.qgz format "for the possibilities it will offer in
the future".
But we need to solve the problems reported by users quickly.
See you in 41 days,
Jorge
Às 20:09 d
On 1/21/19 5:27 PM, Jorge Gustavo Rocha wrote:
> Edit once the ~/.vimrc and add the line:
> au BufReadCmd *.qgz call zip#Browse(expand(""))
>
> Afterwards, you just need to:
> 1) vim project.qgz
> and it open the project. Hit enter on top of the project.qgs file and
> make your changes.
Cool, Wo
Hi Jorge,
cool tips thanks!
Le lun. 21 janv. 2019 à 17:27, Jorge Gustavo Rocha a
écrit :
> Hi,
>
> Just 0,20 € for editing the *.qgs file inside the *.qgz.
>
> Windows users:
>
> 7zip is able to edit the file in place. By default, it uses Notepad,
> which is not very useful. But you con configur
Hi,
Just 0,20 € for editing the *.qgs file inside the *.qgz.
Windows users:
7zip is able to edit the file in place. By default, it uses Notepad,
which is not very useful. But you con configure a nice editor (notepad++
or another) in the 7zip options. I don't use Windows, but I've launched
one ju
Sorry I was not clear: I meant that in the list you can find several
issues deriving from qgz, as already pointed out.
All the best.
On 21/01/19 16:12, Régis Haubourg wrote:
> Hi Paolo,
> I think you issue list is a bit pessimistic. Looking a issues
> mentionning qgz in the subject, we find only 3
Ok thanks René Luc,
so we have three issues to solve. That's not something that deserves
killing qgz by itself. Let's push that into the bugfix run.
Régis
Le lun. 21 janv. 2019 à 16:13, René-Luc Dhont a écrit :
> On windows, the user with an accent in the account name can create the
> project as
Hi Paolo,
I think you issue list is a bit pessimistic. Looking a issues mentionning
qgz in the subject, we find only 3-4 issues:
- One with user account names on windows with special characters #20562
- probably to related to special characters in filename #19567 / #19446
- one for embbeded layer
On windows, the user with an accent in the account name can create the
project as a QGZ file but can't save the updated project as a QGZ file.
In the list provided by
Paolo,https://issues.qgis.org/projects/qgis/issues?category_id=35&set_filter=1&sort=id%3Adesc&status_id=o&subproject_id=%21%2A
Hi René-Luc,
What issues did you face during training? I'm afraid we won't improve if we
advice to workaround this feature .
Régis
Le lun. 21 janv. 2019 à 16:00, René-Luc Dhont a écrit :
> Hi all,
>
> During training, I discourage to use .qgz and auxiliary storage. I force
> users to save projec
Hi all,
During training, I discourage to use .qgz and auxiliary storage. I force
users to save project as .qgs to avoid issues.
It is not stable yet for me.
René-Luc
Le 21/01/2019 à 15:54, Paolo Cavallini a écrit :
Hi all,
On 21/01/19 14:40, Hugo Mercier wrote:
I would vote for your 3rd p
Hi all,
On 21/01/19 14:40, Hugo Mercier wrote:
> I would vote for your 3rd proposition: replace xml hacking by something
> that looks like calls to an API.
> And adding an option for those who want to switch back to .qgs +
> separated aux files, keeping the default to .qgz.
moreover, there are a
>My first reaction is "please KISS", the XML project is already
complicated, so I would stick to option 1.
Well, qgz adressed a really common caveat: Users just didn't know anything
about auxiliary data qgd files (the same as for Memory Layer Saver plugin
.mldata files) and lost data when sharing
My first reaction is "please KISS", the XML project is already complicated,
so I would stick to option 1.
About usability, I really don't mind it. Having a zipped file is convenient
when... I make a mess, editing the project file.
There is already an enhancement proposal to optionally save the proj
Hi all,
I like the qgz format for the possibilities it will offer in the future.
But have to agree at the moment we are missing many of the advantages
while the drawbacks become apparent.
On 1/21/19 2:40 PM, Hugo Mercier wrote:
> Hi,
>
> On 21/01/2019 14:19, Régis Haubourg wrote:
>> I really don'
Hi,
On 21/01/2019 14:19, Régis Haubourg wrote:
> Hi all,
>
> The initial plan - discussed some years ago on the lists - was to have a
> container so that we can embed resources along the project file, and
> open the door to a lot of nice features for sharing qgis projects.
> The auxiliary data wo
Hi all,
The initial plan - discussed some years ago on the lists - was to have a
container so that we can embed resources along the project file, and open
the door to a lot of nice features for sharing qgis projects.
The auxiliary data work was the opportunity to add this optional format and
check
Hi all,
No, Andreas, you are not alone. I was planning to write to the list for the
same reason. thanks.
I'm not sure how many users rely on qgd data yet, but I find it annoying
when using a simple and basic project to have it in qgz format by default
(and losing the so good "find and replace" in
Hi QGIS devs,
Am I the only QGIS user that finds it a bit annoying that .qgz is now
the default format instead of .qgs (plain text format)?
I really often look into the .qgs files, or I create scripts that
process them or find and replace stuff in text editor.
Now I always have to unzip fir
27 matches
Mail list logo
