Maximum characters that can bet output in the Debug Window ?

[dominique]

I think this problem wasn't there in the previous version of AutoIt
I now use V3.3.18.0

When a debug output window is created by _DebugSetup($sTitle) the number of characters that can be output seems to be limited.

To test this, I am writing as many lines of about 100 bytes as possible, and the output stops in the middle of the 287th line, which means that the debug window can output about 30000 bytes maximum.  From where does this limitation come from? How can this restriction be removed?

This is what is where the output stops.

281ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
282ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
283ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
284ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
285ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
286ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
287ABCDEFGHIJ123456789012345

[Jos]

Why would you want to debug such long strings to an interaction output window?  Won't logging the debug info to a log file make way more sense? 

[Festerini]

2 hours ago, dominique said:

I think this problem wasn't there in the previous version of AutoIt
I now use V3.3.18.0

When a debug output window is created by _DebugSetup($sTitle) the number of characters that can be output seems to be limited.

To test this, I am writing as many lines of about 100 bytes as possible, and the output stops in the middle of the 287th line, which means that the debug window can output about 30000 bytes maximum.  From where does this limitation come from? How can this restriction be removed?

This is what is where the output stops.

281ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
282ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
283ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
284ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
285ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
286ABCDEFGHIJ12345678901234567890ABCDEFGHIJ12345678901234567890ABCDEFGHIJ123456789012345678901234567890
287ABCDEFGHIJ123456789012345

As Jos says debugging to a log file makes more sense. More importantly, what is the application that requires that much data in debugging?  Is it actual debugging or you are using that function as part of a script?

 

[mLipok]

2 hours ago, dominique said:

From where does this limitation come from? How can this restriction be removed?

Debug.au3 UDF

GUICtrlSendMsg($__g_hReportEdit_Debug, $EM_LIMITTEXT, 0, 0) ; Max the size of the edit control.

and
https://learn.microsoft.com/en-us/windows/win32/controls/em-limittext

Edited February 22 by mLipok

[mLipok]

try this:
 

#include <GUIConstantsEx.au3>
#include <GuiEdit.au3>
#include <MsgBoxConstants.au3>

Example()

Func Example()
    ; Create GUI
    GUICreate("Edit Get/Set Limit Text (v" & @AutoItVersion & ")", 400, 300)
    Local $idEdit = GUICtrlCreateEdit("This is a test" & @CRLF & "Another Line", 2, 2, 394, 268)
    GUISetState(@SW_SHOW)

    MsgBox($MB_SYSTEMMODAL, "Information", "Text Limit: " & _GUICtrlEdit_GetLimitText($idEdit))

    MsgBox($MB_SYSTEMMODAL, "Information", "Setting Text Limit")
    _GUICtrlEdit_SetLimitText($idEdit, 1024*1024)

    MsgBox($MB_SYSTEMMODAL, "Information", "Text Limit: " & _GUICtrlEdit_GetLimitText($idEdit))

    ; Loop until the user exits.
    Do
    Until GUIGetMsg() = $GUI_EVENT_CLOSE
    GUIDelete()
EndFunc   ;==>Example

 

[dominique]

>>> Why would you want to debug such long strings to an interaction output window?  Won't logging the debug info to a log file make way more sense? 

I always used that window where I can trace the behavior of the program. So _DebugOut() produces a trace of the execution.

>>> As Jos says debugging to a log file makes more sense. More importantly, what is the application that requires that much data in debugging?  Is it actual debugging or you are using that function as part of a script?

If that info is put into a log file, you cannot see in real time how the application functions.  I merely use that window as a command window where only output is directed to.

I still do not see how I could increase the size of that "Edit" Edit field. Once the GUI is created by

Global $sTrace =  "IFA_execution trace"
_DebugSetup($sTrace)
What would be the next command to increase the buffer space of that window?

_GUICtrlEdit_SetLimitText($sTrace, 1024*1024) does not help

 

In AutoIt 3.3.14.5 that buffer was quasi unlimited. With AutoIt 3.3.18.0 that buffer size appears decreased.

[mLipok]

ufff..

_GUICtrlEdit_SetLimitText($__g_idEdt_Report_Debug, 1024*1024)

 

[dominique]

Thanks,  I now realize the GUI function needed to access the global variable in order to work. 

$__g_idEdt_Report_Debug

[dominique]

In addition 

_GUICtrlEdit_SetLimitText($__g_idEdt_Report_Debug, 1024*1024)

only works when at least 1 Debug line has already been written to the debug window such as

_DebugOut(" Start tracing ...")