PureBasic Forums - English

I have the full version

But I use Linux. Maybe GetAsyncKeyState_() refers to Win API?

Thanks for sharing. This is a nice example.

Only one minor issue I noticed: The following function does not work and I cannot find it in the documentation: GetAsyncKeyState_

If the conditional is commented out, the application compiles.

Voilà!

PureBasic AppTainer Helper (PAT) v1.0.0 (Beta) - compile for multiple Linux distros in seconds

https://i.postimg.cc/FKVtKxDg/PATv100-screenshot.png

What is PureBasic AppTainer Helper (PAT)?

I've uploaded the .def files including a helper script called "PAT" to allow compiling ...

Sure, on a very high level, the process is:

1. Download and install AppTainer from the AppTainer site (I couldn't find it in apt)
2. Create a ".def" file for each Linux distro to compile for. This is the tricky part, since the .def file is a script that defines all the packages that need to be ...

After a lot of experimentation, it seems that AppTainer indeed is very efficient way to compile on Linux without using VMs. I have tested some simple compiled apps in a couple of VMs of older distros, and they work as intended, both GUI, console and C backend executables.

I can now compile my PB ...

As an alternative to VMs you could try keeping a number of relevant Linux versions, with appropriate PureBasic installs, on bootable USB memory sticks with save persistence.

Thanks. I might try that out.

Meanwhile, I think I managed to get AppTainer working - kind of. I installed PB 6.04 and ...

I understand that the "best practice" for ensuring broad compatibility on Linux machines is to compile on the lowest Linux distro that still allows your application to compile and run. But what do you recommend in terms of...

- Method : Virtual machines, Docker, Apptainer, maybe something else ...

Thanks, your last hint seems to work!

See the adjusted code below. It's tested only on my Linux PC, but with the compiler directive, it hopefully also works on Windows. In short, my app now launches the terminal, which in turn relaunches the app inside itself. The behaviour is the same in the ...

Thanks for the suggestion. The logger confirms that the executable is launching, but I am not able to try the Windows code snippet.

I can still only run my console app via the terminal, and not by double-clicking it. I wonder if there is some Linux limitation here.

Here's one short console ...

I've created a small console program and it runs just fine, if I compile it and run it from CLI/terminal.

However, nothing happens if try to double-click it to launch it. Does anyone know why the console program won't launch in its own window?

I don't think it is quitting silently, because the ...

Thanks! I used the solution that you provided here: https://www.purebasic.fr/english/viewtopic.php?t=83435

In case anyone else finds this, what I did to implement this was:

1. Put the bash (.sh) script in a folder next to the PB CHM help file that I got from the Windows PB Installer
2. Change the ...

Hi,

I was wondering if anyone has a clever trick that allows using the .chm version of the help file instead of the standard Linux help file from the form designer?

I find the CHM help format slightly more convenient to work with, even if I have to extract it from a Windows install first to ...

I agree. It seems somewhat buggy, or at least it's not optimal UX design, if the setting risks breaking auto-generated form event procedures.

It would seem more logical to me, if that setting in Preferences only decides whether the default state in the form designer would be enabled event ...

Thanks for your answer.

After some more testing, I think this maybe works alright. If I understand the "Generate event procedures" setting in Preferences (not the similarly named setting in the form designer) it actually works as follows:

1. If enabled in Preferences -> An event procedure will be ...

Hi,

I was wondering if the following is the intended behaviour of the PureBasic form designer?:

If I disable "Generate event procedure" in File -> Preferences -> Form, this seems to also delete the an existing event procedure in the form that is currently being edited, even though this form ...