Hi,

please can you create a suggestion task for this in our bugtracker(http://bugreports.qt.nokia.com/secure/CreateIssue.jspa?pid=10561&issuetype=15&Create=Create)? Project "Nokia Qt SDK" is ok for the moment. In the future we will have there a project called installer framework.
And we need the description of your aim for this maybe we/our team have a better idea to resolve it.

Cheers,
--
Tim Jenssen


>Hi,
>
>The Installer::valueChanged() signal sounded promising at first sight, but then I realized that I also wanted to (ab)use the existing warning label show a nice red warning when the chosen target directory is not suitable (similar to what happens when the target directory contains a space). So, could you consider adding the latter solution to the installer fw ie. make the GUI accessible, please?
>
>--
>J-P Nurmi


>>Hi,
>>
>>and sorry for the delay. In short:
>>
>>var page = component.userInterface( "TargetDirectoryPage" ); // is not 
>>working because TargetDirectoryPage is not a script added 
>>userinterface, even it would be one it is not an userinterface of the 
>>current component.
>>What are you aiming?
>>
>>A solution could be:
>>
>>    installer.valueChanged.connect(this, testValueConnect); } 
>>testValueConnect = function(key, value) {
>>    if (key == "TargetDir") {
>>        print("This is called if the user leaves the 
>>TargetDirectoryPage");
>>    }
>>}
>>
>>The other solution would be that I have to add an interface for all 
>>userinterfaces, like it is available in the auto install script:
>>var page = gui.pageWidgetByObjectName( "LicenseAgreementPage" ); //but 
>>this is not working in the component script, because the gui object is 
>>not available there at the moment
>>
>>Best Regards,
>>--
>>Tim Jenssen


>>>Hi Tim and Maurice,
>>>
>>>I’ve been playing around with http://scm.dev.nokia.troll.no/projects/research/repos/installerfw. I’m mocking up a temporary installer for the Qt Components project managers. The project needs to be installed within a compatible Qt installation directory. Therefore I’d like to add some extra sanity checking on the “TargetDirectoryPage”. However, I’m having big problems with trying to connect to the “targetDirectoryLE.textChanged” signal in the package's install script.
>>>
>>>First approach:
>>>
>>>function Component()
>>>{
>>>    var page = component.userInterface( "TargetDirectoryPage" );
>>>    page.targetDirectoryLE.textChanged.connect( this, Component.prototype.targetDirectoryChanged );
>>>   // TypeError: Result of expression 'page' [null] is not an object.
>>>}
>>>
>>>Second approach:
>>>
>>>function Component()
>>>{
>>>    component.loaded.connect( this, Component.prototype.loaded ); }
>>>
>>>Component.prototype.loaded = function()
>>>{
>>>    if (installer.isInstaller()) {
>>>        var page = component.userInterface( "TargetDirectoryPage" );
>>>        page.targetDirectoryLE.textChanged.connect( this, Component.prototype.targetDirectoryChanged );
>>>        // TypeError: Result of expression 'page' [null] is not an object.
>>>    }
>>>}
>>>
>>>
>>>I can see something similar done with custom pages in the com.nokia.sdk.qt.gui example package, but it just doesn't work out for me with built-in pages. Could you guys help me with this, please? How can I delay the connect statement so that "TargetDirectoryPage" has been constructed?
>>>
>>>--
>>>J-P Nurmi