On the garnet simulator, nativeFormat won't work (it returns a null pointer),
but on my verizon simulator, it works fine.
Is there a way to get it to work?
If not, how can I test to see if I am on the simulator so that it will do
screenFormat on the simulator and nativeFormat on any real
I'm migrating a CW project from one computer to
another, and resuming work on this project after
several months lull. When I build it on the new
machine, I get the error in the subject when trying to
use the WinCreateOffscreenWindow function. The
compiler will recognize screenFormat
Brian Preston wrote:
I commented it out, just to see if I could get my app
running on the emulator (which it was doing fine on
the old machine). It ran fine until I tried to call
WinGetBounds(), where it said that routine doesn't
exist in this version of the PalmOS.
That function doesn't exist
At 08:55 PM 4/5/2005, you wrote:
I'm migrating a CW project from one computer to
another, and resuming work on this project after
several months lull. When I build it on the new
machine, I get the error in the subject when trying to
use the WinCreateOffscreenWindow function. The
compiler
In OS3.5,I can use WinCreateOffscreenWindow:
{
WinHandle theWindowHandle;
theWindowHandle = WinCreateOffscreenWindow(
theBoundsPtr-extent.x,theBoundsPtr-extent.y,screenFormat,theError );
}
I can copy theWindowHandle-bitmapP to BitmapPtr variable.
But In OS5,I use the same code ,I find
I have noticed that on the PalmOS Simulator, if I create an off screen
buffer using nativeFormat, then the resulting Bitmap is ALWAYS 16-bit
color (LE), regardless of what color depth mode the device is in. (In
my case it is in 8-bit mode.) Is this the intended way nativeFormat is
supposed
Solved the issue:
The problem was that you have to call
WinSetCoordinateSystem(kCoordinatesNative);
before every single graphics call, 'cause it's always being set back
to low resolution.
In this case, I forgot to call it again right before creating my
offscreen window. So when I told it to
Due to some of the font issues with the 4.x Sony Hi-Res, in order to use a
custom font within a popup dialog within a field, one must draw it first in
an offscreen window at the correct resolution, then when it actually gets
redered it'll appear correctly.
Has anyone does any work in regards to
Hi,
Whenever I run Gremlins in emulator, I get 2 memory leak corresponding to
WinCreateOffscreenWindow thogh i have not used this function in program. I
have used bitmaps in my application. Does it relates to that?
Will this problem come up in real device also?
Please help me out.
Regrads
Is there a way for WinCreateOffscreenWindow to create a window of a bit depth
that is not the current. Right now I can create a 16-bit offscreen window by
putting the device into 16-bit mode creating it and putting it back into the
native 8-bit mode. However, this causes some unpleasing flash
Hi!
Is there a way for WinCreateOffscreenWindow to create a window of a bit depth
that is not the current. Right now I can create a 16-bit offscreen window by
putting the device into 16-bit mode creating it and putting it back into the
native 8-bit mode. However, this causes some
Tilo,
--- Tilo Christ [EMAIL PROTECTED] wrote:
Hi!
Is there a way for WinCreateOffscreenWindow to create a window of a bit
depth
that is not the current. Right now I can create a 16-bit offscreen window
by
putting the device into 16-bit mode creating it and putting it back
I just downloaded PalmOS Simulator DR8 and noticed
that the WinCreateOffscreenWindow creates a window
that is too small by one pixel in both the x and y
directions.
FYI.
Mike McCollister
__
Do You Yahoo!?
Yahoo! Sports - live college hoops
=
WinCreateOffscreenWindow(rect.extent.x,rect.extent.y,screenFormat,BadaBOOM)
;
BadaBOOM |= (Boolean)(gHelp-helpWindow == NULL);
Allows us to create a good sized scrollable window for devices with depths
less than 8bpp. Obviously 8bpp color devices cause an allocation 64K
which is wasteful
},{145,489}};
gHelp-helpWindow =
WinCreateOffscreenWindow(rect.extent.x,rect.extent.y,screenFormat,BadaBOOM)
;
BadaBOOM |= (Boolean)(gHelp-helpWindow == NULL);
Allows us to create a good sized scrollable window for devices with depths
less than 8bpp. Obviously 8bpp color devices cause
On Thu, 28 Feb 2002, Aaron Ardiri wrote:
Questions: If the displayed text graphics only requires 4 to 8 colors in
total do we have to allocate for 8bpp? Does creating a custom palette help
to minimize heap requirements?
yes, it would. :)
bah.. before you nag me about how.. look at
Hello,
Using Handspring Visors w/ PalmOS3.1. I've created off screen windows to
speed up my displays using WinCreateOffscreenWindow. But I am finding the
Field updates still occur on the display window. How can I re-locate the
display pointer to my off screen window?
Thanks for your help
Please,
If you have some sample code using WinCreateOffscreenWindow and how to put
some controls inside, and update the Form with his content, send to me,
PLEASE
%(
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support
So it sounds like WinCreateOffscreenWindow has done what you asked,
successfully. (You could always look at the struct in the debugger to
verify.)
...
In any case, it can't handle allocating 64k, even if there wasn't an
overflow problem, so don't ask it to :-)
I'm not really controlling
OK, so either I'm completely losing my mind of something is screwy here.
On devices 3.5, I'm making a WinCreateOffscreenWindow call. As far as
I can figure, WinCreateOffscreenWindow shouldn't create the window and
should return an error if the dimensions I pass are too large -
requiring a memory
doesn't support allocating something 64k, but since the offscreen window
is always 1-bit, it'd have to be a pretty large window to go past that.
However this isn't correct. As documented in WinCreateOffscreenWindow,
and I can attest to the documentation being correct
From: Steve Patt
The usually reliable David F. wrote:
And no, it
doesn't support allocating something 64k, but since the offscreen window
is always 1-bit, it'd have to be a pretty large window to go past that.
However this isn't correct.
I, for one, am shocked! And to think that I
The usually reliable David F. wrote:
And no, it
doesn't support allocating something 64k, but since the offscreen window
is always 1-bit, it'd have to be a pretty large window to go past that.
However this isn't correct.
I, for one, am shocked! And to think that I referred to
The usually reliable David F. wrote:
And no, it
doesn't support allocating something 64k, but since the offscreen window
is always 1-bit, it'd have to be a pretty large window to go past that.
However this isn't correct. As documented in WinCreateOffscreenWindow,
and I can attest
Hi,
When I create an offscreen window using WinCreateOffscreenWindow, is the
handle created locked? I am assuming that it is since I get a bus error when
I try to lock the handle.
Now the real question is how do I get the pointer for the offscreen data?
For example, the call below I get
"McCollister, Mike" [EMAIL PROTECTED] writes:
Now the real question is how do I get the pointer for the offscreen data?
For example, the call below I get a handle called hOffscreen.
Do you mean you want to access the bitmap? If so, WinGetBitmap() in
palmos 3.5 and higher. In earlier palmos
When I create an offscreen window using WinCreateOffscreenWindow, is the
handle created locked? I am assuming that it is since I get a bus error when
I try to lock the handle.
Now the real question is how do I get the pointer for the offscreen data?
For example, the call below I get
, January 18, 2001 3:31 PM
To: Palm Developer Forum
Subject: Re: WinCreateOffscreenWindow question
When I create an offscreen window using WinCreateOffscreenWindow, is the
handle created locked? I am assuming that it is since I get a bus error
when
I try to lock the handle.
Now
Once again you come through. Wonderful help.
should i invoice you? :)
Now do you happen to know if there is a function or macro in the Palm OS
headers that does this?
UInt16 RGB16;
RGB16 = ((RGBColor.r 0xF8) 8) + ((RGBColor.g 0xFC) 3) +
((RGBColor.b 0xF8) 3);
good question
Hello all,
I just curious if anyone knows of any special memory allocation or
fragmentation issues associated with WinCreateOffscreenWindow. I have an
app where I create (if necessary) an offscreen window that's used
temporarily and then deleted. Over the course of the app (or a million
search palm-dev-forum wincreateoffscreenwindow
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
D]
cc:(Keith Rollin/US/PALM)
Subject: search palm-dev-forum wincreateoffscreenwindow
search palm-dev-forum wincreateoffscreenwindow
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/tech/support/forums/
--
For inform
David,
Thanks, that should work!!
-Prashant
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Fedor
Sent: Tuesday, August 15, 2000 10:59 AM
To: Palm Developer Forum
Subject: Re: WinCreateOffscreenWindow() with desired depth - without
flicker?
How
WinScreenMode(winScreenModeSet, NULL, NULL, depth, NULL);
WinCreateOffscreenWindow(width, height, screenFormat, error);
This works, but I get an annoying flash on the screen. Is there any way to
set the depth of the offscreen window to something that is different freom
the depth of the main
How can I create an offscreen window of a desired UInt32 depth (say 1bpp),
where the depth is different from that of the display screen (say 2bpp).
I can't think of a better way, prior to Palm OS 3.5. But as of 3.5, you
can use BmpCreate and then WinCreateBitmapWindow to use any depth (and/or
Thank you. The answer helped me to find a bug.
Ewaryst Izewski
- Original Message -
From: [EMAIL PROTECTED]
To: Palm Developer Forum [EMAIL PROTECTED]
Sent: Saturday, May 13, 2000 12:26 AM
Subject: Re: emulator and WinCreateOffscreenWindow
Since many of the built-in apps and sample
OK. I'll ask again. Maybe this time somebody will share his (or her) wisdom
with me.
Is it normal that when I call WinCreateOfscreenWindow or WinSaveBits the
emulator displays the message: "'Your program' has just tried to write to
the ROM"?
If it is, can I stop the emulator annoying me with such
ase respond to "Palm Developer Forum" [EMAIL PROTECTED]
Sent by: "Ewaryst Izewski" [EMAIL PROTECTED]
To: "Palm Developer Forum" [EMAIL PROTECTED]
cc:(Keith Rollin/HQ/3Com)
Subject: emulator and WinCreateOffscreenWindow
OK. I'll ask again. Maybe this ti
38 matches
Mail list logo
