Ok, been pulling my hair out for last 4 hours until I realized what was going on.

I have a TYPE with 3 integers and a string:

TYPE MYTYPE
    INT1 AS INTEGER
    INT2 AS INTEGER
    INT3 AS INTEGER
    INFO AS STRING
END TYPE

Then used it as so:

REDIM MYVARIABLE(1) AS MYTYPE

So far so good. As I start putting data into the array I need to resize it from time to time:

REDIM _PRESERVE MYVARIABLE(UBOUND(MYVARIABLE) + 1) AS MYTYPE

Still good right? Nope. The previous data gets completely garbled. The problem you ask?

INFO AS STRING

Change it to:

INFO AS STRING * 20

and all is good in QB64 land.

It seems variable length strings are a no-no when using REDIM _PRESERVE

If this is already a known issue then somehow I have missed it all these years. If it isn't then this is a warning letting others know this happens.

I was ready to throw my joystick through my screen until it finally dawned on me as to what may have been happening. The integers I was storing ranged from 1 to 6 but somehow they were changing to 16, 57, 3471, etc.. I thought maybe I was going nuts for a while, LOL.

Ugh.

Not strictly connected to QBJS, BAM or other BASICs, but seems the best place to point you to another stunning Web-based application, especially for the graphicans among us.

DPaint.js is inspired by the legendary Commodore Amiga Program "DeluxePaint". Just select "Documentation" from the "Help" menu, there you find some feature highlights and a introduction video.

CONST QB64 = QB64pe

Hi QB64 coders
QB64 developers
QB64 members of community

in what  manner do you manage modern input  mouse like touchpad of notebook?
Today new notebooks have customized input from touchpad with 2 or 3 or 4 fingers on it ....
how to catch and manage these new mouse input?
Where do you find and use the code for managing these modern mouse input?
In the old '80-'90 it was the new frontier managing mouse input (see call interrupt &H33, call absolute with binary code into an array), today the input with multiple fingers from a touchpad or another kind of input device is the new frontier.
I have get no good search result on stackoverflow.

Thanks for feedback boys and girls of QB64pe

I am confused. What is the compiler trying to do?

I try to pass a parameter of type INT or Float and it keeps telling me that the conversion from type INT* to INT and from Float to Float* cannot be performed - what does this mean? Here is a sample code to QB64PE and below that the contents of the H file. It should be fine (but it would have to work) - what did I do wrong?

QB64 code:

Starting a thread here to post fun facts about QBJS that you might not know.

Fun Fact #1 - You can define optional parameters!

Is there a (simple) way to increase font- size during programme execution when using the _rgb32 screen? If not, could this be made possible?

I have an older program that used to run fine but now exits unexpectedly in 3.6.0 without any message.

Below a snippet of what I pinned down the error to: (r$ = Mid$(arr$(i&), 80, 20) in processArr&)

Anyone know of commands in QB64 that:

1) Reads the number of available cores "cores"
2) Assigns or allocates an X number of cores to a program?

Regards - dsip

Not sure where a good place to suggest ideas for improving QB64's IDE so I am dropping it here. I'd be happy to do it right next time, if this isn't, if someone kindly points me to the right place.

Anyways, my idea is having a way to mark functions and subs in the SUBs menu (you know the one you get with F2). Be useful to mark complete, in-progress, or place holder and sort by such a flag. Just my two cents.

Have a lovely day or evening wherever you may be