Custom Query
Results (31 - 33 of 3866)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#32 | Gary | DarkTurok | Fixed | _GUICtrlTreeView_GetNext does not return 0 for last item |
Description |
The following code shows a bug in _GUICtrlTreeView_GetNext. The bug also affects _GUICtrlTreeView_FindItem; this routine will enter a infinite loop when the searched text is not found in the tree-view, because it relies on _GUICtrlTreeView_GetNext to return zero when called for the last item. (Thus prio Major) #include <GuiConstantsEx.au3> #include <GuiTreeView.au3> #include <GuiImageList.au3> Opt('MustDeclareVars', 1) Example_External() Func Example_External() Local $GUI, $hItem[10], $hTreeView Local $iStyle = BitOR($TVS_EDITLABELS, $TVS_HASBUTTONS, $TVS_HASLINES, $TVS_LINESATROOT, $TVS_DISABLEDRAGDROP, $TVS_SHOWSELALWAYS ) $GUI = GUICreate("(External) TreeView Get Next", 400, 300) $hTreeView = _GUICtrlTreeView_Create ($GUI, 2, 2, 396, 268, $iStyle, $WS_EX_CLIENTEDGE) GUISetState() _GUICtrlTreeView_BeginUpdate ($hTreeView) For $x = 0 To 5 $hItem[$x] = _GUICtrlTreeView_Add ($hTreeView, 0, StringFormat("[%02d] New Item", $x + 1), $iImage, $iImage) Next _GUICtrlTreeView_EndUpdate ($hTreeView) If _GUICtrlTreeView_GetNext( $hTreeView, $hItem[5] ) <> 0 Then MsgBox(4160, "Information", "_GUICtrlTreeView_GetNext does not return 0 when called with last item" ) EndIf ; Loop until user exits Do Until GUIGetMsg() = $GUI_EVENT_CLOSE GUIDelete() EndFunc ;==>Example_External |
|||
#33 | squirrely1 | No Bug | _IsNumber() & IsInt() both incorrectly return true | |
Description |
XP SP2 EN x86 MsgBox(0,"Testing IsInt()",IsInt(Number("K")) & " - Should be: 0") MsgBox(0,"Testing IsNumber()",IsNumber(Number("K")) & " - Should be: 0") |
|||
#34 | Jon | stevy80@… | Works For Me | Pixelchecksum returns wrong values |
Description |
Hello, I developed an application with visual c# under windows xp. This program uses autoitx3.dll. Everything worked fine until I upgraded the system. With the new cpu (64 bit) - still under xp - the pixelchecksum function (aprox. in the half of the cases) returns wrong values (-2147483648). After this, I tried the program on two more machines with Intel P4 cpu, and the results was the same. I tested the checksum at these machines with autoit main too, and that worked perfectly. So I think the problem is in autoitx. |