|
Post by dragonjim on Feb 20, 2018 1:10:48 GMT 1
Sorry, missed this post.
No, it is not just you. Advice generally (and not just with regards to GFABASIC) is to use Double variables only when necessary; if possible, use Single instead.
This also relates to comparing non-integer return values from GFA functions: many of them return a Single value which does not compare well with a Double (and, remember, all non-integer 'magic' numbers in GFA are treated as Doubles) and DllVersion is a good example of this:
If DllVersion > 2.31 Then ... ...sometimes works and, when mainly when compiled, sometimes does not. To get round this, convert the magic number (2.31) into a Single as follows:
If DllVersion > 2.31! Then ...
|
|
|
Post by infoliner on Feb 23, 2018 19:50:08 GMT 1
Try to use "Near" instead of "=",
? = x NEAR y
See help for it, it might help. I never use floating point variables, I always make them integer.
|
|