PureBasic Forums - English

Hello again,

Sorry for the delay, took some time to trim/narrow the code.

I could simplfy it further but wanted to maintain both dialogs logic well separated.


With Gtk subsystem, everything is as expected : child window opens as modal, with parent window disabled.
With Qt subsystem, both ...

Please always post a small snippet showing the issue, thanks !


EDIT : For some reason, if the dialog loses focus and is brought back into focus, the layout works... until you resize the Gtk dialog again.

Sorry, here is a simple code that shows the difference between Gtk & QT subsystems ...

Resizing a Gtk dialog using a vertical Splitter as its main element, and containing boxes will mess the layout when resizing.
Works as expected with the Qt subsystem.

DIsableWindow() works as expected using Gtk dialogs, but will disable both parent/child dialogs using the Qt subsystem (at least on the project I am working on).

And how do you test and debug your code :?:


The exact same way I test/debug code with current Purebasic : the code is written/tested on main computer used as main dev environment which for me is Linux only. Cross compilation is to then have binaries/packages automatically generated for multiple ...

With pbcompilerc using gcc as a backend, and most linux distributions having gcc cross compilers available, allowing to chose the target gcc would make for easy cross compilations, and almost transparent compiling to currently not supported OS/architecture provided they have Gtk/Qt (I am thinking of ...

Thanks all!

As I am looking for an OS agnostic solution, it looks like using a trace file is the way to go for now (unless I find an equivalent to outputdebugstring() in linux).

Hi all!

I have a main executable (coded in PB) accessing a dll library (also coded in PB).
In windows, it looks like the -d compiler argument does nothing when the /DLL (or linux/macos equivalent) argument is used.

Does PB give the possibility to debug a loaded library (for example by opening a ...

PUREBASIC_HOME must be set in order to call pbcompiler or pbcompilerc from the command line (forgot to do that).

Thanks for the help

Hi there

"~/purebasic/compiler" is in my $PATH (I can call pbcompiler and pbcompilerc from any directory), and I do manage to compile projects directly from the PB ide.

But, if I use
pbcompiler main.pb -o ../bin/myproject -t -z -pf -dc
I get the following return :
PureBasic 6.04 LTS (Linux ...

I am investigating if it is possible to cross-compile Purebasic C output using a gcc/ld cross compiler (on linux x86_64).
I am using gcc and ld for the target architecture.

First step is extracting/getting the C code:
pbcompilerc -c ./main.pb
Gives me a purebasic.c file.

Then compiling the code ...

Joris wrote: Wed Mar 30, 2022 8:08 am Was BeOs not completely programmed in assembler ? Haiky turns out to be more of a C language, doesn't it?

Only the kernel is C and assembly. All the API is C++, a well designed one but very object oriented making interfacing with C languages difficult

Haiku uses a (by a quick look of it, nice) C++ framework for their OS API. PB does not play nicely with a C++ based API. It would need C bindings for everything which messes up the nice Haiku object model. Or something like dynamic object calling. Think CocoaMessage (that one sends ObjectiveC ...

I do! I discovered BeOS with this floppy disk (I think I got it buying a magazine).

A few weeks later I bought another magazine, this time with the Personal Edition CD. You could install BeOS directly from within Windows 95/98 if I remember well. Having started computing at the Atari/Amiga ...

Same here, old BeOS Personnal Edition user. At the time BeOS was so ahead of other operating systems!
Haiku has gone a long way in modernizing BeOS.

With the C back-en now available for PB, and Qt being available on Haiku, using the Linux Qt PB as a base could make porting PB to Haiku relatively ...