PureBasic Forums - English

Mindphazer wrote: ↑Fri Apr 19, 2024 2:12 pm

Piero wrote: ↑Fri Apr 19, 2024 1:56 pm What confused me is that it's normally very easy:

Code: Select all

Until event = #PB_Event_CloseWindow or EventMenu() = #PB_Menu_Quit

It works if you click on "Quit", but you wanted to catch the ⌘Q shortcut

That is wrong. EventMenu() may only be queried if there is also an event #PB_Event_Menu.

If no valid data is received (never [STX]text[ETX]) you can kick out the client. CloseNerkConnection

Not testet ... ... CompilerIf #PB_Compiler_OS = #PB_OS_MacOS Procedure MacOS_Quit() PostEvent(#PB_Event_CloseWindow, 0, 0) EndProcedure CompilerEndIf If OpenWindow(0, 100, 200, 500, 300, "PureBasic MiniBrowser v1.0", #PB_Window_MinimizeGadget | #PB_Window_MaximizeGadget | #PB_Window_SizeGa...

maybe ... #EnableSQLite = #False CompilerIf #EnableSQLite #UseSQLiteDatabase = #True If Not UseSQLiteDatabase() Debug "Error ..." End EndIf CompilerEndIf Enumeration _own_db_format #OWN_DB_FORMAT_INMEMORY #OWN_DB_FORMAT_OWN #OWN_DB_FORMAT_XML #OWN_DB_FORMAT_JSON CompilerIf Defined(UseSQLit...

Actually, it's fine the way it was before. I don't see any problem here whether you write "mystruct\a = 2" or "mystruct\a[0] = 2".
Forbidding too much is not good either.

It is always better to take a structure and create it for the entire runtime of the thread with AllocateStructure.

Caronte3D wrote: ↑Thu Apr 18, 2024 8:53 am I don't know if relevant, but is better not use KillThread() to terminate threads, much better to do some break inside so the thread ends it self.
At least, for me, the KillThread is delicate

KillThread is only called if WaitThread was not successful after time

You have programmed yourself a memory leak when rewriting thUDPServer. Client()\text is no longer corrected. In addition, you have removed the Repeat Until, which means that the data in the receive buffer can no longer be separated. There may be several sent data in the receive buffer that need to b...

Oops,
some codes will no longer work.
So please remove this adjustment.

At this point I would like to give an important note for both proposed solutions. In both cases the information is passed just as a reference to the thread, and not as a variable or copy. This means, the myParams.Parameters (first example) or text$ (second example) have to keep as they are as long ...

No problem with Window 10 Pro 22H2

For macOS Packet PB v6.11 Beta 1, the IDE and the compiler show version v6.10 LTS.
But it is the new compiler v6.11 beta 1 because the bug with arrays is fixed.

Thank you very much,

For macOS Packet PB v6.11 Beta 1, the IDE and the compiler show version v6.10 LTS.
But it is the new compiler v6.11 beta 1 because the bug with arrays is fixed.

Update v2.12
- Bugfix ActiveScript Release

Oops, I had one Object.Release() too many.
Furthermore, I set the debug output to #DebugLevel = 6 (#DebugLevelActiveScriptEx) to display all debug outputs.

As it looks now all reference counters of all objects are correct