• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 571
  • Last Modified:

Borland OWL Resource Dialog Button

Is that possible somehow to capture and handle
the "BN_PUSHED" (equ. "BN_HILITE") OWL event from the
ordinary button of the Dialog resource work shop window
for application written for Win95 Win32 Target platform?
I have been using Borland C++,V.5.01 compiler with OWL library on Pentium 200 machine. I could trail only
BN_CLICKED, BN_DBLCLICKED, BN_SETFOCUS, BN_KILLFOCUS
notification events.

0
leonov
Asked:
leonov
  • 2
1 Solution
 
gaohongCommented:
Yes, you could still catch BN_HILITE with
  EV_CHILD_NOTIFY(id, BN_HILITE, method)
in OWL, however, BN_PUSHED is only for Win95. Even BN_HILITE
is supplied only for compatibility.

good luck



0
 
leonovAuthor Commented:
Gaohong's answer gives the same information as
OWL Help does. But, my question was:
Why I can not catch BN_HILITE as well as
BN_PUSHED, even working under Windows95?

ID_CHILD_NOTIFY(ID_BUTTON,BN_PUSHED,HandleMethod);
does not work, and
ID_CHILD_NOTIFY(ID_BUTTON,BN_HILITE,HandleMethod);
does not work either.

Do you think, there is something wrong with
OWL library?  How to check this?
Is it possible to fix this trouble
by recompiling the library?

0
 
gaohongCommented:
It is my understanding that you only needs BN_PUSHED or BN_HILITE
in ownerdraw button, and it is supplied for only backward compatibility.

For 32bit application on win95 or after win3.1, your ownerdraw
button should rely on DRAWITEMSTRUCT.

If we are talking about non-ownerdraw button, forget about
try to get this messages (BN_PUSHED), windows has down all the things for you.

0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now