Re: [Qbs] Qt Quick Tests and custom import paths

2018-05-17 Thread Christian Kandeler
On Thu, 17 May 2018 14:59:31 +0200 wrote: > It does, I use following quite a lot: >   > property var foo: (function (arg1, arg2) { return arg1 + arg2; }) > property var elsewhere: foo() Yes, for the project resolution phase it's fine. But using the function in a rule

Re: [Qbs] Qt Quick Tests and custom import paths

2018-05-17 Thread resurrection
It does, I use following quite a lot:   property var foo: (function (arg1, arg2) { return arg1 + arg2; }) property var elsewhere: foo()   __ Od: Christian Kandeler Komu: qbs@qt-project.org Datum: 17.05.2018

Re: [Qbs] Qt Quick Tests and custom import paths

2018-05-17 Thread Federico Frenguelli
> What do you mean by that? > > > Is it possible to access a product's properties from the artifact? > > Artifact objects have a "product" property, which gives you the product > object. > My idea was to define a custom property in the test Product like the "qmlImportPaths" property that is used

Re: [Qbs] Qt Quick Tests and custom import paths

2018-05-17 Thread Christian Kandeler
On Thu, 17 May 2018 10:57:31 +0200 Federico Frenguelli wrote: > On Thu, 17 May 2018 at 10:25, Christian Kandeler > wrote: > > > On Wed, 16 May 2018 18:01:40 +0200 > > Federico Frenguelli wrote: > > > > > > If functions were

Re: [Qbs] Qt Quick Tests and custom import paths

2018-05-17 Thread Federico Frenguelli
On Thu, 17 May 2018 at 10:25, Christian Kandeler wrote: > On Wed, 16 May 2018 18:01:40 +0200 > Federico Frenguelli wrote: > > > > If functions were properly supported as properties, there'd be a simple > > > generic solution: > > > > > >

Re: [Qbs] Qt Quick Tests and custom import paths

2018-05-17 Thread Christian Kandeler
On Wed, 16 May 2018 18:01:40 +0200 Federico Frenguelli wrote: > > If functions were properly supported as properties, there'd be a simple > > generic solution: > > > > AutotestRunner { > > additionalArgsFunc: function(testArtifact) { > > var myArgs = []; > >