Search found 68 matches
- Sat Jan 28, 2023 9:01 pm
- Forum: BlackBox Framework
- Topic: Team development
- Replies: 2
- Views: 22810
Team development
BlackBox is a big enough program to have been developed by a team of programmers. I was wondering if Oberon Microsystems was using any team development tools, and how their process was organized. The current BlackBox lacks any such tools, save maybe for the Compare Texts command. Modern-day mainstre...
- Fri Oct 14, 2022 6:52 pm
- Forum: Components Support
- Topic: USA users of BlackBox
- Replies: 4
- Views: 14613
Re: USA users of BlackBox
Lance, Could you share how you use BB?lschwerdfager wrote: ↑Fri Jul 08, 2022 3:53 am Lance Schwerdfager ... I'm actually Canadian but that should be sufficiently close to qualify.
- Sat Aug 13, 2022 8:15 pm
- Forum: Common questions
- Topic: 64 bit?
- Replies: 7
- Views: 19596
Re: 64 bit?
Yes, there are plans for a 64bit compiler and 64bit BB.
Out of curiosity, Why are you interested? Is it, well, curiosity, or any practical intent?
Out of curiosity, Why are you interested? Is it, well, curiosity, or any practical intent?
- Thu Jan 20, 2022 2:29 pm
- Forum: Bug
- Topic: VAR [nil] for tagged structural parameters
- Replies: 3
- Views: 9525
Re: VAR [nil] for tagged structural parameters
Moving the check up to the front-end of the compiler sounds like a good idea to me. SetDIBColorTable is definitely a mistake: PROCEDURE SetDIBColorTable (p0: WinApi.HDC; p1, p2: INTEGER; VAR [nil] p3: ARRAY OF WinApi.RGBQUAD): INTEGER; UINT SetDIBColorTable( [in] HDC hdc, [in] UINT iStart, [in] UINT...
- Sat Nov 06, 2021 6:13 pm
- Forum: System
- Topic: DLL memory model
- Replies: 2
- Views: 12424
Re: DLL memory model
I have discovered that Kernel uses WinApi.VirtualAlloc/VirtualFree for 'module memory': code, global vars, metainformation; and WinApi.HeapAlloc/HeapFree to allocate clusters of memory that are used for dynamic variables. I wonder if it makse sense to use HeapAlloc/Free. These functions allow to all...
- Sat Nov 06, 2021 5:50 pm
- Forum: BlackBox Framework
- Topic: HostPorts.Input fixup
- Replies: 4
- Views: 10421
Re: HostPorts.Input fixup
Update for p. 3 of my last post: the lagging I described only occurs in Linux. Turns out in Windows WM_MOSEMOVE events never 'stack up' in the queue, and the WM_MOUSEMOVE message always contains the most recent pointer location. However, f.Input still 'eats' WM_LBUTTONDOWN messages and thus a corres...
- Fri Nov 05, 2021 10:31 pm
- Forum: BlackBox Framework
- Topic: HostPorts.Input fixup
- Replies: 4
- Views: 10421
Re: HostPorts.Input fixup
Some questions: 1. Here https://community.blackboxframework.org/viewtopic.php?f=48&t=181&hilit=ghosting was a brief discussion of window ghosting, whereby Josef suggested removing all messages from the WinApi queue while only processing mouse messages by using 0, 0 for filters in the call to...
- Thu Nov 04, 2021 10:06 am
- Forum: System
- Topic: DLL memory model
- Replies: 2
- Views: 12424
DLL memory model
Reading the Kernel module, I have noticed two memory models distinguished by the variable dllMem: BOOLEAN; Also, the Kernel module used in Linux for the cross-platform BlackBox does not have two memory models, but only one; and it looks like the one used in Linux Kernel matches the dllMem model in W...
- Wed Aug 04, 2021 1:32 pm
- Forum: BlackBox Framework
- Topic: SYSTEM.TYP - Why is it even there?
- Replies: 1
- Views: 12171
SYSTEM.TYP - Why is it even there?
Colleagues, In keeping my work on Herschel, the amd64 compiler for CP, I have encountered the following. Platform-Specific issues defines the module SYSTEM, including procedures TYP and ADR. Their definition in PSI is limited compared to what they actually do. SYSTEM.TYP expects, according to PSI, a...
- Fri Jul 23, 2021 3:11 pm
- Forum: BlackBox Framework
- Topic: Current directory and Dialog.RunExternal
- Replies: 8
- Views: 16162
Re: Current directory and Dialog.RunExternal
Colleagues, Helmut's explanation did help me understand the issue better. 1) All these features 'live' in HostFiles, and HostFiles alone. This means it is not a BlackBox feature, rather, a platform feature (in this case, platform=win32) 2) 'BlackBox installation path' = path where BlackBox.exe resid...