Quantcast
Channel: West Wind Message Board Messages
Viewing all articles
Browse latest Browse all 10393

Re: Pageframe/OptionGroups

$
0
0
Re: Pageframe/OptionGroups
FoxInCloud
Re: Pageframe/OptionGroups
04/18/2012
11:33:19 AM
3HD0ORQRM Show this entire thread in new window
Gratar Image based on email address
From:
Patrick
To:
Attachments:
None

It does not look to be the same naming problem from what I can tell.

I can work around both of these. I will add my object to the page at design time. I can call this.parent.click() in the option buttons to get the optiongroup click event to fire.


> Page3.Init()
Could be a naming issue as we recently saw

> OptionGroup.Click() does not fire after adapting
Can't imagine why ...

> LPARAMETERS nButton, nShift, nXcoord, nYcoord
VFP visual editor adds this line automatically when you edit a *.?cx method.
Inherited from aw.vcx!aw???
Provides nButton, nShift, nXcoord, nYcoord support in .click() after calling DoDefault(@nButton, @nShift, @nXcoord, @nYcoord)
(see inherited code for details)
A sweet FoxInCloud goodie ...


After adapting an app I notice two problems with my app.

In a pageframe I have the following code in the Page3 Init Event, it does not appear to run after adapting:
This.addobject("policy1", "Agent_apps_x")
THIS.POLICY1.VISIBLE = .T.

In a optiongroup I have code in the OptionGroup Click event that does not fire after adapting.

In the the Option object I had no code in the click event, now it has:
LPARAMETERS nButton, nShift, nXcoord, nYcoord



Viewing all articles
Browse latest Browse all 10393

Trending Articles