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

Re: starting an app

$
0
0
Re: starting an app
FoxInCloud
Re: starting an app
Apr. 17, 2013
10:05 am
3RI0LMY72Show this entire thread in new window
Gratar Image based on email address
From:Thierry Nivelet (FoxInCloud)
To:Rafael Copquin
Rafael,

a) did you choose 'lef' as application code ?
b) can you post a screeshot? We used to know this issue and have solved it recently
c) please post the contents of the form.scx.properties field:

use your.scxlocatefor objname = yourCommandGroup_cliptext = properties

thanks


I have spent a long time trying to adapt one of my apps.

I have a class library that contains a base form with some common methods that all my forms use. I made a subclass of the awfrm class and then added the above methods. This was the only way that I could open my forms after the first adaptation made by the FAA.
However, in some of the forms of my app I use commandgroups. To my surprise the following happened:

a) the commandgroups were transformed by the FAA using the class lefcmd (the subclassed library was named lef.vcx by the FAA)
b) the button sizes, positions, quantity and captions were gone, being replaced by raw commandgroups. I mean, commandgroups with a default quantity of buttons, no code in the buttons, no captions and without respecting the sizes, positions and display - vertical instead of horizontal, for instance)
c) the code in the click event of my buttons was also gone

How can this behaviour be avoided?


-- thn (FoxInCloud)


Viewing all articles
Browse latest Browse all 10393

Trending Articles