Someone from Palm or MW posted here instructions how to
create .r source file from .rsrc file.
In short, here is what you must do (if you are using CW R6, I
don't know if it works with R5):
- open your project settings, locate and highlight the RSRC file type
in the "File Mappings" panel.
- change the compiler option to "Rez" and click on the "Change" button
- in the "Rez" panel add "UIResDefs.r" to the "Prefix File" field. That file
must be somewhere in your include path.
To get the source code from the .rsrc file, right-click on that .rsrc file
in the project window and choose "Disassemble" option.
Regards
Bozidar
> -----Original Message-----
> From: Richard Hartman [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 02, 1999 6:48 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Tabbed forms - A place for .r files?
>
>
>
>
> > -----Original Message-----
> > From: Brian Hall [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, December 02, 1999 8:40 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Tabbed forms - A place for .r files?
> >
> >
> > >This is actually what we do - our tabs and and the stuff
> > they show and
> > >hide are all on one form. It isn't that bad. In constructor you can
> > >select the widget you need by using the menu option "Show object
> > >heirarchy" under the Layout menu. You do have to be careful
> > to make some
> > >changes numerically rather than visually to be certain that
> > everything
> > >lines up as you expect. You can also hide objects to get
> > them out of the
> > >way temporarily. It is quite possible to have a form that
> > contains lots
> > >of overlapping widgets without it becoming unmanageable.
> >
> > It isn't visual, but working with .r files is one way to
> > handle complex
> > forms such as that. You can even define constants (for example, base
> > horizontal and vertical offsets).
> >
>
> This sort of thing is one reason that I wish that
> Constructor saved the visually-edited resources in
> source form instead of the proprietary binary blob.
>
> I think they mentioned that that might be coming
> in the future ... but they didn't mention a particular
> target version.
>
>
>
>
> --
> -Richard M. Hartman
> [EMAIL PROTECTED]
>
> 186,000 mi./sec ... not just a good idea, it's the LAW!
>
>
