On Wednesday 08 January 2014 21:24 David Greaves wrote:
> The original intention was to offer a range of functionality to suite
> different skill levels.
And the intention is much appreciated especially for n00bs like me :)
It only needs a bit of tweaking:
1. Disable updating the yaml all togethe
The original intention was to offer a range of functionality to suite different
skill levels.
Essentially "the Qt way" is to use the .pro files to specify things like
myapp.files/myapp.path and INSTALLS += myapp. That should drive the Files:
section of the yaml. To avoid making experience Qt devs
Indeed, as a novice with rpm I always open .yaml it in kate.
On 01/08/2014 06:06 PM, christopher.l...@thurweb.ch wrote:
seconded: So far I have not seen the benefit of a dedicated editor: It
does not make it any easier for the novice to understand what the
entries are for, so why this dedicate
seconded: So far I have not seen the benefit of a dedicated editor: It
does not make it any easier for the novice to understand what the
entries are for, so why this dedicated Editor?
mfg
Chris
Zitat von "Luciano Montanaro" :
But anyway, it changes it in a way that fails the validator
But anyway, it changes it in a way that fails the validator I
would prefer if it left it alone after creation.
Also, I find the custom form editor is an anti-feature...
* it gets in the way as soon as the .yaml file gets complex
* it has fixed-size text box, and to undo the changes one has t
Technically I think it's a feature, QtC plugin just doesn't expect .yaml to
be changed in a way you changed it :)
Anyway, someone from Jolla team already told they were going to disable the
.yaml autoupdate or at least make it optional. Meanwhile version control is
your friend. Or as I also do it,
Oh, it's a bug?!
https://together.jolla.com/question/10996/bug-qt-creator-reorders-yaml-file-for-no-apparent-reason/
BR.
Sven
On 06.01.2014, at 00:39, Thomas Tanghus wrote:
> On Sunday 05 January 2014 14:12 Putze Sven wrote:
>> IMHO the .yaml file is (partly) rewritten if something changes in y
On Sunday 05 January 2014 14:12 Putze Sven wrote:
> IMHO the .yaml file is (partly) rewritten if something changes in your .pro
> file,
Which is good to start with, but f* annoying in the long run, firstly
because it's writing full paths as in /usr/share instead of %{_datadir} and
insists in
Hi Sven
I am not sure. The vanishing happens as soon as I hit command S (to
save the changes).
Chris
Zitat von "Putze Sven" :
Hi,
IMHO the .yaml file is (partly) rewritten if something changes in
your .pro file, could this be your problem here?
BR.
Sven
On 29.12.2013, at 17:48, chris
Hi,
IMHO the .yaml file is (partly) rewritten if something changes in your .pro
file, could this be your problem here?
BR.
Sven
On 29.12.2013, at 17:48, christopher.l...@thurweb.ch wrote:
> Hi All
>
> If add a new dependency to the a projects .yaml file via the QtCreator yaml
> file editor,
Hi All
If add a new dependency to the a projects .yaml file via the QtCreator
yaml file editor, then immediately hit "cmd S" to save the changes,
then more often than not the new entry vanishes, and i have to repeat
the process.
So far I have not established exactly what pattern of circum
11 matches
Mail list logo
