Let it be obvious that I disagree with *fxm* and any of the associated statements .... He (she ?) seems to misinterpet too many things at a once (in a livetime) sort of way ... Meaning (clear and straight): I want an explicit apology ... (where I stands for the community at large) (just reverting th...

The only certain expectation is as described in FB-Manual/Operator precedence.

fxm wrote:UShort or ULong or ..... for WStrings, depending on platform! <-- metioned already!
The keyword manual should be the reference for the language.

We agree on that but only as long as that doesn't make it "incomprehensible" for most.

I prefer mine which is more compact and precise IMHO. I definitely don't: its more compact (yes) but far less simple to understand. This is, what should have TOP PRIORITY. Secondly, users must like it (not you or me). in its first form: A UByte containing the ASCII value of a string-character (byre...

Maybe it would be better like this? Returns a numeric reference to a character value in a string Anyway, if it's the term 'reference' that bothers you, we can't escape it because it's the appropriate term! I beg to differ, how it is returned is only a secondary priority. Ordinary users want to know...

Seems you don't want to understand the difference between a Assembler (TASM/FASM ...) and FBC's inline ASM ...

Its not wrong "what I've written", as you've just confirmed. Thanks.

Assuming that the return value of your function is DWORD sized, this one works : I think it's vice versa: stating the size of the 0 value: Asm mov [function], DWord Ptr[0] Since the size of [function] is known (typically EAX or RAX, aka: register size). Depends on bitness of FBC used (32 - DWord, 6...

For 32-bit colors I would NOT use Enum (result is: Integer) but rather ULong Const 's. Example below: Const As ULong red = &hFFCF0000, orange = &hFF7F7F00, _ yellow = &hFFFFDF00, green = &hFF00CF3F, _ cyan = &hFF00CFCF, blue = &hFF003FCF, _ purple = &hFFCF00CF, black = &a...

@BasicCoder2, back to "old habits" so soon? Below: removed not really needed Const (NULL) removed all "shared" stuff (using local variables instead) dynamic array (instead of limited, static size) Sub converted to Function (returns image ptr) added some checks (no BMP found ...) ...

@fxm, have you tried to force -mt in compilation?

Properties are of limitted value in such cases (only ever a single value handled). They can be substituted with one's own handlers, like below example: ' This code works Type MyObject Public: declare Sub SetO(ByVal Val_x as UInteger, ByVal Val_y as UInteger) declare Function GetO(ByVal mode As ULong...

Using outdated manuals / compilers results almost always in some or other problem. Don't blame others if you are not keeping things updated (1.05.0 is pretty old by now). Programmers Manual: Passing Arrays to Procedures (online/up to date) Forum Search (advanced): - Query: +Passing +Array - Option: ...

Flyzone wrote:I'm here to report a BUG

It's not a bug.
After a simple Sleep you'll have to clear the keyboard buffer, if you want to assure it's "empty".
While InKey <> ""
Wend

Indeed, a very insightful comment, as expected.