Custom Query (3933 matches)
Results (436 - 438 of 3933)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3555 | Works For Me | _GUICtrlRichEdit_StreamToVar with > 2048 characters | ||
| Description |
This bug was discussed and solved here: https://www.autoitscript.com/forum/topic/188643-is-_guictrlrichedit_streamtovar-limited-to-2048-chars/ The problem happens when trying to stream a RichEdit with length > 2048 to a variable with _GUICtrlRichEdit_StreamToVar. The stream to file works correctly in this matter. The problem lies within this code which is called by the function: Func __GCR_StreamToVarCallback($iCookie, $pBuf, $iBuflen, $pQbytes)
#forceref $iCookie
Local $tQbytes = DllStructCreate("long", $pQbytes)
DllStructSetData($tQbytes, 1, 0)
Local $tBuf = DllStructCreate("char[" & $iBuflen & "]", $pBuf)
Local $s = DllStructGetData($tBuf, 1)
$__g_pGRC_sStreamVar &= $s
Return 0
EndFunc ;==>__GCR_StreamToVarCallback
The buffer is not updated correctly at the end of the function. The solution is to add a line before the return statement and modify the earlier struct set: Func __GCR_StreamToVarCallback($iCookie, $pBuf, $iBuflen, $pQbytes)
#forceref $iCookie
Local $tQbytes = DllStructCreate("long", $pQbytes)
DllStructSetData($tQbytes, 1, $iBuflen) ;Modified this line
Local $tBuf = DllStructCreate("char[" & $iBuflen & "]", $pBuf)
Local $s = DllStructGetData($tBuf, 1)
$__g_pGRC_sStreamVar &= $s
DllStructSetData($tQbytes, 1, StringLen($s)) ;Added this line
Return 0
EndFunc ;==>__GCR_StreamToVarCallback
This correctly updates the struct and solves the character limit. |
|||
| #3554 | Rejected | Ini functions should be documentated as containing limitations | ||
| Description |
There's an old feature request #15 about fixing the various limitations of the Ini functions (what's not mentioned there is that they sometimes throw an @error when their target is called Autoinf.inf). But I have a different feature request - just document the fact that there are limitations, to avoid confusion. Do functions like FileRead not suffer from such limitations because they are custom made by AutoIt, while Ini functions use Windows API? If so, mention this officially. For example: IniReadSectionNames Remarks Note that Ini functions rely on Windows API which suffers from various limitations. This situation shall remain as Microsoft asked to use other storage methods. Custom UDFs that bypass the limitations can be found on AutoIt's forums. |
|||
| #3553 | Rejected | _SQLite_Startup() - cannot use SQLite.dll without "_x64" suffix in 64 bit script | ||
| Description |
Now _SQLite_Startup() prohibit use dll without "_x64" in dll name in 64 bit script. It not very convenient. Func _SQLite_StartupEX($sDll_Filename = "", $bUTF8ErrorMsg = False, $iForceLocal = 0, $hPrintCallback = $__g_hPrintCallback_SQLite) #forceref $iForceLocal If $sDll_Filename = Default Or $sDll_Filename = -1 Then $sDll_Filename = "" If $hPrintCallback = Default Then $hPrintCallback = __SQLite_ConsoleWrite $__g_hPrintCallback_SQLite = $hPrintCallback If $bUTF8ErrorMsg = Default Then $bUTF8ErrorMsg = False $__g_bUTF8ErrorMsg_SQLite = $bUTF8ErrorMsg If $sDll_Filename = "" Then $sDll_Filename = "sqlite3.dll" Local $hDll = DllOpen($sDll_Filename) If $hDll = -1 Then $__g_hDll_SQLite = 0 Return SetError(1, 0, "") Else $__g_hDll_SQLite = $hDll Return SetExtended(0, $sDll_Filename) EndIf EndFunc ;==>_SQLite_Startup |
|||
