Caveats of the 3.0 SDK are not necessarily caveats of the 3.0 OS. It is
quite possible that newer versions of the SDK address these limitations on
the SDK side, and are no longer relevant. If it once was in the
documentation, but isn't now, it means it was deliberately removed, and
I've yet to hear of Palm deliberately hiding limitations. My gut feeling
is that if the new documentation doesn't list the limitations, don't worry
about it.
-Thomee-
In article <57129@palm-dev-forum>, [EMAIL PROTECTED] says...
>
> :-D Yes I know that, that's a legal :-D method. I didn't tell you this at
> the first place because something very interesting :-D is written in 3.0 SDK
> docs, this thing is absent in 3.5 SDK docs :-D. Here are the lines that I
> found interesting :-D about FrmSetObjectPosition
>
> "Comment: Doesn't update the display. Presently, only label objects are
> affected.
> Caveat: This function currently doesn't work when used on a bitmap."
> .....Straight from 3.0 SDK docs
>
> Do you get my point what will happen if you try to run your applications on
> OS 3.0 :-D . Keep in mind you also want to change the position of
> PopupTriggers etc. also ;-D
>
> Regards,
> Khurram+
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
