Value of constants

[mestnyi]

Aren't these bit constants?

Code: Select all

Debug #PB_Button_Toggle ; return 4099 not 4096
Debug #PB_ComboBox_Editable ; return 66 not 64

[STARGÅTE]

Aren't these bit constants?

Code: Select all

Debug #PB_Button_Toggle ; return 4099 not 4096
Debug #PB_ComboBox_Editable ; return 66 not 64

Why should they have only one set bit? Probably these constants are itself combinations of multiple OS specific constants.

[BarryG]

Constants starting with "#PB_" are custom-made for PureBasic and can be any value decided by Fred. They don't always correspond to an existing API constant, and nor should they.

[mestnyi]

that's right, but I remember that there were problems with the combobox.
maybe it was because of him that there were problems, maybe there was a typo

[Fred]

BarryG is right, you should never rely on the constant value as it can change anytime between releases.

[BarryG]

Fred, on this subject... I've always meant to report that there are no constants for the return value of FileSize()... should there be? Can you add some? Thanks.

[Fred]

It would be better indeed.

[Axolotl]

Yes, I would support that.
BTW: I use this for a (very) long time now!? Just a cautious suggestion.

Code: Select all

;/
;| FileSize() results as constants 
;\
#PB_FileSize_Empty     =  0    
#PB_FileSize_Missing   = -1   
#PB_FileSize_Directory = -2 

[Quin]

Yes, I would support that.
BTW: I use this for a (very) long time now!? Just a cautious suggestion.

Code: Select all

;/
;| FileSize() results as constants 
;\
#PB_FileSize_Empty     =  0    
#PB_FileSize_Missing   = -1   
#PB_FileSize_Directory = -2 

Something like this would be absolutely amazing, for the first three years of me using PB I had to go check what the return value was for missing file vs directory every time I wanted to use this function

[mestnyi]

BarryG is right, you should never rely on the constant value as it can change anytime between releases.

I agree with you, but I'm working on a GUI to replace the standard one for all three axes, and it was almost ready until my hard drive burned down, I had to rewrite it again, so I'm directly connected with both hands.
I just saw a lot of potential in purebasic, its syntax has sunk into my soul, but the graphical interface kills with its limitations.

So it's not a typo, is that what Fred intended?

[Fred]

Yes

[BarryG]

.

[Little John]

Something like this would be absolutely amazing, for the first three years of me using PB I had to go check what the return value was for missing file vs directory every time I wanted to use this function

You can use Macros:

Code: Select all

Macro ExistFile (_entry_)
   Bool(FileSize(_entry_) > -1)
EndMacro

Macro ExistDirectory (_entry_)
   Bool(FileSize(_entry_) = -2)
EndMacro

[Demivec]

Something like this would be absolutely amazing, for the first three years of me using PB I had to go check what the return value was for missing file vs directory every time I wanted to use this function

You can use Macros:

Code: Select all

Macro ExistFile (_entry_)
   Bool(FileSize(_entry_) > -1)
EndMacro

Macro ExistDirectory (_entry_)
   Bool(FileSize(_entry_) = -2)
EndMacro

Or using the proposed constants:

Code: Select all

Macro ExistFile (_entry_)
   Bool(FileSize(_entry_) >= #PB_FileSize_Empty)
EndMacro

Macro ExistDirectory (_entry_)
   Bool(FileSize(_entry_) = #PB_FileSize_Directory)
EndMacro