> >i would not rule out the OS ignoring the frame attribute when it is a
> >push button :) that should be pretty easy to test :)
>
> I just checked the Palm OS source code. Indeed, for both selector
triggers
> and push buttons, the OS will always force their frame style to
rectangleFrame.
so, technically, we could remove the ifFrame option from the push button
and selector trigger code in pilrc? :) its kind of bad on palm's behalf
to do that actually..
case rwPBN: /* pushbutton */
ParseItm(&itm,
ifText | ifId | ifRc | ifUsable | ifEnabled | ifFont |
- ifAnchor | ifGroup | ifSmallMargin | ifFrame,
+ ifAnchor | ifGroup | ifSmallMargin,
if2Graphical | if2BitmapID | if2SelectedBitmapID, if3Null,
if4Null);
goto Control;
and..
case rwSLT: /* selectortrigger */
ParseItm(&itm,
ifText | ifId | ifRc | ifUsable | ifEnabled | ifFont |
- ifAnchor | ifSmallMargin | ifFrame,
+ ifAnchor | ifSmallMargin,
if2Graphical | if2BitmapID | if2SelectedBitmapID, if3Null,
if4Null);
goto Control;
inside pilrc.c - due to the nature of ParseItem, (need to understand this
code a bit better) i dont know if it is possible to barf if the frame
options
are actually used - maybe it does with these modifications.
if we cannot control the frame, surely neither should pilrc.
> I suggest you simulate push buttons using normal graphical buttons.
You'll
> just have to manage the selected/non-selected state yourself.
yeah, the selected/non-selected state issue is nasty.
---
Aaron Ardiri [EMAIL PROTECTED]
CEO - CTO +46 70 656 1143
Mobile Wizardry http://www.mobilewizardry.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
