Bug or new feature? Conditions within the GUI - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

RedDrago
Posts: 33
Joined: Thu Jan 19, 2012 9:23 am

Bug or new feature? Conditions within the GUI

Hello,

the first time I saw this, i was wondering if thats som kind of a joke. I have a dialog for registration purpose. If the user does not want to register, he is free to use the software for 30 days. otherwise he'll need a registration from our side. that part was working perfectly in the previous version.

Now with AI version 8.9 I wantet to check if it is still working. And indeed it is... but not the way it should.

the Controls are enabled when the should not, and are disabled when they should be enabled.
And that despite of the fact, that the conditions are set correctly.

The controls to fill in the registration Key should be only enabled if the Checkbox with the Property REGCB has the value "Checked".
The Button "Next" should be enabled if either the Checkbox with the property DEMOCB has the value "Checked" or if REGCB equals Checked and the Proberty LICENSEVALID is set to "VALID".

The condition is defined Control condition is defined as:
Next:
Disabeld: REGCB = Checked AND LICENSEVALID = INVALID
Enabled: DEMOCB = Checked OR LICENSEVALID = VALID

Registration Fields:
Enabled: REGCB = Checked
Disabled: DEMOCB = Checked

Publish Events:
DEMOCB: REGCB = {}
REGCB: DEMOCB = {}

Do you have a idea, what could have caused that weird behavior?

Thank you in advance.
Tobias
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Bug or new feature? Conditions within the GUI

Hi Tobias,

Can you please specify the previous version of Advanced Installer you were using before the upgrade? Also, can you please send us the .AIP ( project file ) to support at advancedinstaller dot com so we can investigate it?

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
RedDrago
Posts: 33
Joined: Thu Jan 19, 2012 9:23 am

Re: Bug or new feature? Conditions within the GUI

Hello Mihai,

I've send you the AIP file.
The previous version was 8.8 I think. Whenever there was an Update available, I installed it as soon as possible.

Thanks,
Tobias
RedDrago
Posts: 33
Joined: Thu Jan 19, 2012 9:23 am

Re: Bug or new feature? Conditions within the GUI

Hello Mihai,

It looks like that this has something to do with the Checkboxes.

I found the following entries in the log:

Code: Select all

MSI (c) (9C:4C) [15:47:51:567]: PROPERTY CHANGE: Adding REGCB property. Its value is 'CheckBox'.
MSI (c) (9C:4C) [15:47:51:567]: PROPERTY CHANGE: Deleting DEMOCB property. Its current value is 'Checked'.
MSI (c) (9C:4C) [15:47:53:487]: PROPERTY CHANGE: Adding DEMOCB property. Its value is 'CheckBox'.
MSI (c) (9C:4C) [15:47:53:487]: PROPERTY CHANGE: Deleting REGCB property. Its current value is 'CheckBox'.
MSI (c) (9C:4C) [15:47:55:579]: PROPERTY CHANGE: Adding REGCB property. Its value is 'CheckBox'.
MSI (c) (9C:4C) [15:47:55:579]: PROPERTY CHANGE: Deleting DEMOCB property. Its current value is 'CheckBox'.
That "CheckBox" does not equal "Checked" should be clear. But after changing the value to "Checked", the Dialog kept the same behavior with the following log:

Code: Select all

MSI (c) (2C:9C) [16:20:14:628]: PROPERTY CHANGE: Adding REGCB property. Its value is 'Checked'.
MSI (c) (2C:9C) [16:20:14:628]: PROPERTY CHANGE: Deleting DEMOCB property. Its current value is 'Checked'.
MSI (c) (2C:9C) [16:20:16:670]: PROPERTY CHANGE: Adding DEMOCB property. Its value is 'Checked'.
MSI (c) (2C:9C) [16:20:16:670]: PROPERTY CHANGE: Deleting REGCB property. Its current value is 'Checked'.
The Controls are still enabled when they sholdn't and are disabled when they should be enabled.
On top of that, two other Textboxes are always editable, despite of the fact that they are "Read-only".

I was also able to reproduce that completly in a new project.

Thanks Tobias
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Bug or new feature? Conditions within the GUI

Hi Tobias,

We'll get back to you soon once we get a chance to investigate.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Bug or new feature? Conditions within the GUI

Hi Tobias,

I have looked into your project and here's what the behavior should be according to your settings:
  • Checkbox with DEMOCB attached public property has:
    Value: CheckBox
    Default Value: Checked
    > This means the DEMOCB property's initial value (without any user interaction on the checkbox) will be "Checked".
    > If the user interacts with the checkbox (checks, unchecks and then checks it again), the DEMOCB property's value will be set to "CheckBox".
  • Checkbox with REGCB attached public property has:
    Value: CheckBox
    Default Value: <empty string>
    > This means the REGCB property will not be set initially (without any user interaction on the checkbox).
    > If the user interacts with the checkbox (checks, unchecks and then checks it again), the REGCB property's value will be set to "CheckBox".
According to these settings, the above behavior is part of the control functionality. The details are described in the CheckBox user guide reference.

Also, I don't understand why you set the following published event sequence( two SetProperty events for each REGCB and DEMOCB ) on the Validate button.
a.jpg
a.jpg (22.6 KiB) Viewed 8923 times
After following this review, can you please underline what is the step by step exact test case of the misbehavior you reported? Also, please send us the sample project on which the test case applies.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
RedDrago
Posts: 33
Joined: Thu Jan 19, 2012 9:23 am

Re: Bug or new feature? Conditions within the GUI

Hello Mihai,

I've attached the sample project to this post. It does not require any dll I used in the other project, but it shows the very same behavior.
Also, I don't understand why you set the following published event sequence( two SetProperty events for each REGCB and DEMOCB ) on the Validate button.
I did this, to force an update on the controls. Otherwise, the Next button would not have been enabled. The Gui simply did not "detect" the property changes which were made by the custom action.

I've also tried to set the value directly, without any success...
SetDEMOCB.jpg
SetDEMOCB.jpg (60.15 KiB) Viewed 8920 times
The sample shows also the behavior, that the two fields, which should be readonly, are still editable.
I have looked into your project and here's what the behavior should be according to your settings:

Checkbox with DEMOCB attached public property has:
Value: CheckBox
Default Value: Checked
> This means the DEMOCB property's initial value (without any user interaction on the checkbox) will be "Checked".
> If the user interacts with the checkbox (checks, unchecks and then checks it again), the DEMOCB property's value will be set to "CheckBox".
Checkbox with REGCB attached public property has:
Value: CheckBox
Default Value: <empty string>
> This means the REGCB property will not be set initially (without any user interaction on the checkbox).
> If the user interacts with the checkbox (checks, unchecks and then checks it again), the REGCB property's value will be set to "CheckBox".
That's correct.
I've also tried to replaced the Value "CheckBox" with an empty string and "Checked". Both approaches didn't change the behavior.

Test steps:
  • Navigate to the License dialog.
    • Demo is Checked
    • Key1, Key2 and Validate should be disabled
  • Check "Registrierung"
    • Key1, Key2 and Validate should be enabled now
    • The Button "Next >" should be disabled
  • Fill out Key1 and Key2 (Optional in the sample project)
  • Push the "Validate" Button
    • Button "Next >" should be enabled now
If you need any further clarifications, please don't hesitate to ask.

Thanks,
Tobias
Attachments
CheckBoxSample.aip
(15.36 KiB) Downloaded 556 times
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Bug or new feature? Conditions within the GUI

Hi Tobias,

There's no bug. Windows Installer properties are string types.

The fix steps are:
- change each condition syntax as follows:
1.jpg
1.jpg (4.61 KiB) Viewed 8914 times
- delete DEMOCB SetProperty init event
- set DemoCheckBox's value and default value to Checked
- set RegCheckBox's value to Checked

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
RedDrago
Posts: 33
Joined: Thu Jan 19, 2012 9:23 am

Re: Bug or new feature? Conditions within the GUI

Hello Mihai,

thanks, its working now again.

But still I'am wondering why it worked before. I'am absolutely sure, that I did not use quotation marks in these conditions before.

But one problem still persists. The Textboxes SessionId and PCNR are still editable, despite of the fact that their property "Read-only" is set to "True":
AI-ReadOnly.jpg
AI-ReadOnly.jpg (96.84 KiB) Viewed 8912 times
Do you know what could cause this behavior?

Thanks,
Tobias
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Bug or new feature? Conditions within the GUI

Hi Tobias,

The extended attributes are only available when enabling Enhanced UI from the Themes page -> Settings tab.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”