MessageRequester constants

[mestnyi]

now it's the other way around, it works fine on Mac and Linux, but on Windows it gets mixed up.

Code: Select all

;\\                                       ; win ; mac & lin
; Debug #PB_MessageRequester_YesNoCancel  ; 3   ; 2
; Debug #PB_MessageRequester_YesNo        ; 4   ; 1
; Debug #PB_MessageRequester_Yes          ; 6   ; 6
; Debug #PB_MessageRequester_Error        ; 16  ; 8
; Debug #PB_MessageRequester_Warning      ; 48  ; 16
; Debug #PB_MessageRequester_Info         ; 64  ; 4
; 
; Debug ""
; Debug #PB_MessageRequester_Ok           ; 0   ; 0
; Debug #PB_MessageRequester_Cancel       ; 2   ; 2
; Debug #PB_MessageRequester_No           ; 7   ; 7
; 

Define Flag.q = #PB_MessageRequester_YesNoCancel|#PB_MessageRequester_Warning

If Flag & #PB_MessageRequester_Info
   Debug "#PB_MessageRequester_Info"
EndIf

If Flag & #PB_MessageRequester_Error
   Debug "#PB_MessageRequester_Error"
EndIf

If Flag & #PB_MessageRequester_Warning
   Debug "#PB_MessageRequester_Warning"
EndIf

[spikey]

The values are not entirely bit-based. You can't do things like 'and mask' on them properly. Specifically, on Windows, #PB_MessageRequester_Warning has a two significant bit value not a single bit value and there is an overlap.

Code: Select all

Debug RSet(Bin(#PB_MessageRequester_Info), 8, "0")
Debug RSet(Bin(#PB_MessageRequester_Warning), 8, "0")
Debug RSet(Bin(#PB_MessageRequester_Error), 8, "0")

These values aren't intended to hang around to provide persistent state information. They're intended for transient and disposable dialogs.

(#PB_MessageRequester_Yes is an output value not an input one.)

[mestnyi]

Specifically, on Windows, #PB_MessageRequester_Warning has a two significant bit value not a single bit value and there is an overlap.

exactly why is this so?

These values aren't intended to hang around to provide persistent state information. They're intended for transient and disposable dialogs.

https://www.purebasic.com/documentation ... ester.html
look at what is written in the help.

(#PB_MessageRequester_Yes is an output value not an input one.)

[spikey]

Exactly why is this so?

The values are inherited directly from the Windows API header files, because they will end up back in an API function at runtime. I assume that a similar rationale applies to the other operating systems too and this is where the slight variations creep in. They are just 'redecorated' in PureBasic format to present a consistent look for PB programmers in the source code. In this case the header is WinUser.h on Windows.

[mk-soft]

Only Windows ...

Code: Select all

Debug #PB_MessageRequester_Ok
Debug #MB_OK

Debug #PB_MessageRequester_YesNo
Debug #MB_YESNO

Debug #PB_MessageRequester_YesNoCancel
Debug #MB_YESNOCANCEL

r1 = MessageRequester("Only Windows", "Ok/Cancel", #MB_OKCANCEL)
Debug r1
Select r1
  Case #IDOK
    Debug "OK"
  Case #IDCANCEL
    Debug "Cancel"
EndSelect

r1 = MessageRequester("Only Windows", "Retry/Cancel", #MB_RETRYCANCEL)
Debug r1
Select r1
  Case #IDRETRY
    Debug "Retry"
  Case #IDCANCEL
    Debug "Cancel"
EndSelect