PureBasic Forums - English

Is there any plan to update SDL to the latest version in the 5.40 final ?

What is the reason for the removal of RemovePackFile() and PackEntrySize() with #PB_Packer_CompressedSize? Do we have to copy files over to a new pack file in order to remove some? Thanks.

It was already the case before, there was no inplace removefile.

Hello.
It seems that the Variable Viewer on the x86 environment does not show the global variables.
It shows the global arrays, linked lists and maps normally.
Regards.

Thanos

If you don't need performances, you can use an image and then draw it on your sprite/texture, it should do the job.

Alexi wrote:then i'll kiss the hole team!

The hole team or the whole team ? Let me choose...

Fred wrote:If you don't need performances, you can use an image and then draw it on your sprite/texture, it should do the job.

And if you need performance? Does the VectorDrawing lib use (slow) GDI+ on all supported versions of Windows, or is it able to detect
the Windows version at runtime and use more modern (hardware-accelerated) API's like Direct2D and DirectWrite, for example?

(If not, could that be changed? GDI+ is already listed as 'Legacy Graphics' - it's too old and slow)

I wouldn't read too much into the word 'legacy'. It applies because the technology has been in Windows for a long time now but I wouldn't call the performance of GDI+ 'slow'.

netmaestro wrote:I wouldn't read too much into the word 'legacy'. It applies because the technology has been in Windows for a long time now

It means the listed technologies are not developed any further. It is what it is, and as a software graphics engine
it will probably work for some years. It does not depend on DX etc., so no changes are required for new Windows versions.
Just like GDI - it's still there.

netmaestro wrote:but I wouldn't call the performance of GDI+ 'slow'.

Check out some .NET WPF toolkits with animated GUI controls (animated Charts, Gauges and such stuff).
Performance of GDI+ is bad the bigger the Canvas is. With a very big or even fullscreen Canvas performance
gets very slow (displays/monitors get also bigger, 4k etc.). When using Matrix transformations (rotation etc.)
it's much slower with a software renderer.

Anyway, it was just an idea. Why not add a Direct2D/DirectWrite layer if it's possible and available at runtime?
If not, the fallback GDI+ is used. With that, VistaSP2/Win7/Win8.x/Win10 users could get some enhancement,
while the app still works using GDI+ for the XP guys. Same could probably be done for the 2DDrawing lib and
ImageOutput/WindowOutput, to speed things up.
Everthing MS did in the last 10 years (WPF, Metro/ModernUI etc.) is using hardware-accelerated GUIs.
Scintilla has also a mode to use Direct2D/DirectWrite.

The focus of the VectorDrawing library for this release was functionality and cross-platform compatibility. I.e. to get something that works well on all platforms. Performance was not my primary concern.

We'll see what improvements can be made in the future.

That is a damn good work nonetheless ! Fixes many problems at once (AA, resolution, area drawing, texts...), thank you !

freak wrote:The focus of the VectorDrawing library for this release was functionality and cross-platform compatibility. I.e. to get something that works well on all platforms. Performance was not my primary concern.

We'll see what improvements can be made in the future.

Thank you!

Is that new vector library fast enough for games? Or only to create static images?

the animated vector drawing http://purebasic.fr/english/viewtopic.p ... 52#p472019
posted by eddy and edited in 22 sept (not like the picture) is a show case for a possible usage in 2D games. thanks i have visited the page again. should be added to the official examples.

thanos wrote:Hello.
It seems that the Variable Viewer on the x86 environment does not show the global variables.
It shows the global arrays, linked lists and maps normally.
Regards.

Thanos

Did anyone else faced this problem?