The default buffer size for both reading and writing to files is 8KB: class inputStream_file : inputStream open core constants defaultBufferSize = 0x2000. If your read in 8 bit text mode (e.g. utf8), the actual buffer size is only half, because we there is an approximate doubling when converting fro...

It is a Windows thing. It seems to be controllable. See: Fault Tolerant Heap.

No, unfortunately not.

I can reproduce the problem.
But it does not exist in Vip 9.

Notice that you already knew it (see a couple of mails above ).

The Personal Edition doesn't contain vpiOldDomains.

When I compile the project with the Commercial Edition I don't get any errors.

Notice that when upgrading to the newer gui structure you will not need vpiOldDomains.

I have updated hitTest like this (i.e. the lines after the cut):: clauses hitTest(PNT, ItemId, SubItem) :- LVHITTESTINFO = gui_native::lvhittestinfo(PNT, 0, 0, 0, 0), _ = gui_native::sendMessage(nativeWindow, lvm_subItemHitTest, gui_api::wNull, uncheckedConvert(gui_native::lParam, LVHITTESTINFO)), g...

The listView control is a standard Windows control. The hitTest predicates uses the LVM_SUBITEMHITTEST to determine where the point is. For reasons unknown to me this message think that most of the header row belongs to the first data line. The difference in the left and right click happens because ...

You cannot rotate controls (yo my knowledge). You could create one that is high and narrow, but the text on the button would still be horizontal.

It is sufficient with one postAction:

There are individual examples concerning listBox and database among the examples that are distributed with the system. The database demos (assuming that you mean SQL/ODBC databases) is only in the Commercial Edition (because the Personal Edition does not support ODBC). We do not have any tutorials a...

Working with multiple threads has that kind of synchronization problems that you mention and that is why it is not simple to shift work into separate threads. To enable premature termination of a background task, it is of course necessary to ensure that the termination is carried out is a safe order...

I think it looks fine. You should notice that it is not necessary to guard random with a critical section, it is already guarded internally.

Please read about how to present code in Visual Prolog discussion forum.

The format is not designed to be easy to read. It is designed to be difficult to read.

Well, you seem to have achieved this (sorry I didn't resist it).

Anyways, if you open the file in binary mode then readBytes will read a binary like that.