Hi,

FiC introduces a problem with optiongroups after adaptation.
This carries on from this post here

I would like to suggest that awopt calls this.parent.click, similar to this code that I have put into XXXopt :

*** The class aw::awopt has code in the click event, which means that if an instance does not have code in its click event then the awopt code is run and this then
*** happens instead of triggering the click event of any parent optiongroup control (which would be the normal VFP behaviour).
*** So, call the click event of any optiongroup control after this.  4TFIC
=Dodefault()
If this.Parent.BaseClass = "Optiongroup"
	this.Parent.Click
endif

Paul

Do you mean that, in normal VFP behavior, when clicking on an Optionbutton without code in .Click() then parent Optiongroup.Click() fires?

Yes it must do, as we have optionbuttongroups that fire the code in the parent click without any code in the child buttons.

confirmed!

• Optiongroup.Click() fires when clicking a member optionbutton without code in .click().
• same for commandGroup and member commandButton

we've implemented a workaround for both Web and desktop modes.

will be released with 2.30.0-beta.3 later today

Great, I had the same problem with commandGroup