PureBasic Forums - English

The main event loop should be able to handle both windows.

If you don't require any window-specific control, this would suffice:


Win1 = OpenWindow(#PB_Any, 300, 300, 300, 150, "Main Window", #PB_Window_SystemMenu)
Win1Text = TextGadget(#PB_Any, 20, 50, 260, 30, "Elapsed: 0 sec")
AddWindowTimer ...

MikeGreen99 wrote: Mon Dec 08, 2025 10:05 pm I got it working . After modding .bashrc I forgot to boot.

Perfect, then. Linux configurations can prove to be a little slippery, sometimes.

If you may require any further clarifications, as you come to grasps with the intricacies of PureBasic, we're always here.

MikeGreen99 wrote: Sun Dec 07, 2025 9:53 pmHow do I set the 'PUREBASIC_HOME' env variable ?

It depends on the Linux distro, but you'd usually have to export the variable in the profile or bashrc file. And preferably add PureBasic to the path variable as well.

The FormDesigner forced the name of my Form to Window_0 . Can I change this ? What if I had multiple .pbf Forms, would they all use Window_0 ? How would the Main Program distinguish one .pbf Form from another ?


Simply change the variable name of the window in the properties window of the form ...

I was expecting a sort of "symmetry" where all the drag and drop events would be at the same level in my event loop code. But since #PB_Event_GadgetDrop is a window event and #PB_EventType_DragStart is a gadget event, they aren't.


So, your question is, why not just add a corresponding drop event ...

If I add:

OpenTestForm01()

to the form "FormTest01.pbf", I will lose this line as the Form Code is continually being regenerated.



We shouldn't add anything to the form code files. They are automatically-generated files and will continue to regenerate as the form is edited, purging all ...

For constants, FormDesigner uses Named Enumeration. For different form files, you also have to use different names for constants and variables to avoid conflicts.

For large multi-codebase projects, even named enumerations could pose a problem if the various enumerator labels don't align. And with ...

...disable the #PB_Any setting in FormDesigner. I think it's better to use constants with enumerations for the GUI instead of lots of variables.

I'm sure that coding styles are personal choices, but PureBasic's humble #PB_Any directive hides a very powerful dynamic object numbering system, which ...

... These were not my mistakes, but from snippets by others in these forums. ...

Forum snippets are usually quick & dirty examples to simply illustrate core concepts of the questions being asked.

Even when lifted from the tips & tricks section, they are usually generic, abridged versions lacking ...

...if disabling "Generate event procedure" also makes changes to already made forms, it would be difficult to have different projects that use different event handling methods...

I would believe that this is a somewhat buggy behaviour , because as you said, it could break projects that were ...

...the first portion of my program which dies on line 4


If OpenTestForm01() exists and is a valid window procedure in your form file, and the form file is in the same folder as your executable, this should work:
#ProgramTitle = "TestForm01.pb"
#ProgramVersion = "v1.00.0 MG"
XIncludeFile ...

Could CountString get the same Mode parameter as FindString please?
#PB_String_CaseSensitive: case sensitive search (a=a) (default).
#PB_String_NoCase : case insensitive search (A=a).

I currently have to have two copies of a string around for counting, original case and lower case.




In ...

AZJIO wrote: Sun Nov 30, 2025 7:42 amWhy is there such a difference?

Although they all implement the common Linux kernel, each distro is compiled differently, and with different dependencies as well.

So, the toolchains, build configs, graphic systems, etc, would work differently.

Love it or hate it, it's here to stay. So, may as well get used to it.

It's ELIZA, forty years in the making. :lol:

But seriously, it's a machine, albeit with a plethora of ethical and real-world ramifications. Sentience may not be possible, but what is it, anyway?

Meanwhile, let's just enjoy ...

Hello again, @Jan2004.

As most have highlighted, multiple calls to the WaitWindowEvent() function is not recommended. Even if your modal windows are in separate code files, they will be integrated into the calling code and should thus merge with its main event loop.

Alternatively, the binding ...