TonyDuBass

when I used the ternary operator, was only seeking a better aesthetics to the code. Because prior to version 3.3.10.0, the ternary could simply be written as: "(1 exp exp 2: exp 3)" ... Now I have to write the same code assigning the value to a variable.

Really thanks to your help, kylomas. By the end I used your second suggestion, to don't turn off the syntax check. Generally I use the portable version of AutoIt and is an older version. I'm not used to this way of using the ternary operator. Although I have used the ternary like if...else, the ternary has a faster response than if...else. But I think I ended up using the ternary in this case just to satisfy my self.

I'm not having the same luck. In the old version worked like this: (($WinPos[0] + $WinPos[2]) > @DesktopWidth _ Or $WinPos[0] < 0 _ Or $WinPos[1] < 0 _ Or ($WinPos[1] + $WinPos[3]) > (@DesktopHeight - (@DesktopHeight * 0.085))) _ And Not BitAND(WinGetState($hWindow), 32) ? _ WinMove($hWindow, Default, (@DesktopWidth/2) - (658/2), (@DesktopHeight/2) - (440/2), 658, 440, 1) I tried to use the parenthesis but I can not work in the new version writing the code below: (((($WinPos[0] + $WinPos[2]) > @DesktopWidth _ Or $WinPos[0] < 0 _ Or $WinPos[1] < 0 _ Or ($WinPos[1] + $WinPos[3]) > (@DesktopHeight - (@DesktopHeight * 0.085))) _ ;(@DesktopHeight * 0.085) é a largura do menu iniciar. And Not BitAND(WinGetState($hWindow), 32)) ? _ WinMove($hWindow, Default, (@DesktopWidth/2) - (658/2), (@DesktopHeight/2) - (440/2), 658, 440, 1) : "")