On Thu, Feb 21, 2002 at 02:16:02PM -0800, Danny Epstein wrote:
> It sounds like we should add a FrmGlueHideObject function that has
> permission to access the usable bit on old versions of Palm OS.
Yes, and while you're at it, could also add code so that it would handle
Tables and Lists correctly
> To continue checking your other code properly, you really do need to put
> your "glue" code in a separate .c file.
As usual, thanks for setting the record straight! :)
-
Danny
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/
"Danny Epstein" <[EMAIL PROTECTED]> wrote in message
news:77542@palm-dev-forum...
> > I have code in the app to hide the graphic and button if they aren't
> > supposed to appear, and reposition/resize all following UI objects. If
> > there is a table, the code also removes a row in if the graphi
On Thu, Feb 21, 2002 at 02:16:02PM -0800, Danny Epstein wrote:
> It sounds like we should add a FrmGlueHideObject function that has
> permission to access the usable bit on old versions of Palm OS. For now, you
> can use your own glue code instead. You should be okay as far as
> compatibility, but
> I have code in the app to hide the graphic and button if they aren't
> supposed to appear, and reposition/resize all following UI objects. If
> there is a table, the code also removes a row in if the graphic and button
> _are_ supposed to appear.
Interesting problem. You can probably get away
"Danny Epstein" <[EMAIL PROTECTED]> wrote in message
news:77510@palm-dev-forum...
>
>>[...]
> > I guess this means I need to do a TblSetRowUsable (usable = false) then,
> > so I'll give it a try. Will this also cause TblGetNumberOfRows to
return a
> > value that omits unusable rows?
> No. The n
> This article basically suggests doing what I'm already doing (turning off
> the usable bit), but which causes a compilation error with the new SDK - I
> want to get rid of the error without setting the bit.
It sounds like we should add a FrmGlueHideObject function that has
permission to access
Mark: Check out a msg I posted on this forum on 02/20/2002 @ 1:49pm,
subject = SDK 4.0 Upd1
I ran into a similar situation with "unusable", and documented how I intend
to get around it there.
Regards,
Terry
--
For information on using the Palm Developer Forums, or to unsubscribe, please se
> http://www.escribe.com/computing/pcpqa/m48694.html
This article basically suggests doing what I'm already doing (turning off
the usable bit), but which causes a compilation error with the new SDK - I
want to get rid of the error without setting the bit.
> http://www.escribe.com/computing/pcpqa
> One is hiding a form bitmap on pre-OS 3.3 systems. FrmHideObject does not
> seem to work on those systems, and I see no alternative to it.
See Dave Johnson's post:
http://www.escribe.com/computing/pcpqa/m48694.html
Peter's post may also be relevant:
http://www.escribe.com/computing/pcpqa/m224
I've been working on getting rid of all the system internal structure
references in my app, and I'm down to two for which I see no alternative.
One is hiding a form bitmap on pre-OS 3.3 systems. FrmHideObject does not
seem to work on those systems, and I see no alternative to it. Is
FrmHideObje
11 matches
Mail list logo
