Message-ID: <41C9EABC.4070901@clanganke.de>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
MIME-Version: 1.0
References: <E1ChCHa-0004N8-00@pop-a065d14.pas.sa.earthlink.net>
In-Reply-To: <E1ChCHa-0004N8-00@pop-a065d14.pas.sa.earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Wed, 22 Dec 2004 22:44:28 +0100
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Christian Langanke <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] wlanstat icon size (was Jacaranda for dummies)

Steven Levine wrote:

>It might be nice to support some additional icon sizes for those that wish
>to run standalone.  This would allow selecting an icon size consistent
>with the other desktop icons.
>
oops, got you as well :-)
size*4 is already implemented. Think I wrote it already: launch 
readme.cmd, search "size" or execute  context menu item of the 
standalone executable: "Window" - "Large window size"

Nevertheless I stick to the point that if a 16x16 icon cannot longer be 
recognized, the window solution is set too high.

>BTW, just wondering.  What was the reason for using MB1 for moving the
>icon?  This is somewhat inconsistent for OS/2.
>
Nearly... MB2 initiates drag and drop, MB1 initiates a move of a program 
window (think of moving the window by dragging the title bar with MB1). 
OTOH this difference is not very obvious for a so tiny window, so I 
would allow both if possible. But...

If a button down event  (for either button) is catched by the window 
procedure to initiate the window move by sending a TRACKFRAME message to 
the frame window (my code), this for unknown reasons interrupts the 
normal window message sequence (Presentation Manager code). This normal 
sequence among other messages would normally include that the button up 
event for the same button is posted/sent to the window procedure.

Now the button up event (to be precise: the one for MB2) is used for to 
launch the context menu. So if I use the MB2 down event to send the 
TRACKFRAME message, moving the window, the MB2 button up event is never 
sent, hence we loose the context menu...

If somebody can tell me how to solve this, I'd tend to allow the window 
move with either button.

bye, Christian

-------------------------------------------------

Christian Langanke
COS2E & CWSE
Team OS/2 Ruhr e.V.
cla@clanganke.de




=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).

For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).

This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=