nanogui: Thread: Two microwindows questions


[<<] [<] Page 1 of 1 [>] [>>]
Subject: Two microwindows questions
From: "Keith Williams" ####@####.####
Date: 15 Nov 2002 23:36:53 -0000
Message-Id: <JKEGKHCJDJGHAADLELJPAEJOCCAA.espian@insightbb.com>

Hi,

First, does anyone have a code example using the functions in kbd_ipaq.c?
It's obvious that what the open and close functions do.  Is the standard way
to find out if a key has been pressed and which one to setup a timer and
continuously poll IPAQ_Read(...)?

Second, I have spent a lot of time over the last couple of days pouring
through the mwin docs and Win32 docs.  I've seen things that allude to what
I want to do, but haven't figured out exactly how to do it.  I to create a
window that has a thin frame (OK so far...) but I want the interior of the
window to be transparent (not invisible).  The GDI API mentions that you can
stipulate the style of WS_EX_TRANSPARENT, but this has some other
ramifications with sibling windows.  The API docs says, "To achieve
transparency without these restrictions use the SetWindowRgn function."
I've looked at the docs for it and it seems to act in the opposite way that
I want.

I know that I am sooo close to have enough knowledge to do a first cut.

Thanks for any information that you can provide,

Keith

Subject: Re: [nanogui] Two microwindows questions
From: "Greg Haerr" ####@####.####
Date: 16 Nov 2002 18:19:29 -0000
Message-Id: <083f01c28d9b$5468b230$6401a8c0@gregnewport>

> First, does anyone have a code example using the functions in kbd_ipaq.c?
> It's obvious that what the open and close functions do.  Is the standard
way
> to find out if a key has been pressed and which one to setup a timer and
> continuously poll IPAQ_Read(...)?

No thats not standard, but sometimes required when the kernel
button interface is screwed up.  This is probably fixed in a later
version of the ipaq kernel.


 but I want the interior of the
> window to be transparent (not invisible).  The GDI API mentions that you
can
> stipulate the style of WS_EX_TRANSPARENT,

Win32 uses window procedures (winprocs) and messages
to make everything happen.  The window background
is drawn by DefaultWindowProc after the WM_ERASEBKGND
message is sent to your window procedure and passed along.
If you catch that message and return 1, the background won't
be drawn.  I think this method is used in some of the win32
sample code, src/demos/mwin/*.c

Regards,

Greg

[<<] [<] Page 1 of 1 [>] [>>]


Powered by ezmlm-browse 0.20.