On Mon, 8 Jul 2019 at 22:09, Christian Kandeler <christian.kande...@qt.io> wrote: > I would not bother with any of that. Just update the files. Any halfway > decent IDE will have a watch on the qbs files and re-resolve the project. I'm > not ruling out that manually manipulating the build graph (as we do for file > updates) is possible, but it seems quite ambitious. > > > > > Yes indeed, it looked quite complicated to me. Sounds like a good plan > > to use QtC's watch system > > Actually, a watch system isn't even needed at all, as the IDE knows that it's > told qbs to update the files. So it can just manually schedule a re-parse. In > fact, we actively switch off the watcher for such cases, to suppress the "do > you want to reload" dialog.
I see, but for some reason, it's not auto-reloading, will investigate further, thanks for the tip. > > > i guess the only thing I'm missing is > > saving the edited file on the QtC side, or maybe it's better to do > > that on Qbs side (but wouldn't be consistent with group/file > > add/remove). > > I'm pretty sure we do save the files on the qbs side there. Yes, as Qbs unit tests show, it obviously does happen, but within QtC something is missing... Interesting. Thanks for sharing. Chris _______________________________________________ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs