It appears that Constructor has worked this way for awhile.  Is it supposed
to?  You can generate the behavior by creating a group in any form.  I'll
still send you a file off line as an example.

When Constructor generates the header file, it defines the object id numbers
by concatenating the following information:  FormName (under "Forms" in
Constructor), ObjectIdentifier (from the object's layout properties), and
ObjectType (i.e., button, field, etc.).  Thus, if my form name is "Form1",
and I have a pushbutton with the object identifier of "Form2", Constructor
will generate an id for this pushbutton of "Form1Form2PushButton", which is
fine.

However, when Constructor generates group ID defines, it departs from the
above scheme and concatenates the form title to the string "FormGroupID#",
where # (a number) may, or may not, be included.  It seems to process out
invalid characters well enough, but the compiler chokes if you use an
entirely numeric title.  Why are these defines generated differently?

Regards,

Steve

-----Original Message-----
From: Heather Tufts [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 11, 2000 4:30 PM
To: Palm Developer Forum
Subject: RE: Constructor for Palm OS Bug


Dan,

Could you send me your resource file so I can take a look at it?  I'll be
glad to report it if I can reproduce it.

-hkmlt

-----Original Message-----
From: OBrien, Dan [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 10, 2000 8:00 AM
To: Palm Developer Forum
Cc: McMicken, Steven
Subject: Constructor for Palm OS Bug


I believe I've discovered another minor bug in release 1.5b7 of Constructor
for Palm OS. 

The 'tFRM' resource section of resultant header (.h)  file shown below,
which was generated using the 1.5b7 version of Constructor.
Notice the prefix generated for the two Group ID's consists of the form
title "Test SDK 3.5 Rsrcs" (with spaces and periods removed), followed by
"Form".  They should have been generated using just the form name, "Main".  

In this case they caused no problem, the CW compiler [preprocessor]
processes the header file nicely.  
But, in another job I was working on, the form name was "FTest" and the form
title was "123456789012345", as I was changing the form title at runtime,
and wanted up 15 chars reserved for the form title in the FTestForm
resource.  When the compiler [preprocessor] threw an error, (as it should),
I discovered this Constructor problem.

#define 123456789012345FormGroupID      1       <=== throws error as
definitions must start with letter.

I worked around this situation by either post editing the resultant
constructor header file, and later simply changing the form title to
"A23456789012345"

Dan O'Brien
[EMAIL PROTECTED]
Detroit Engineering Center
2870 Technology Dr.
Rochester Hills, MI 48309
248.293.1324  FAX: 248.293.1309


//      Header generated by Constructor for Palm OS� 1.5
//
//      Generated at 2:00:29 PM on Thursday, July 06, 2000
//
//      Generated for file: C:\Projects\Palm\Test35Sdk\Src\Test35Sdk.rsrc
//
//      THIS IS AN AUTOMATICALLY GENERATED HEADER FILE FROM CONSTRUCTOR FOR
PALM OS�;
//      - DO NOT EDIT - CHANGES MADE TO THIS FILE WILL BE LOST
//
//      Palm App Name:          "Test Sdk"
//
//      Palm App Version:               "0.1"



//      Resource: tFRM 1000
#define MainForm                        1000 
#define MainTestCheckbox                1002
#define MainRomSnField          1013
#define MainUnnamed1003Label            1003
#define MainUnnamed1009Label            1009
#define MainUnnamed1010Label            1010
#define MainUnnamed1012Label            1012
#define MainUnnamed1015Label            1015
#define MainTestAPushButton             1004
#define MainTestBPushButton             1005
#define MainTestCPushButton             1006
#define MainTestDPushButton             1007
#define MainRepeatRepeating             1008
#define MainHorizontalScrollBar         1011
#define MainVerticalScrollBar           1014
#define MainGbGraphicButton             1001
#define TestSDK35RsrcsFormGroupID        0
#define TestSDK35RsrcsFormGroupID2      100




-- 
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/

-- 
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/

--
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/

Reply via email to