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 to remove lines one by one I would prefer a .yaml syntax highlighter, with the possibility to highlight syntax errors. But even without highlighting, I would rather use the normal text editor component... as it is, if I have to modify it I have to open the yaml file with vim (I have added a few variables to feed the VERSION to the qmake command line to my project). Regards, Luciano On Tue, Jan 7, 2014 at 9:41 PM, Artem Marchenko <artem.marche...@gmail.com> wrote: > 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, I keep .yaml open in the text editor, so I > can Undo changes there. > > /Artem > > > On Mon, Jan 6, 2014 at 9:39 PM, Sven Putze <sailfish...@hardcodes.de> wrote: >> >> 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 <tho...@tanghus.net> wrote: >> >> > 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 making those "corrections" every time you touch the .pro, >> > secondly >> > because it makes any kind of Continuous Integration close to impossible >> > if you >> > have the IDE open when it's is running. >> > Causes a loop between SDK IDE noticing .pro has been **touched**, not >> > edited, >> > and then updating the .yaml, ending up in git conflicts. >> > *Sigh* - I spend the better part of last night trying to figure out >> > where my >> > very simple scripts went wrong, until I found out it was the freaking >> > SDK that >> > was messing with me :D >> > >> > Sorry, kinda OT but otherwise SDK related ;) >> > >> > -- >> > Med venlig hilsen / Best Regards >> > >> > Thomas Tanghus >> > _______________________________________________ >> > SailfishOS.org Devel mailing list >> >> _______________________________________________ >> SailfishOS.org Devel mailing list > > > > > -- > Artem Marchenko > http://agilesoftwaredevelopment.com > http://twitter.com/AgileArtem > > _______________________________________________ > SailfishOS.org Devel mailing list -- Luciano Montanaro Anyone who is capable of getting themselves made President should on no account be allowed to do the job. -- Douglas Adams _______________________________________________ SailfishOS.org Devel mailing list
