Search code examples
visual-foxprofoxpro

ADD OBJECT to subcontainer of object being defined

I'm writing a program to generate a VFP form class with lots (90+ each) of labels and radio buttons on it. That's the easy part. (and yes, I know that's a lot of radio buttons, but that's what the users want).

We have several VCXs in our application which do something similar, but not with anywhere near as many individual controls. So, rather than spend a huge fraction of my life dragging and dropping fields around, and realizing that I happen to have a handy list of all the fields, their options and default values, I used the 'View Class Code' option from the Class Browser to get a sample of what the code looks like as a base. Then I wrote code to generate a PRG with all the pieces I need.

My actual problem is that the code output by 'View Class Code' seems to include invalid syntax:

DEFINE CLASS form40 AS frmae
  Height = 427
  Width = 710
  ScrollBars = 2
  DoCreate = .T.
  Visible = .T.
  Name = "form40"

  ADD OBJECT form40.cntouter.cntform40 AS cntctrls WITH ;
    Top = 175, ;
    Left = 2, ;
    Visible = .T., ;
    Name = "Cntform40"

ENDDEFINE

The class frmae is a class (from a VCX) which includes a container called 'cntouter'. Class cntctrls is the container that contains all the labels/radio buttons.

The problem is that apparently you can't, in the DEFINE CLASS command, ADD OBJECT to a member. The dotted syntax causes a syntax error. Yet, this technique is used in the 'View Class Code' output.

I suspect I could get around this by generating an Init method which calls ADDOBJECT() to add my control container to cntouter, but I'd rather have it in the class definition.

Solution

  • The "View Class Code" option doesn't produce runnable code; it never has.

    My suggestion for doing what you need is to create an option button class with the appearance that you want. Then, use your existing list to populate a cursor and write code that spins through that and adds option buttons to a container class.

    The key thing you need to know here is that you can run code in the IDE that affects a form or class that's open in the Form Designer or Class Designer. That's what Builders do. So rather than generate a code-based class, use code to create a visual class.