BUG? : $BS_DEFPUSHBUTTON + GUICtrlSetBkColor

[mLipok]

REPRO:

expandcollapse popup

#include <GUIConstantsEx.au3>
#include <ButtonConstants.au3>
#include <EditConstants.au3>
_TEST()

Func _TEST()
    ; GUI START
    Local $hWND = GUICreate("TEST GUI", 624, 461, 252, 103)
    Local $idInput = GUICtrlCreateInput("", 160, 24, 201, 25)

    Local $idButton_TEST1 = GUICtrlCreateButton("TEST1", 384, 24, 91, 25, $BS_DEFPUSHBUTTON)
    Local $idButton_TEST2 = GUICtrlCreateButton("TEST2", 480, 25, 100, 25)
    GUICtrlSetBkColor(-1, 0x00FFFF)

    GUISetState()
    ; GUI END

    Local $aMsg, $nMsg, $sTemp
    While 1
        $aMsg = GUIGetMsg(1)
        If UBound($aMsg) And $aMsg[1] = $hWND Then
            $nMsg = $aMsg[0]
            If $nMsg Then
                Switch $nMsg
                    Case $GUI_EVENT_CLOSE
                        ExitLoop
                    Case $idInput
                    Case $idButton_TEST1
                        $sTemp = GUICtrlRead($idInput)
                        MsgBox(0, 'TEST1 Button Pushed', $sTemp)
                        GUICtrlSetState($idInput, $GUI_FOCUS)
                    Case $idButton_TEST2
                        MsgBox(0, 'TEST2 Button Pushed', $sTemp)
                        GUICtrlSetState($idInput, $GUI_FOCUS)
                EndSwitch
            EndIf
        EndIf
    WEnd
    GUIDelete($hWND)

EndFunc   ;==>_TEST2Documents

HOWTO: 

1. type some text in $idInput
2. now click $idButton_TEST1 - is ok
3. change text in $idInput
4. press ENTER in $idInput - $idButton_TEST1 is used/fired
5. now click $idButton_TEST2 - is ok
6. change text in $idInput
7. press ENTER in $idInput - $idButton_TEST2 is used/fired

Question:

Why in step #7    $idButton_TEST2 is used/fired

Remarks:

This is not happend when you comment this line:

GUICtrlSetBkColor(-1, 0x00FFFF)

EDIT:

$idButton_TEST1 is loses $BS_DEFPUSHBUTTON property when $idButton_TEST2 is clicked.

Edited September 16, 2014 by mLipok

[JohnOne]

Because of a bug in autoit, the one M23 mentioned the other day.

[mLipok]

As I understand this bug is already known (something reminds me that there have been problems with the colors of the buttons).

So far, I see that it is not in the open Tickets (or poorly I was looking for)?

Any chance of fixing it?

[JohnOne]

I'm a bit busy at the moment, maybe later

[JohnOne]

If I recall, the bug is not on the agenda, something to do with the AutoIt bowl depth of where it occurs, but a workaround is available. but don't know where.

Edited September 16, 2014 by JohnOne

[AdmiralAlkex]

As I understand this bug is already known (something reminds me that there have been problems with the colors of the buttons).

So far, I see that it is not in the open Tickets (or poorly I was looking for)?

Any chance of fixing it?

 

The developers have stated multiple times throughout the years that custom colors are evil and probably shouldn't have ever been created.

 

#376

 

I'm just going to set this as won't fix. I do not agree with any way to fix this short of writing the GUI from scratch and not even including custom colors (it should have never been built-in in the first place).

[mLipok]

Ok thanks for your time.
I will look for find an workaround solution.

Cheers

mLipok