perl-win32-gui-users — Using the Win32::GUI Perl extension

Re: [perl-win32-gui-users] Bug bug bug

[Robert M. <rob...@us...>]

Glenn Linderman wrote:
> I continued looking at this issue, and discovered some code in my "real" 
> program, that wasn't in the test program.
> 
> Apparently, way back in the dark ages of Win32::GUI, in order to get 
> things to work right, I had to "fiddle" with some of the style 
> settings... and some of that code made its way into a common subroutine, 
> and got included in this program too.
> 
> WS_VSCROLL | WS_VISIBLE | WS_CHILD | 1
> 
> The first two can be replaced in modern GUI by
> 
> -vscroll => 1, -visible => 1
> 
> Not sure that the third one is really necessary now, I think it was 
> necessary then because it was -setstyle (later converted to -addstyle).

-visible shouldn't be necessary.  -vscroll is required if you want a 
vertical scrollbar on the comboxbox's listview window.

Interesting history lesson.  I think I am seeing the reason for 
-setstyle being marked deprecated, although I think it still has its 
uses if you know what you're doing.

> Is there an option that is equivalent to WS_CHILD?

No.  Win32::GUI tries to get it right itself.  You shouldn't need this 
today, unless you're trying to do something funky.

> Not sure why the last one (1) was included, but clearly it is part of 
> the current confusion.

The (1) is CBS_SIMPLE.  So if you had this there and used -dropdown 
(CBS_DROPDOWN = 2) you'd actually get a dropdownlist (CBS_DROPDOWNLIST = 
3 = CBS_SIMPLE | CBS_DROPDOWN).  We're back to your original analysis.

I'll fix it so that if multiple of these 3 options are used, only the 
last one will actually take effect, not a combination of them, and I'll 
fix the docs to indicate that they are mutually exclusive.

Regards,
Rob.

Re: [perl-win32-gui-users] disabling the check on a checkbox???

[Robert M. <rob...@us...>]

Glenn Linderman wrote:
>  > At this point the control
>  > has seen a "click" and sends a BTN_CLICK (IIRC) notification to it's
>  > parent - it's already done all the other processing.  You could
>  > achieve what you are trying here by catching the _MouseDown event, and
>  > preventing that being delivered to the Button control.
> 
> So I changed -onClick to
> 
> -onMouseDown => sub { return 0; },
> 
> and it helps... but not quite enough... slow, individual clicks no 
> longer check the box... but a pair of rapid clicks will!
> 
> So I added
> 
> -onMouseUp => sub { return 0; },

You could instead catch and ignore the _MouseDblClick events.  When 
clicking on a window/control the event sequence is:
(1) MouseDown
(2) MouseUp
(3) MouseDblClick (if it happens soon enough after (1) and the 
window/control's Windows Class has the CS_DBLCLCKS style)
(4) MouseUp

> and it helps to the extent that the a pair of rapid clicks makes the 
> white part of the check box go grey when the mouse is over it... and 
> also has the extremely surprising side effect that the program no longer 
> terminates when clicking the close box... even though the handlers are 
> only on the Checkbox.  I have to ^C from the console window to terminate 
> it!  So this is extremely undesirable, and also not understood.

I can explain it now that I've seen it, but wouldn't have predicted it - 
it shows the dangers of not passing things to their default handlers :-( 
  The effect you see is not only that the close button doesn't work, but 
that you can't click anywhere in the window, including to move and 
resize the window - you can fix this by clicking on another window or 
the desktop.

This happens because on a double-click (and click) the buttom does a 
SetCapture(), so that it can see the eventual mouse up message even if 
you then drag the mouse off the button - so that it can redraw it in 
it's un-pushed state (try with a real button rather than a check box, 
it's more obvious.  If it didn't do this, then it wouldn't know if you 
let let the button up outside the button.

In this case you're not letting the button see mouse up messages, so it 
never does a ReleaseCapture() - fortunately you can get the system to do 
it for you by clicking in another window - the system allows this to 
prevent an application taking over the mouse forever (you'd need a 
system-wide hook to achieve this :-).

>  > You could also
>  > achieve what (I think) you are looking for by creating the control
>  > with the BS_CHECKBOX style, rather than the default BS_AUTOCHECKBOX.
>  > Then the control does not re-drw itself, and you have to tell it how
>  > it should look.
> 
> I'm not sure what you mean here... is it that you have to call 
> Checked(0) or Checked(1), or that you have to supply a user-draw routine 
> (I hope not!).  Some experimentation, below, proves you mean the 
> former!  This technique looks very workable.

Yes, that was what I meant.

Rob.

Re: [perl-win32-gui-users] Installing Win32::GUI (cpan) on perl/mingw/dmake

[Waldemar B. <wb...@sa...>]

Robert May napisał(a):
> On 23/04/07, Reini Urban <ru...@x-...> wrote:
>> Hi Waldemar,
>>
>> 2007/4/22, Waldemar Biernacki <wb...@sa...>:
>> > 1. the file GUI.rc (in root install directory) has readonly attribute
>> > and installation stops. When I change it to read/write attribute all
>> > pass OK. Is it a very small bug or I did something incorrectly?
>>
>> Thanks, this is a bug indeed.
>
> Hmm. I don't see that here (WinZip and Win98). What tools are used
> for unpacking, and what OS?
>
======================================
OS = Windows XPHE [ver 5.1.2600]
======================================
Mingw with gcc 3.4.5 (date is 2006-01-18)
======================================
dmake 4.8-20070327-SHAY (Windows / MS Visual C++)
======================================
After standard perl installation (sources "stable.tar.gz" version 5.8.8 
date 06-02-01 unpacked using the 7z software): dmake dmake test dmake 
install.
During the installation I installed additional software it wanted (gpg, 
gzip, tar ... and so on a lot of questions!)
Then I modified the files Config.pm and Config_heavy.pl properly.

The module Win32::GUI I installed using standard cpan command: "cpan 
install Win32::GUI". I noticed the problem with the
attribute. I pointed installation directory as "c:\perl\.cpan" and in 
the subdirectory of the packet
I have changed the attribute (being in cpan shell in another cmd shell), 
returned to cpan shell and push the cpan command again.
that's it.
I have to admit I wanted to install perl (and libraries including 
DBD::Pg instead DBD::PgPP and my own too) from source last 6 months 
trying various
perl/mingw/dmake/nmake/make software. At last I did it!

I've just compiled Wn32::GUI again downloading it from cpan again. No 
atribute problem. Was the packet exchanged? No compilation problems!
Some tests (after "dmake test") have not passed but no errors.



 > 2. Actually it has passed but not all! I'v got the note:
>> > =====================================================
>> > Win32::GUI::AxWindow can only be built using MSVC, not 'gcc',
>> > as it depends on the Microsoft Active Template Library (ATL).
>> > Win32::GUI::AxWindow will be skipped during the current build process.
>
>> > At this time Win32::GUI::DIBitmap cannot be build using gcc.
>> > Win32::GUI::DIBitmap will be skipped during the current build process.
>>
>> We assume that with mingw you don't have the original MSVC ATL 
>> libraries.
>> This is most likely wrong for you, so you have to fix the Makefile.PL
>>
>> > Win32::GUI::Grid can only be built using MSVC, not 'gcc',
>> > as it requires the MFC framework.
>> > Win32::GUI::Grid will be skipped during the current build process.
>>
>> We assume that with mingw you don't have the original MSVC MFC
>> libraries. This is most likely wrong for you, so you have to fix the
>> Makefile.PL
>
>> You only need the libraries and to fix the Makefile.
>
> If anyone has further information or success building these modules
> with mingw, then I'd be very interested in making this happen - I
> spent a long time looking at it last year, and drew a blank. I'm not
> convinced it's a simple problem.
>
> Regards,
> Rob.
>

Re: [perl-win32-gui-users] disabling the check on a checkbox???

[Robert M. <rob...@us...>]

On 24/04/07, Roode, Eric <er...@ba...> wrote:
> For what it's worth, I have always been unclear on what the Win32::GUI
> doco means by "the event is not passed to the default event processor".
> Any clarification, anywhere, would be useful.

OK.  The default handling of an event depends on the control.  For
example, consider a left mouse click (_MouseDown).  For a Window, the
default processing does nothing, so being able to stop it is, o be
honest, not very useful.   But, for a button, the default processing
of a left mouse down (performed by the control itself), is to re-draw
the button in the depressed state, and capture the mouse, waiting for
a mouse up event to occur.  In this case intercepting the _MouseDown
event, before the button sees it and preventing it being passed to
it's 'default handler' it would have the effect of stopping the user
clicking the button.

In general it's always advisable to allow messages to be passed on to
their default handler's, and only prevent that if there are known
side-effects that you want to stop.

Regards,
Rob.

Re: [perl-win32-gui-users] Bug bug bug

[Robert M. <rob...@us...>]

On 24/04/07, Glenn Linderman <pe...@ne...> wrote:
> On approximately 4/24/2007 11:57 AM, came the following characters from
> the keyboard of Robert May:
> > On 07/04/07, Glenn Linderman <pe...@ne...> wrote:
> >> I turned on -dropdown => 1 for a Combobox, and got a -dropdownlist style
> >> instead.
> >>
> >> The bottom two bits should be a 2-bit mask, for three values: simple =
> >> 1, dropdown = 2, dropdownlist = 3.  I'm not sure what 0 does...
> >> looks/acts a lot like when simple = 1.
> >
> > OK, I can see what needs to be changed in the code.  Can I confirm
> > that you're changing the style of the dropdown at run-time?  Will be
> > fixed in the next release.
>
> Thanks, Rob, I'm not sure what you mean by changing the style of the
> dropdown at run-time... I was using the  -dropdown => 1  and
> -dropdownlist => 1  sort of parameters to $mw->AddCombobox ...
>
> I wasn't doing anything like $cb->Change ...

OK, so where you using more than one of -dropdown, -dropdownlist and
-simple at the same time?  I'm struggling to tie up what I think the
code is dowing with what your describing.

Rob.

Re: [perl-win32-gui-users] Toggle "always on top" status

[Robert M. <rob...@us...>]

On 16/04/07, Perl Rob <pe...@co...> wrote:
> I'm using the "-topmost" option on my window to make it start out always on
> top. However, I'd like to provide a check box (labeled "Always on top" and
> checked by default) that allows the user to toggle whether the window stays
> on top or doesn't. Unfortunately, I can't get the change to take effect.
> Below is the code I'm trying. What am I doing wrong (or is this even
> possible)?
>
> sub AlwaysOnTop_Click
> {
>     $aot_state = $aot_check_box->GetCheck();
>     if ($aot_state == 0)
>     {
>             Win32::GUI::Change($main, -topmost => 0);
>     }

[snip]

Unfortunately -topmost is one of a small number of things that you
can't simply Change() after creating a window (all the topmost option
does is toggle the WS_EX_TOPMOST flag, which is documented by MS as
not the way to do it).

The 'correct' way to change the topmost state of a window is using the
SetWindowPos() method.  Here's some code:

#!perl -w
use strict;
use warnings;

use Win32::GUI qw(CW_USEDEFAULT HWND_TOPMOST HWND_NOTOPMOST
                             SWP_NOMOVE SWP_NOSIZE);

my $appname = 'Test App';

my $mw = Win32::GUI::Window->new(
       -title => $appname,
       -left  => CW_USEDEFAULT,
       -size  => [300,200],
);

$mw->AddCheckbox(
       -text    => 'Topmost',
       -pos     => [10,10],
       -onClick => \&set_topmost,
);

$mw->Show();
Win32::GUI::Dialog();
$mw->Hide();
exit(0);

sub set_topmost {
       my ($self) = @_;

       my $title = $appname;
       my $hwnd_after = HWND_NOTOPMOST;

       if ($self->Checked()) {
               $title .= ' - Topmost';
               $hwnd_after = HWND_TOPMOST;
       }

       $self->GetParent()->Text($title);
       $self->GetParent()->SetWindowPos($hwnd_after, 0,0,0,0,
                                                  SWP_NOMOVE|SWP_NOSIZE);

       return 0;
}
__END__

Regards,
Rob.

Re: [perl-win32-gui-users] Rich text field

[Robert M. <rob...@us...>]

On 22/04/07, Sean Healy <jal...@ho...> wrote:
> > I have already tried it, but I cannot store more than 32 KB of text in a
> > Richedit field (using Win32::GUI::Richedit).
> > Those 32 kb of text takes around 48 kb of rich text, but it cannot store
> > more than that.
>
> Look at the Win32::GUI::RidhEdit methods GetLimittext(), SetLimitText(),
> and LimiteText().
>
> An unfortunate misspelling on that last one; perhaps that can be fixed in
> a future version - as of 1.05 it's still LimiteText instead of LimitText
> Of course, both names may need to be kept for several versions, so as not
> to break any code that's using the misspelled version.

I've added it to my list of things to fix.  I assume that's a French
spelling ...

You may also be interested in this thread from when we discussed this
issue back in February:

https://sourceforge.net/mailarchive/message.php?msg_id=45CD1523.2010609%40optonline.net

Regards,
Rob.

Re: [perl-win32-gui-users] disabling the check on a checkbox???

[Robert M. <rob...@us...>]

On 24/04/07, Glenn Linderman <pe...@ne...> wrote:
> $mw->AddCheckbox(
>       -name   => "cb",
>       -text   => 'click me',
>       -pos    => [10, 20],
>       -tabstop  => 1,
>       -onClick => sub { return 0; },
> );
>
> Why does the above program allow the checkbox to be checked and
> unchecked?  Why doesn't the -onClick handler, which returns 0, prevent
> the box from being checked?

Because the _Click() events are generated by the Button control AFTER
it sees a mouse down and up combination.  At this point the control
has seen a "click" and sends a BTN_CLICK (IIRC) notification to it's
parent - it's already done all the other processing.  You could
achieve what you are trying here by catching the _MouseDown event, and
preventing that being delivered to the Button control.  You could also
achieve what (I think) you are looking for by creating the control
with the BS_CHECKBOX style, rather than the default BS_AUTOCHECKBOX.
Then the control does not re-drw itself, and you have to tell it how
it should look.

Regards,
Rob.

Re: [perl-win32-gui-users] Installing Win32::GUI (cpan) on perl/mingw/dmake

[Robert M. <rob...@us...>]

On 23/04/07, Reini Urban <ru...@x-...> wrote:
> Hi Waldemar,
>
> 2007/4/22, Waldemar Biernacki <wb...@sa...>:
> > 1. the file GUI.rc (in root install directory) has readonly attribute
> > and installation stops. When I change it to read/write attribute all
> > pass OK. Is it a very small bug or I did something incorrectly?
>
> Thanks, this is a bug indeed.

Hmm. I don't see that here (WinZip and Win98).  What tools are used
for unpacking, and what OS?

> > 2. Actually it has passed but not all! I'v got the note:
> > =====================================================
> > Win32::GUI::AxWindow can only be built using MSVC, not 'gcc',
> > as it depends on the Microsoft Active Template Library (ATL).
> > Win32::GUI::AxWindow will be skipped during the current build process.

> > At this time Win32::GUI::DIBitmap cannot be build using gcc.
> > Win32::GUI::DIBitmap will be skipped during the current build process.
>
> We assume that with mingw you don't have the original MSVC ATL libraries.
> This is most likely wrong for you, so you have to fix the Makefile.PL
>
> > Win32::GUI::Grid can only be built using MSVC, not 'gcc',
> > as it requires the MFC framework.
> > Win32::GUI::Grid will be skipped during the current build process.
>
> We assume that with mingw you don't have the original MSVC MFC
> libraries. This is most likely wrong for you, so you have to fix the
> Makefile.PL

> You only need the libraries and to fix the Makefile.

If anyone has further information or success building these modules
with mingw, then I'd be very interested in making this happen - I
spent a long time looking at it last year, and drew a blank.  I'm not
convinced it's a simple problem.

Regards,
Rob.

Re: [perl-win32-gui-users] ANNOUNCE: Updated Website Search Facility

[Robert M. <rob...@us...>]

On 14/04/07, Robert May <rob...@us...> wrote:
> I've just updated the search facility on the project's website to use a
> Google Custom Search that will search not only the project website and
> wiki, but also the mailing list archives[1] and the project's codebase.
>   I hope it is an improvement over what we had before.
>
> It's available at:
> http://perl-win32-gui.sourceforge.net/search
> and from the navigation bar on every other page.
>
> Please let me know if you have any problems, or if there are any other
> web resources that you think should be included in the results.

Well it was broken (I'd left a link to my test server in the code).  Fixed now.

Rob.

Re: [perl-win32-gui-users] Bug bug bug

[Robert M. <rob...@us...>]

On 07/04/07, Glenn Linderman <pe...@ne...> wrote:
> I turned on -dropdown => 1 for a Combobox, and got a -dropdownlist style
> instead.
>
> The bottom two bits should be a 2-bit mask, for three values: simple =
> 1, dropdown = 2, dropdownlist = 3.  I'm not sure what 0 does...
> looks/acts a lot like when simple = 1.

OK, I can see what needs to be changed in the code.  Can I confirm
that you're changing the style of the dropdown at run-time?  Will be
fixed in the next release.

[ As an aside a combobox treats no 'type style' the same as the
'simple' style.  If you set the styles to 0 on creation, you should
find that they are changed to 1 during creation].

Regards,
Rob.

Re: [perl-win32-gui-users] disabling the check on a checkbox???

[Roode, E. <er...@ba...>]

For what it's worth, I have always been unclear on what the Win32::GUI
doco means by "the event is not passed to the default event processor".
Any clarification, anywhere, would be useful.=20


Eric

-----Original Message-----
From: per...@li...
[mailto:per...@li...] On Behalf Of
Glenn W Munroe
Sent: Tuesday, April 24, 2007 2:27 PM
To: 'Glenn Linderman'; 'GUI'
Subject: Re: [perl-win32-gui-users] disabling the check on a checkbox???

Glenn,

I wouldn't expect it to prevent it from being checked. Do you expect
this behaviour from the Windows control itself or from Win32::GUI?
Certain actions for some controls have a "pre-change" notification (e.g.
the TCN_SELCHANGING notification sent when a tab is *about* to change),
which can be used to prevent the change, but I don't see anything like
that on MSDN for a checkbox.

Or do you expect this from Win32::GUI? I know a return value of 0
prevents the "default action" from taking place, but I see that as a
"post-change"
action, if that makes sense. (I'm not sure where that action is
defined).=20

Or am I missing your point entirely?

Glenn2

> -----Original Message-----
> From: per...@li... [mailto:perl-

> win...@li...] On Behalf Of Glenn=20
> Linderman
> Sent: 24 April 2007 13:39
> To: GUI
> Subject: [perl-win32-gui-users] disabling the check on a checkbox???
>=20
> use strict;
> use warnings;
>=20
> use Win32::GUI();
>=20
> my $mw;
>=20
> $mw =3D new Win32::GUI::Window(
>     -name         =3D> "mw",
>     -title        =3D> "Checkbox default action",
>     -pos          =3D> [100, 100],
>     -size         =3D> [200, 200],
>     -dialogui     =3D> 1,
> );
>=20
> $mw->AddCheckbox(
>       -name   =3D> "cb",
>       -text   =3D> 'click me',
>       -pos    =3D> [10, 20],
>       -tabstop  =3D> 1,
>       -onClick =3D> sub { return 0; },
> );
>=20
>=20
> $mw->Show();
> Win32::GUI::Dialog();
>=20
>=20
> Why does the above program allow the checkbox to be checked and=20
> unchecked?  Why doesn't the -onClick handler, which returns 0, prevent

> the box from being checked?
>=20
> --
> Glenn -- http://nevcal.com/
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
> A protocol is complete when there is nothing left to remove.
> -- Stuart Cheshire, Apple Computer, regarding Zero Configuration=20
> Networking
>=20
>=20
> ----------------------------------------------------------------------
> --- This SF.net email is sponsored by DB2 Express Download DB2 Express

> C - the FREE version of DB2 express and take control of your XML. No=20
> limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Perl-Win32-GUI-Users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
> http://perl-win32-gui.sourceforge.net/


------------------------------------------------------------------------
-
This SF.net email is sponsored by DB2 Express Download DB2 Express C -
the FREE version of DB2 express and take control of your XML. No limits.
Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Perl-Win32-GUI-Users mailing list
Per...@li...
https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
http://perl-win32-gui.sourceforge.net/

Re: [perl-win32-gui-users] disabling the check on a checkbox???

[Glenn W M. <gwm...@gm...>]

Glenn,

I wouldn't expect it to prevent it from being checked. Do you expect this
behaviour from the Windows control itself or from Win32::GUI? Certain
actions for some controls have a "pre-change" notification (e.g. the
TCN_SELCHANGING notification sent when a tab is *about* to change), which
can be used to prevent the change, but I don't see anything like that on
MSDN for a checkbox.

Or do you expect this from Win32::GUI? I know a return value of 0 prevents
the "default action" from taking place, but I see that as a "post-change"
action, if that makes sense. (I'm not sure where that action is defined). 

Or am I missing your point entirely?

Glenn2

> -----Original Message-----
> From: per...@li... [mailto:perl-
> win...@li...] On Behalf Of Glenn
> Linderman
> Sent: 24 April 2007 13:39
> To: GUI
> Subject: [perl-win32-gui-users] disabling the check on a checkbox???
> 
> use strict;
> use warnings;
> 
> use Win32::GUI();
> 
> my $mw;
> 
> $mw = new Win32::GUI::Window(
>     -name         => "mw",
>     -title        => "Checkbox default action",
>     -pos          => [100, 100],
>     -size         => [200, 200],
>     -dialogui     => 1,
> );
> 
> $mw->AddCheckbox(
>       -name   => "cb",
>       -text   => 'click me',
>       -pos    => [10, 20],
>       -tabstop  => 1,
>       -onClick => sub { return 0; },
> );
> 
> 
> $mw->Show();
> Win32::GUI::Dialog();
> 
> 
> Why does the above program allow the checkbox to be checked and
> unchecked?  Why doesn't the -onClick handler, which returns 0, prevent
> the box from being checked?
> 
> --
> Glenn -- http://nevcal.com/
> ===========================
> A protocol is complete when there is nothing left to remove.
> -- Stuart Cheshire, Apple Computer, regarding Zero Configuration
> Networking
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Perl-Win32-GUI-Users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
> http://perl-win32-gui.sourceforge.net/

[perl-win32-gui-users] Event debug

[Kieren D. <Kie...@ha...>]

Is there a way I can find out what events are triggered as windows are
manipulated?
I was trying to catch the event which is triggered when I press return
in a TextField, but I ended up setting it=20
as multiline and reacting to each Change event. I'm wondering whether I
could simply have the name wrong.
Could anyone help me, please?

Re: [perl-win32-gui-users] Rich text field

[Octavian R. <ora...@gm...>]

Hi Sean,

Thank you for your help. I hope I will be able to do it.

Octavian

----- Original Message ----- 
From: "Sean Healy" <jal...@ho...>
To: <per...@li...>
Sent: Sunday, April 22, 2007 7:08 PM
Subject: Re: [perl-win32-gui-users] Rich text field


>> I have already tried it, but I cannot store more than 32 KB of text in a
>> Richedit field (using Win32::GUI::Richedit).
>> Those 32 kb of text takes around 48 kb of rich text, but it cannot store
>> more than that.
>>
>> I have tried using the Load() and Save() methods  and I have also tried
>> creating the rich text manually and storing it in the field, but it
>> doesn't
>> allow more than 32 kb of text.
>
> Look at the Win32::GUI::RidhEdit methods GetLimittext(), SetLimitText(),
> and LimiteText().
>
> An unfortunate misspelling on that last one; perhaps that can be fixed in
> a future version - as of 1.05 it's still LimiteText instead of LimitText
> Of course, both names may need to be kept for several versions, so as not
> to break any code that's using the misspelled version.
>
> Here's some more info on the text size limit:
>
> EM_LIMITTEXT Message
>
> The EM_LIMITTEXT message sets the text limit of an edit control. The text
> limit is the maximum amount of text, in TCHARs, that the user can type
> into the edit control. You can send this message to either an edit control
> or a rich edit control.
>
> For edit controls and Microsoft Rich Edit 1.0, bytes are used. For Rich
> Edit 2.0 and later, characters are used.
>
> Syntax
>
> To send this message, call the SendMessage function as follows. lResult =
> SendMessage(     // returns LRESULT in lResult
>    (HWND) hWndControl,     // handle to destination control
>    (UINT) EM_LIMITTEXT,     // message ID
>    (WPARAM) wParam,     // = (WPARAM) () wParam;
>    (LPARAM) lParam     // = 0; not used, must be zero
> );
>
>
> Parameters
> wParam
> Specifies the maximum number of TCHARs the user can enter. For ANSI text,
> this is the number of bytes; for Unicode text, this is the number of
> characters. This number does not include the terminating null character.
>
> Rich edit controls: If this parameter is zero, the text length is set to
> 64,000 characters.
>
> Edit controls on Windows NT/2000/XP: If this parameter is zero, the text
> length is set to 0x7FFFFFFE characters for single-line edit controls or -1
> for multiline edit controls.
>
> Edit controls on Windows 95/98/Me: If this parameter is zero, the text
> length is set to 0x7FFE characters for single-line edit controls or 0xFFFF
> for multiline edit controls.
> lParam
> This parameter is not used.
>
> Return Value
> This message does not return a value.
>
> Remarks
>
> The EM_LIMITTEXT message limits only the text the user can enter. It does
> not affect any text already in the edit control when the message is sent,
> nor does it affect the length of the text copied to the edit control by
> the WM_SETTEXT message. If an application uses the WM_SETTEXT message to
> place more text into an edit control than is specified in the EM_LIMITTEXT
> message, the user can edit the entire contents of the edit control.
>
> Before EM_LIMITTEXT is called, the default limit for the amount of text a
> user can enter in an edit control is 32,767 characters.
>
> Edit controls on Windows NT/2000/XP: For single-line edit controls, the
> text limit is either 0x7FFFFFFE bytes or the value of the wParam
> parameter, whichever is smaller. For multiline edit controls, this value
> is either -1 byte or the value of the wParam parameter, whichever is
> smaller.
>
> Edit controls on Windows 95/98/Me: For single-line edit controls, the text
> limit is either 0x7FFE bytes or the value of the wParam parameter,
> whichever is smaller. For multiline edit controls, this value is either
> 0xFFFF bytes or the value of the wParam parameter, whichever is smaller.
>
> Rich Edit: Supported in Rich Edit 1.0 and later. Use the message
> EM_EXLIMITTEXT for text length values greater than 64,000. For information
> about the compatibility of rich edit versions with the various system
> versions, see About Rich Edit Controls.
>
> Message InformationHeader Declared in Winuser.h, include Windows.h
> Minimum operating systems Windows 95, Windows NT 3.1
>
>
> See Also
> Edit Controls Overview, EM_EXLIMITTEXT, WM_SETTEXT
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Perl-Win32-GUI-Users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
> http://perl-win32-gui.sourceforge.net/ 

Re: [perl-win32-gui-users] Installing Win32::GUI (cpan) on perl/mingw/dmake

[Reini U. <ru...@x-...>]

Hi Waldemar,

2007/4/22, Waldemar Biernacki <wb...@sa...>:
> I've decided to install Win32::GUI on my machine (WinXPHE) via cpan port.
> I've compiled perl from source using mingw+dmake and everything pass OK.
> BUT...
>
> when I was installing Win32:GUI (1.05) from cpan (using polish mirror)
> I've noticed two problems:
>
> 1. the file GUI.rc (in root install directory) has readonly attribute
> and installation stops. When I change it to read/write attribute all
> pass OK. Is it a very small bug or I did something incorrectly?

Thanks, this is a bug indeed.

> 2. Actually it has passed but not all! I'v got the note:
> =====================================================
> BUILDENV=mingw  Used build environment is: MSWin32 and MinGW
>
> NOTE: Makefile.PL will add the instruction to use the Resource Compiler to
> your Makefile; if you don't want to compile resources with your extension,
> call this script with this additional argument:
>
>     perl Makefile.PL USERESOURCE=0
>
> Win32::GUI::AxWindow can only be built using MSVC, not 'gcc',
> as it depends on the Microsoft Active Template Library (ATL).
> Win32::GUI::AxWindow will be skipped during the current build process.
>
> Writing Makefile for Win32::GUI::Constants - perfect.exe
> Writing Makefile for Win32::GUI::Constants
>
> At this time Win32::GUI::DIBitmap cannot be build using gcc.
> Win32::GUI::DIBitmap will be skipped during the current build process.

We assume that with mingw you don't have the original MSVC ATL libraries.
This is most likely wrong for you, so you have to fix the Makefile.PL

> Writing Makefile for Win32::GUI::DropFiles
>
> Win32::GUI::Grid can only be built using MSVC, not 'gcc',
> as it requires the MFC framework.
> Win32::GUI::Grid will be skipped during the current build process.

We assume that with mingw you don't have the original MSVC MFC
libraries. This is most likely wrong for you, so you have to fix the
Makefile.PL

> Writing Makefile for Win32::GUI::ReleaseNotes
> Writing Makefile for Win32::GUI::Scintilla
> Writing Makefile for Win32::GUI
> =====================================================

> My question: is it possible to install these uninstalled modules without
> installing MSVC and the mentioned libs: ATL and MFC?

You only need the libraries and to fix the Makefile.

-- 
Reini Urban
http://phpwiki.org/              http://murbreak.at/
http://spacemovie.mur.at/   http://helsinki.at/

Re: [perl-win32-gui-users] Rich text field

[Jason P. <jp...@un...>]

Nice! Thanks for the tip on the function, and the message parameters :)  
I'm sure some of us will be needing this in the future.

Sean Healy wrote:
>> I have already tried it, but I cannot store more than 32 KB of text in a
>> Richedit field (using Win32::GUI::Richedit).
>> Those 32 kb of text takes around 48 kb of rich text, but it cannot store
>> more than that.
>>
>> I have tried using the Load() and Save() methods  and I have also tried
>> creating the rich text manually and storing it in the field, but it  
>> doesn't
>> allow more than 32 kb of text.
>>     
>
> Look at the Win32::GUI::RidhEdit methods GetLimittext(), SetLimitText(),  
> and LimiteText().
>
> An unfortunate misspelling on that last one; perhaps that can be fixed in  
> a future version - as of 1.05 it's still LimiteText instead of LimitText  
> Of course, both names may need to be kept for several versions, so as not  
> to break any code that's using the misspelled version.
>
> Here's some more info on the text size limit:
>
> EM_LIMITTEXT Message
>
> The EM_LIMITTEXT message sets the text limit of an edit control. The text  
> limit is the maximum amount of text, in TCHARs, that the user can type  
> into the edit control. You can send this message to either an edit control  
> or a rich edit control.
>
> For edit controls and Microsoft Rich Edit 1.0, bytes are used. For Rich  
> Edit 2.0 and later, characters are used.
>
> Syntax
>
> To send this message, call the SendMessage function as follows. lResult =  
> SendMessage( 	    // returns LRESULT in lResult
>     (HWND) hWndControl, 	    // handle to destination control
>     (UINT) EM_LIMITTEXT, 	    // message ID
>     (WPARAM) wParam, 	    // = (WPARAM) () wParam;
>     (LPARAM) lParam 	    // = 0; not used, must be zero
> ); 	
>
>
> Parameters
> wParam
> Specifies the maximum number of TCHARs the user can enter. For ANSI text,  
> this is the number of bytes; for Unicode text, this is the number of  
> characters. This number does not include the terminating null character.
>
> Rich edit controls: If this parameter is zero, the text length is set to  
> 64,000 characters.
>
> Edit controls on Windows NT/2000/XP: If this parameter is zero, the text  
> length is set to 0x7FFFFFFE characters for single-line edit controls or -1  
> for multiline edit controls.
>
> Edit controls on Windows 95/98/Me: If this parameter is zero, the text  
> length is set to 0x7FFE characters for single-line edit controls or 0xFFFF  
> for multiline edit controls.
> lParam
> This parameter is not used.
>
> Return Value
> This message does not return a value.
>
> Remarks
>
> The EM_LIMITTEXT message limits only the text the user can enter. It does  
> not affect any text already in the edit control when the message is sent,  
> nor does it affect the length of the text copied to the edit control by  
> the WM_SETTEXT message. If an application uses the WM_SETTEXT message to  
> place more text into an edit control than is specified in the EM_LIMITTEXT  
> message, the user can edit the entire contents of the edit control.
>
> Before EM_LIMITTEXT is called, the default limit for the amount of text a  
> user can enter in an edit control is 32,767 characters.
>
> Edit controls on Windows NT/2000/XP: For single-line edit controls, the  
> text limit is either 0x7FFFFFFE bytes or the value of the wParam  
> parameter, whichever is smaller. For multiline edit controls, this value  
> is either -1 byte or the value of the wParam parameter, whichever is  
> smaller.
>
> Edit controls on Windows 95/98/Me: For single-line edit controls, the text  
> limit is either 0x7FFE bytes or the value of the wParam parameter,  
> whichever is smaller. For multiline edit controls, this value is either  
> 0xFFFF bytes or the value of the wParam parameter, whichever is smaller.
>
> Rich Edit: Supported in Rich Edit 1.0 and later. Use the message  
> EM_EXLIMITTEXT for text length values greater than 64,000. For information  
> about the compatibility of rich edit versions with the various system  
> versions, see About Rich Edit Controls.
>
> Message InformationHeader	Declared in Winuser.h, include Windows.h
> Minimum operating systems	Windows 95, Windows NT 3.1
>
>
> See Also
> Edit Controls Overview, EM_EXLIMITTEXT, WM_SETTEXT
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Perl-Win32-GUI-Users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
> http://perl-win32-gui.sourceforge.net/
>
>
>   

[perl-win32-gui-users] Installing Win32::GUI (cpan) on perl/mingw/dmake

[Waldemar B. <wb...@sa...>]

Hi!
I've decided to install Win32::GUI on my machine (WinXPHE) via cpan port.
I've compiled perl from source using mingw+dmake and everything pass OK.
BUT...

when I was installing Win32:GUI (1.05) from cpan (using polish mirror) 
I've noticed two problems:

1. the file GUI.rc (in root install directory) has readonly attribute 
and installation stops. When I change it to read/write attribute all 
pass OK. Is it a very small bug or I did something incorrectly?
2. Actually it has passed but not all! I'v got the note:

=====================================================
BUILDENV=mingw  Used build environment is: MSWin32 and MinGW

NOTE: Makefile.PL will add the instruction to use the Resource Compiler to
your Makefile; if you don't want to compile resources with your extension,
call this script with this additional argument:

    perl Makefile.PL USERESOURCE=0

Win32::GUI::AxWindow can only be built using MSVC, not 'gcc',
as it depends on the Microsoft Active Template Library (ATL).
Win32::GUI::AxWindow will be skipped during the current build process.

Writing Makefile for Win32::GUI::Constants - perfect.exe
Writing Makefile for Win32::GUI::Constants

At this time Win32::GUI::DIBitmap cannot be build using gcc.
Win32::GUI::DIBitmap will be skipped during the current build process.

Writing Makefile for Win32::GUI::DropFiles

Win32::GUI::Grid can only be built using MSVC, not 'gcc',
as it requires the MFC framework.
Win32::GUI::Grid will be skipped during the current build process.

Writing Makefile for Win32::GUI::ReleaseNotes
Writing Makefile for Win32::GUI::Scintilla
Writing Makefile for Win32::GUI
=====================================================


My question: is it possible to install these uninstalled modules without 
installing MSVC and the mentioned libs: ATL and MFC?

wb

Re: [perl-win32-gui-users] Rich text field

[Sean H. <jal...@ho...>]

> I have already tried it, but I cannot store more than 32 KB of text in=
 a
> Richedit field (using Win32::GUI::Richedit).
> Those 32 kb of text takes around 48 kb of rich text, but it cannot sto=
re
> more than that.
>
> I have tried using the Load() and Save() methods  and I have also trie=
d
> creating the rich text manually and storing it in the field, but it  =

> doesn't
> allow more than 32 kb of text.

Look at the Win32::GUI::RidhEdit methods GetLimittext(), SetLimitText(),=
  =

and LimiteText().

An unfortunate misspelling on that last one; perhaps that can be fixed i=
n  =

a future version - as of 1.05 it's still LimiteText instead of LimitText=
  =

Of course, both names may need to be kept for several versions, so as no=
t  =

to break any code that's using the misspelled version.

Here's some more info on the text size limit:

EM_LIMITTEXT Message

The EM_LIMITTEXT message sets the text limit of an edit control. The tex=
t  =

limit is the maximum amount of text, in TCHARs, that the user can type  =

into the edit control. You can send this message to either an edit contr=
ol  =

or a rich edit control.

For edit controls and Microsoft Rich Edit 1.0, bytes are used. For Rich =
 =

Edit 2.0 and later, characters are used.

Syntax

To send this message, call the SendMessage function as follows. lResult =
=3D  =

SendMessage( 	    // returns LRESULT in lResult
    (HWND) hWndControl, 	    // handle to destination control
    (UINT) EM_LIMITTEXT, 	    // message ID
    (WPARAM) wParam, 	    // =3D (WPARAM) () wParam;
    (LPARAM) lParam 	    // =3D 0; not used, must be zero
); 	=



Parameters
wParam
Specifies the maximum number of TCHARs the user can enter. For ANSI text=
,  =

this is the number of bytes; for Unicode text, this is the number of  =

characters. This number does not include the terminating null character.=


Rich edit controls: If this parameter is zero, the text length is set to=
  =

64,000 characters.

Edit controls on Windows NT/2000/XP: If this parameter is zero, the text=
  =

length is set to 0x7FFFFFFE characters for single-line edit controls or =
-1  =

for multiline edit controls.

Edit controls on Windows 95/98/Me: If this parameter is zero, the text  =

length is set to 0x7FFE characters for single-line edit controls or 0xFF=
FF  =

for multiline edit controls.
lParam
This parameter is not used.

Return Value
This message does not return a value.

Remarks

The EM_LIMITTEXT message limits only the text the user can enter. It doe=
s  =

not affect any text already in the edit control when the message is sent=
,  =

nor does it affect the length of the text copied to the edit control by =
 =

the WM_SETTEXT message. If an application uses the WM_SETTEXT message to=
  =

place more text into an edit control than is specified in the EM_LIMITTE=
XT  =

message, the user can edit the entire contents of the edit control.

Before EM_LIMITTEXT is called, the default limit for the amount of text =
a  =

user can enter in an edit control is 32,767 characters.

Edit controls on Windows NT/2000/XP: For single-line edit controls, the =
 =

text limit is either 0x7FFFFFFE bytes or the value of the wParam  =

parameter, whichever is smaller. For multiline edit controls, this value=
  =

is either -1 byte or the value of the wParam parameter, whichever is  =

smaller.

Edit controls on Windows 95/98/Me: For single-line edit controls, the te=
xt  =

limit is either 0x7FFE bytes or the value of the wParam parameter,  =

whichever is smaller. For multiline edit controls, this value is either =
 =

0xFFFF bytes or the value of the wParam parameter, whichever is smaller.=


Rich Edit: Supported in Rich Edit 1.0 and later. Use the message  =

EM_EXLIMITTEXT for text length values greater than 64,000. For informati=
on  =

about the compatibility of rich edit versions with the various system  =

versions, see About Rich Edit Controls.

Message InformationHeader	Declared in Winuser.h, include Windows.h
Minimum operating systems	Windows 95, Windows NT 3.1


See Also
Edit Controls Overview, EM_EXLIMITTEXT, WM_SETTEXT

Re: [perl-win32-gui-users] Rich text field

[Octavian R. <ora...@gm...>]

> From: "Jason Plum" <jp...@un...>
>
>
>> Hi,
>>
>> Yes, I believe it is quite possible, as unless I am mistaken, I have had
>> > 1MB loaded into a rich edit in one of my widely used programs.
>>
>> The easy way to test it would simply be to create it, and load in > 200KB 
>> of text from some file (or randomly even).
>> Try creating the richtext control and and a textfield. cycle it through 
>> say, 256 characters at a time, upping the value in the text field. This 
>> would give you a visual of where it dies, if it dies.
>>
>> Jason
>>

Hi,

I have already tried it, but I cannot store more than 32 KB of text in a 
Richedit field (using Win32::GUI::Richedit).
Those 32 kb of text takes around 48 kb of rich text, but it cannot store 
more than that.

I have tried using the Load() and Save() methods  and I have also tried 
creating the rich text manually and storing it in the field, but it doesn't 
allow more than 32 kb of text.

Thank you.

Octavian

[perl-win32-gui-users] List box populate

[Parker, C. \(OTDA\) <Chr...@ot...>]

Hello,

How do I repopulate a combobox.

I have 3 comboboxes that I want to populate first.  They are username,
pin, and pc name.  I want to be able to say, if you select a username
then it will change the corresponding pin and pc name.
This uses dbi also.  I havent been able to find any howto's for this. =20
perl, v5.8.8=20

----Code snip----
$cmbIndiv =3D $W2->AddCombobox(
								-name
=3D> 	"cmbIndiv",
								-left
=3D>	110,
								-top
=3D>	10,
								-height
=3D>	30,
								-width
=3D>	150,
								-menu
=3D>	1,
								-tabstop
=3D>	1,
=09
-ShowDropDown	=3D>	1,
								-sort
=3D>	1,
							=09
);
$cmbFed =3D $W2->AddCombobox(
								-name
=3D> 	"cmbFed",
								-left
=3D>	110,
								-top
=3D>	30,
								-height
=3D>	30,
								-width
=3D>	150,
								-menu
=3D>	1,
								-tabstop
=3D>	1
								-sort
=3D>	1,
);
$cmbMach =3D $W2->AddCombobox(
								-name
=3D> 	"cmbMach",
								-left
=3D>	110,
								-top
=3D>	50,
								-height
=3D>	30,
								-width
=3D>	150,
								-menu
=3D>	1,
								-tabstop
=3D>	1
								-sort
=3D>	1,
);

---db connect here---
sub cmbIndiv_Change {
	#open connection to Access database
$dbh =3D DBI->connect('dbi:ODBC:computers.mdb');

# Get selected values COMBOBOXES
#Indiv
$n =3D $cmbIndiv->GetCurSel();
$Indivname =3D $cmbIndiv->GetLBText($n);
#fedpin
$o =3D $cmbFed->GetCurSel();
$fedpin =3D $cmbFed->GetLBText($0);
#machine name
$p =3D $cmbMach->GetCurSel();
$machine =3D $cmbMach->GetLBText($p);
@vars =3D ($Indivname, $fedpin, $machine);
$sql1 =3D q/select * from computers where column =3D ?/;
=09
		$sth =3D $dbh->prepare($sql1);
		$sth->execute(($Indivname));
		my ($username, $pin, $mach);
			$sth->bind_col(1, \$username);
			$sth->bind_col(2, \$pin);
			$sth->bind_col(3, \$mach);
				while ($sth->fetch) {=20
    				#$cmbIndiv->Add($username);
    				$cmbfed->Change($pin);
    				$cmbMach->Change($mach);
    				print STDERR "first arg: $pin in $mach
and $username";
    			}
}

Chris Parker
Network Administration
chr...@ot...
518-486-9508
****************Quote***********************
I strongly recommend that you read "How To Ask Questions The Smart=20
way" by Eric Raymond:
http://www.catb.org/~esr/faqs/smart-questions.html.
****************End Quote*******************
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer.=20
--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged =
or otherwise legally protected. It is intended only for the addressee. =
If you received this e-mail in error or from someone who was not =
authorized to send it to you, do not disseminate, copy or otherwise use =
this e-mail or its attachments.  Please notify the sender immediately by =
reply e-mail and delete the e-mail from your system.

[perl-win32-gui-users] Rich text field

[Octavian R. <ora...@gm...>]

Hi,

Is it possible to create a big Richtext field using Win32::GUI?
For example to hold more than 200 KB.

Thank you.

Octavian

[perl-win32-gui-users] Toggle "always on top" status

[Perl R. <pe...@co...>]

Hi,

 

I'm using the "-topmost" option on my window to make it start out always on
top. However, I'd like to provide a check box (labeled "Always on top" and
checked by default) that allows the user to toggle whether the window stays
on top or doesn't. Unfortunately, I can't get the change to take effect.
Below is the code I'm trying. What am I doing wrong (or is this even
possible)?

 

 

sub AlwaysOnTop_Click

{

    $aot_state = $aot_check_box->GetCheck();

    if ($aot_state == 0)

    {

            Win32::GUI::Change($main, -topmost => 0);

    }

    else

    {

            Win32::GUI::Change($main, -topmost => 1);

    }

}

 

 

Thanks,

Rob

[perl-win32-gui-users] ANNOUNCE: Updated Website Search Facility

[Robert M. <rob...@us...>]

I've just updated the search facility on the project's website to use a 
Google Custom Search that will search not only the project website and 
wiki, but also the mailing list archives[1] and the project's codebase. 
  I hope it is an improvement over what we had before.

It's available at:
http://perl-win32-gui.sourceforge.net/search
and from the navigation bar on every other page.

Please let me know if you have any problems, or if there are any other 
web resources that you think should be included in the results.

Regards,
Rob.

[1] Currently there are not mailing list archive results being returned 
- this appears to be because Google has not yet re-indexed the new 
Sourceforge mail archives.


-- 
Robert May
Win32::GUI, a perl extension for native Win32 applications
http://perl-win32-gui.sourceforge.net/

[perl-win32-gui-users] How to pass a Picture* typed value to the interface of an ActiveX control.

[rob <rob...@gm...>]

hi,

I need to use Win32::GUI::AxWindow to call some ActiveX controls,
some of which interface needs a Picture* value.
Taking SCGrid.ocx (Samples/SCGrid.pl) for an example, if need to call
CellPicture,

[id(0x68030261), propputref]
void CellPicture(
                [in] short Row,
                [in] short Col,
                [in] Picture* rhs);

how to initialize a Picture structure?
Is it able to convert a Win32::GUI:BitBmp object to a Picture* ?

Any help appreciated.

Thanks,

Rob