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

2007-04-22 Thread Octavian Rasnita

From: Jason Plum [EMAIL PROTECTED]



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





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

2007-04-22 Thread Sean Healy

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 0x7FFE 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 0x  
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 0x7FFE 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  
0x 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




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

2007-04-22 Thread Waldemar Biernacki

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