PureBasic Forums - English

Just a shot into the blue: The last entry of the help touching this is from 2012 and lists OGRE 1.82. Also the OGREs copyright text in the help is from 2012. If nobody forgot to update these, it should be 1.82.

RASHAD wrote: ↑Thu Apr 18, 2024 10:44 pm Hi jacdelad
Is that mean he should pay me $20 per month

$20 well invested. I'll think about that.

dige wrote: ↑Thu Apr 18, 2024 7:19 pm Nevertheless, thanks RASHAD, it looks better

You can always trust in RASHAD-GPT!

Thanks Fred...
...today a nightshift without work...so, a nightshift to code!

Try PackMemory() several times and validate whether the result varies in size.

Seriously? Is this the "someone asks this every day"-topic now? This is getting boring...

I am actually wondering how and why white spaces should affect the execution speed at all. I could imagine that compiling takes nuances longer, but then? Isn't the out the same, regardless of how many white spaces I put there?

...which is not a bug, but a request.

This is a terrible idea and also not possible. PureBasic has no power over which address is returned if an object (like a library) is assigned. That's why the help clearly states to use .i for handles. This is also fact for every programming language which uses x86-/x64-architecture. The simple fact...

Oh nice. Thanks!!!!!

I meant calculate it fast than accurate, my fault. But seriously, what do you mean by "accurate"?

What do you mean by accurate? It's more important to calculate 2+2 than to return the right result??
?

These two lines of code capture the mouse position that will be used to draw back to the origin (x,y). The division and multiplication is used to round off to the nearest 8 pixels (pw,ph). The code that calls this procedure is much to extensive to post. I would have never guessed that without conte...

1. Please use code tags. 2. Please post a runable code. We can't know whether the problem is within this procedure or the code around it. 3. What do you expect x1 = (GetGadgetAttribute(Canvas_0, #PB_Canvas_MouseX) / pw) * pw y1 = (GetGadgetAttribute(Canvas_0, #PB_Canvas_MouseY) / ph) * ph to do??? E...

It did occur for me too, but vanished after using a full path.