Jump to content

Introduction to PM Programming - Feb 1995: Difference between revisions

From EDM2
Prokushev (talk | contribs)
400 edits
No edit summary
 
Ak120 (talk | contribs)
35,819 edits
mNo edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Written by [[Larry Salomon Jr.]]
''Written by [[Larry Salomon Jr.]]''


<h2>Introduction</h2>
==Introduction==
The purpose of this column is to provide the readers out there who are not familiar with PM application development the information necessary to satisfy their curiosity, educate themselves, and give them an advantage over the documentation supplied by IBM. Of course, much of this stuff could probably be found in one of the many books out there, but the problem
with books in general is that they don't answer the questions you have after you read the book the first time through.


<p>The purpose of this column is to provide the readers out there who are not
I will gladly entertain feedback from the readers about what was "glossed over" or what was detailed well, what tangential topics need to be covered and what superfluous crap should have been removed. This feedback is essential in guaranteeing that you get what you pay for. <grin>
familiar with PM application development the information necessary to
satisfy their curiosity, educate themselves, and give them an advantage
over the documentation supplied by IBM. Of course, much of this stuff
could probably be found in one of the many books out there, but the problem
with books in general is that they don't answer the questions you have
after you read the book the first time through.


<p>I will gladly entertain feedback from the readers about what was &quot;glossed
It should be said that you must not depend solely on this column to teach you how to develop PM applications; instead, this should be viewed as a supplement to your other information storehouses (books, the network conferences, etc.). Because this column must take a general approach, there will be some topics that you would like to see discussed that really do not belong here. Specific questions can be directed to me via email and I will do my best to answer them in a timely fashion.
over&quot; or what was detailed well, what tangential topics need to be covered
and what superfluous crap should have been removed.  This feedback is
essential in guaranteeing that you get what you pay for. &lt;grin&gt;


<p>It should be said that you must not depend solely on this column to teach
==Last Month==
you how to develop PM applications; instead, this should be viewed as a
Last month, we finished the WC_LISTBOX class and I asked for feedback. I did receive some, for which I am very grateful, but the majority of them were requests for advanced topics, like the container and the notebook controls. We will eventually cover these window classes, but it is
supplement to your other information storehouses (books, the network
essential that we look at the rudimentary ones first, so that you can better appreciate what these advanced classes do for you.
conferences, etc.).  Because this column must take a general approach,
there will be some topics that you would like to see discussed that really
do not belong here.  Specific questions can be directed to me via email and
I will do my best to answer them in a timely fashion.


<h2>Last Month</h2>
This month, we will look at the WC_TITLEBAR and WC_STATIC window classes.
Since both of these classes are not too involving, covering them both should not be a problem.


<p>Last month, we finished the WC_LISTBOX class and I asked for feedback. I
==The Titlebar==
did receive some, for which I am very grateful, but the majority of them
The titlebar class (WC_TITLEBAR) is usually not created directly, but is created for you by the frame window through the WinCreateStdWindow() call.
were requests for advanced topics, like the container and the notebook
It has two primary functions: 1) to display the text of the standard window to which it belongs, and 2) to act as a shortcut to two primary windowing functions, move and maximize/restore.
controls.  We will eventually cover these window classes, but it is
essential that we look at the rudimentary ones first, so that you can
better appreciate what these advanced classes do for you.


<p>This month, we will look at the WC_TITLEBAR and WC_STATIC window classes.
The titlebar does accept two messages: TBM_SETHILITE and TBM_QUERYHILITE.
Since both of these classes are not too involving, covering them both
should not be a problem.
 
<h2>The Titlebar</h2>
 
<p>The titlebar class (WC_TITLEBAR) is usually not created directly, but is
created for you by the frame window through the WinCreateStdWindow() call.
It has two primary functions:  1) to display the text of the standard
window to which it belongs, and 2) to act as a shortcut to two primary
windowing functions, move and maximize/restore.
 
<p>The titlebar does accept two messages: TBM_SETHILITE and TBM_QUERYHILITE.
 
<pre><small>
TBM_SETHILITE
</small></pre>


===TBM_SETHILITE===
This message sets the highlight state of the control.
This message sets the highlight state of the control.


<h2>Parameters</h2>
====Parameters====
 
SHORT1FROMMP(mpParm1) - the new highlight state of the control.
<p>SHORT1FROMMP(mpParm1) - the new highlight state of the control.
{|class="wikitable"
 
|TRUE||Draw the control in highlighted state.
<table>
|-
<tr>
|FALSE||Draw the control in normal state.
<td>TRUE</td>
|}
<td>Draw the control in highlighted state.</td>
 
</tr>
<tr>
<td>FALSE</td>
<td>Draw the control in normal state.</td>
</tr>
</table>
 
<h2>Returns</h2>
 
<p>SHORT1FROMMR() - success indicator.
 
<table>
<tr>
<td>TRUE</td>


<td>Successful completion.</td>
====Returns====
</tr>
SHORT1FROMMR() - success indicator.
<tr>
{|class="wikitable"
<td>FALSE</td>
|TRUE||Successful completion.
<td>Error occurred.</td>
|-
</tr>
|FALSE||Error occurred.
</table>
|}
 
<pre><small>
TBM_QUERYHILITE
</small></pre>


===TBM_QUERYHILITE===
This message returns the highlight state of the control.
This message returns the highlight state of the control.


<h2>Returns</h2>
====Returns====
 
SHORT1FROMMR() - highlight state of the control.
<p>SHORT1FROMMR() - highlight state of the control.
{|class="wikitable"
 
|TRUE||The control is drawn in highlighted state.
<table>
|-
<tr>
|FALSE||The control is drawn in normal state.
<td>TRUE</td>
|}
<td>The control is drawn in highlighted state.</td>
</tr>
<tr>
<td>FALSE</td>
<td>The control is drawn in normal state.</td>
</tr>
</table>
 
Highlight state is used to indicate that the window has the focus.
Highlight state is used to indicate that the window has the focus.
Normally, you do not need to use these messages, since the frame control
Normally, you do not need to use these messages, since the frame control will use them on your behalf.
will use them on your behalf.
 
<p>To set or query the text displayed in the titlebar, use WinSetWindowText()
and WinQueryWindowText().  Again, the frame makes this easy by setting or
querying it for you whenever you set or query the frame window's text.
 
<p>For reference, it should be noted that, whenever the user attempts to move
or maximize/restore the window using the titlebar, the titlebar sends its
owner (the frame usually) a WM_QUERYTRACKINFO message.  The owner can fill
in this structure according to its needs to restrict movement or resizing
as necessary.  We will not discuss this further.
 
<p>That's all there is to the WC_TITLEBAR class.
 
<h2>The Static</h2>
 
<p>The static control is just that:  static.  It never changes.  The point of
the static control is to display text, rectangles, icons, bitmaps, etc.  A
table of the static styles is shown below:
 
<table>
<tr>
<th>Style</th>
<th>Results in</th>
</tr>
<tr>
<td>SS_AUTOSIZE</td>
 
<td>Automatically size to contain the text, icon, or bitmap</td>
</tr>
<tr>
<td>SS_BITMAP</td>
<td>Bitmap</td>
</tr>
<tr>
<td>SS_BKGNDFRAME</td>
<td>Unfilled rectangle painted with the background color</td>
</tr>
<tr>
<td>SS_BKGNDRECT</td>
 
<td>Filled rectangle painted with the background color</td>
</tr>
<tr>
<td>SS_FGNDFRAME</td>
<td>Unfilled rectangle painted with the foreground color</td>
</tr>
<tr>
<td>SS_FGNDRECT</td>
<td>Filled rectangle painted with the foreground color<td>
</tr>
<tr>
<td>SS_GROUPBOX</td>
 
<td>Groupbox</td>
</tr>
<tr>
<td>SS_HALFTONERECT</td>
<td>Filled rectangle painted with a halftoned color</td>
</tr>
<tr>
<td>SS_HALFTONEFRAME</td>
<td>Unfilled rectangle painted with a halftoned color</td>
</tr>
<tr>
<td>SS_ICON</td>
 
<td>Icon</td>
</tr>
<tr>
<td>SS_SYSICON</td>
<td>System icon</td>
</tr>
<tr>
<td>SS_TEXT</td>
<td>Text</td>
</tr>
</table>
 
All but the first style are mutually exclusive.  The first style can only
be used with SS_TEXT, SS_BITMAP, SS_ICON, or SS_SYSICON.  Additionally, if
SS_TEXT is used, you may also or one of the constants from each of the
following groups to align the text in a specific manner.
 
<p>Horizontal alignment
 
<table>
<tr>
<th>Constant</th>
<th>Alignment</th>
</tr>
<tr>
<td>DT_LEFT</td>
<td>Left aligned</td>
</tr>
<tr>
<td>DT_CENTER</td>
 
<td>Center aligned</td>
</tr>
<tr>
<td>DT_RIGHT</td>
<td>Right aligned</td>
</tr>
</table>


<p>Vertical alignment
To set or query the text displayed in the titlebar, use WinSetWindowText() and WinQueryWindowText(). Again, the frame makes this easy by setting or querying it for you whenever you set or query the frame window's text.


<table>
For reference, it should be noted that, whenever the user attempts to move or maximize/restore the window using the titlebar, the titlebar sends its owner (the frame usually) a WM_QUERYTRACKINFO message. The owner can fill in this structure according to its needs to restrict movement or resizing as necessary. We will not discuss this further.
<tr>
<th>Constant</th>
<th>Alignment</th>


</tr>
That's all there is to the WC_TITLEBAR class.
<tr>
<td>DT_TOP</td>
<td>Top aligned</td>
</tr>
<tr>
<td>DT_VCENTER</td>
<td>Center aligned</td>
</tr>
<tr>
<td>DT_BOTTOM</td>
<td>Bottom aligned</td>


</tr>
==The Static==
</table>
The static control is just that: static. It never changes. The point of the static control is to display text, rectangles, icons, bitmaps, etc. A table of the static styles is shown below:
{|class="wikitable"
!Style||Results in
|-
|SS_AUTOSIZE||Automatically size to contain the text, icon, or bitmap
|-
|SS_BITMAP||Bitmap
|-
|SS_BKGNDFRAME||Unfilled rectangle painted with the background color
|-
|SS_BKGNDRECT||Filled rectangle painted with the background color
|-
|SS_FGNDFRAME||Unfilled rectangle painted with the foreground color
|-
|SS_FGNDRECT||Filled rectangle painted with the foreground color
|-
|SS_GROUPBOX||Groupbox
|-
|SS_HALFTONERECT||Filled rectangle painted with a halftoned color
|-
|SS_HALFTONEFRAME||Unfilled rectangle painted with a halftoned color
|-
|SS_ICON||Icon
|-
|SS_SYSICON||System icon
|-
|SS_TEXT||Text
|}


<p>Window text for SS_TEXT statics can be set and queried using the
All but the first style are mutually exclusive. The first style can only be used with SS_TEXT, SS_BITMAP, SS_ICON, or SS_SYSICON. Additionally, if SS_TEXT is used, you may also or one of the constants from each of the following groups to align the text in a specific manner.
WinSetWindowText() and WinQueryWindowText() functions. They accept no
messages, nor send any messages.


<h2>Using SS_ICON, SS_BITMAP, and SS_SYSICON statics</h2>
Horizontal alignment
{|class="wikitable"
!Constant||Alignment
|-
|DT_LEFT||Left aligned
|-
|DT_CENTER||Center aligned
|-
|DT_RIGHT||Right aligned
|}


<p>When creating one of these three types of static controls, the question
Vertical alignment
arises about how one specifies the icon, bitmap, or system icon to display.
{|class="wikitable"
The answer is in the window text.  For the first two, the text must be in
!Constant||Alignment
the form &quot;&#35;n&quot; where n is the ASCII representation of the resource
|-
identifier of the icon or bitmap to be displayed.  A noteworthy caveat is
|DT_TOP||Top aligned
that the icon or bitmap must reside in the .EXE resources; this can create
|-
problems if you're writing a general purpose DLL that cannot make
|DT_VCENTER||Center aligned
assumptions about the .EXE resources.  For the last one, the number
|-
represents the ASCII representation of the appropriate SPTR_* constant
|DT_BOTTOM||Bottom aligned
corresponding to the system icon that you wish to be displayed.
|}


<h2>Opportunities for Mayhem</h2>
Window text for SS_TEXT statics can be set and queried using the WinSetWindowText() and WinQueryWindowText() functions. They accept no messages, nor send any messages.


<p>Because the static control does nothing except &quot;just sit there,&quot; there are
==Using SS_ICON, SS_BITMAP, and SS_SYSICON statics==
plenty of opportunities to create quick-n- dirty solutions to problems by
When creating one of these three types of static controls, the question arises about how one specifies the icon, bitmap, or system icon to display.
creating a static window and then immediately subclassing it with the
The answer is in the window text. For the first two, the text must be in the form "&#35;n" where n is the ASCII representation of the resource identifier of the icon or bitmap to be displayed.  A noteworthy caveat is that the icon or bitmap must reside in the .EXE resources; this can create problems if you're writing a general purpose DLL that cannot make
intent of enhancing its behavior.
assumptions about the .EXE resources. For the last one, the number represents the ASCII representation of the appropriate SPTR_* constant corresponding to the system icon that you wish to be displayed.


==Opportunities for Mayhem==
Because the static control does nothing except "just sit there", there are
plenty of opportunities to create quick-n-dirty solutions to problems by creating a static window and then immediately subclassing it with the intent of enhancing its behavior.


<h2>That's It!</h2>
==That's It!==
That's it for this month.  Next month, we'll begin looking at the WC_MENU window class and we will see how it has become a staple in the bag of tricks that every OS/2 programmer has.  Again, I will gladly accept any feedback that you have regarding this column and its future.


<p>That's it for this month.  Next month, we'll begin looking at the WC_MENU
[[Category: PM Articles]]
window class and we will see how it has become a staple in the bag of
tricks that every OS/2 programmer has.  Again, I will gladly accept any
feedback that you have regarding this column and its future.

Latest revision as of 23:25, 7 March 2018

Written by Larry Salomon Jr.

Introduction

The purpose of this column is to provide the readers out there who are not familiar with PM application development the information necessary to satisfy their curiosity, educate themselves, and give them an advantage over the documentation supplied by IBM. Of course, much of this stuff could probably be found in one of the many books out there, but the problem with books in general is that they don't answer the questions you have after you read the book the first time through.

I will gladly entertain feedback from the readers about what was "glossed over" or what was detailed well, what tangential topics need to be covered and what superfluous crap should have been removed. This feedback is essential in guaranteeing that you get what you pay for. <grin>

It should be said that you must not depend solely on this column to teach you how to develop PM applications; instead, this should be viewed as a supplement to your other information storehouses (books, the network conferences, etc.). Because this column must take a general approach, there will be some topics that you would like to see discussed that really do not belong here. Specific questions can be directed to me via email and I will do my best to answer them in a timely fashion.

Last Month

Last month, we finished the WC_LISTBOX class and I asked for feedback. I did receive some, for which I am very grateful, but the majority of them were requests for advanced topics, like the container and the notebook controls. We will eventually cover these window classes, but it is essential that we look at the rudimentary ones first, so that you can better appreciate what these advanced classes do for you.

This month, we will look at the WC_TITLEBAR and WC_STATIC window classes. Since both of these classes are not too involving, covering them both should not be a problem.

The Titlebar

The titlebar class (WC_TITLEBAR) is usually not created directly, but is created for you by the frame window through the WinCreateStdWindow() call. It has two primary functions: 1) to display the text of the standard window to which it belongs, and 2) to act as a shortcut to two primary windowing functions, move and maximize/restore.

The titlebar does accept two messages: TBM_SETHILITE and TBM_QUERYHILITE.

TBM_SETHILITE

This message sets the highlight state of the control.

Parameters

SHORT1FROMMP(mpParm1) - the new highlight state of the control.

TRUE Draw the control in highlighted state.
FALSE Draw the control in normal state.

Returns

SHORT1FROMMR() - success indicator.

TRUE Successful completion.
FALSE Error occurred.

TBM_QUERYHILITE

This message returns the highlight state of the control.

Returns

SHORT1FROMMR() - highlight state of the control.

TRUE The control is drawn in highlighted state.
FALSE The control is drawn in normal state.

Highlight state is used to indicate that the window has the focus. Normally, you do not need to use these messages, since the frame control will use them on your behalf.

To set or query the text displayed in the titlebar, use WinSetWindowText() and WinQueryWindowText(). Again, the frame makes this easy by setting or querying it for you whenever you set or query the frame window's text.

For reference, it should be noted that, whenever the user attempts to move or maximize/restore the window using the titlebar, the titlebar sends its owner (the frame usually) a WM_QUERYTRACKINFO message. The owner can fill in this structure according to its needs to restrict movement or resizing as necessary. We will not discuss this further.

That's all there is to the WC_TITLEBAR class.

The Static

The static control is just that: static. It never changes. The point of the static control is to display text, rectangles, icons, bitmaps, etc. A table of the static styles is shown below:

Style Results in
SS_AUTOSIZE Automatically size to contain the text, icon, or bitmap
SS_BITMAP Bitmap
SS_BKGNDFRAME Unfilled rectangle painted with the background color
SS_BKGNDRECT Filled rectangle painted with the background color
SS_FGNDFRAME Unfilled rectangle painted with the foreground color
SS_FGNDRECT Filled rectangle painted with the foreground color
SS_GROUPBOX Groupbox
SS_HALFTONERECT Filled rectangle painted with a halftoned color
SS_HALFTONEFRAME Unfilled rectangle painted with a halftoned color
SS_ICON Icon
SS_SYSICON System icon
SS_TEXT Text

All but the first style are mutually exclusive. The first style can only be used with SS_TEXT, SS_BITMAP, SS_ICON, or SS_SYSICON. Additionally, if SS_TEXT is used, you may also or one of the constants from each of the following groups to align the text in a specific manner.

Horizontal alignment

Constant Alignment
DT_LEFT Left aligned
DT_CENTER Center aligned
DT_RIGHT Right aligned

Vertical alignment

Constant Alignment
DT_TOP Top aligned
DT_VCENTER Center aligned
DT_BOTTOM Bottom aligned

Window text for SS_TEXT statics can be set and queried using the WinSetWindowText() and WinQueryWindowText() functions. They accept no messages, nor send any messages.

Using SS_ICON, SS_BITMAP, and SS_SYSICON statics

When creating one of these three types of static controls, the question arises about how one specifies the icon, bitmap, or system icon to display. The answer is in the window text. For the first two, the text must be in the form "#n" where n is the ASCII representation of the resource identifier of the icon or bitmap to be displayed. A noteworthy caveat is that the icon or bitmap must reside in the .EXE resources; this can create problems if you're writing a general purpose DLL that cannot make assumptions about the .EXE resources. For the last one, the number represents the ASCII representation of the appropriate SPTR_* constant corresponding to the system icon that you wish to be displayed.

Opportunities for Mayhem

Because the static control does nothing except "just sit there", there are plenty of opportunities to create quick-n-dirty solutions to problems by creating a static window and then immediately subclassing it with the intent of enhancing its behavior.

That's It!

That's it for this month. Next month, we'll begin looking at the WC_MENU window class and we will see how it has become a staple in the bag of tricks that every OS/2 programmer has. Again, I will gladly accept any feedback that you have regarding this column and its future.

Retrieved from "https://www.edm2.com/index.php?title=Introduction_to_PM_Programming_-_Feb_1995&oldid=55426"