The easiest way to solve the synchronization problem is probably to wrap the calls to the dealerForm controls in postAction calls: dealerForm:postAction({ :- dealerForm:state_ctl:setText(StateStr) }), dealerForm:postAction({ :- dealerForm:deck_ctl:setText(DeckStr) }), dealerForm:postAction({ :- deal...

I took the critical section out and played a bit. Starting a bunch of dealers, closing a lot, and again starting some... That game did not take long until I got an exception: ===== 2019-10-28 23:22:45 ======================= ---------------------------------------- System exception error code = 1 Ex...

In addition to what Harrison said a look into the Language Reference can help you. It says: ..., all clauses for one predicate/fact (the same name and arity) must be grouped together in one clauses section and without intervening clauses of other predicates/facts. That means, allowed is: class predi...

Yes. I have changed the example to use the application windows status line as a load indicator. Now the example displays only a text on the status bar, but that is for what Loffy has asked for. I have tried to use terminate/1 and close/0 to cancel the thread when the formWindow s close button is cli...

aah :idea:, thank you again, Thomas! I have modified the example to directly update the progress display. The example has only one kind of formWindow . But a real application could have many kinds of formWindow s and each kind needs to display different controls on the status bar. Thus (as always) i...

Thank you Thomas! Now the progressBarControl works on the statusBar in the example. Updating the progress directly from the lengthy operations is of course much better than polling for progress updates. But I do not see how to do it. Simply calling Windows GUI predicates from the lengthy operations ...

I have tried to set up an example which follows all of Thomas' advice.

In the example the progressBarControl is working fine in formWindows, but there is a problem with it in the status bar.

Please have a look, Thomas. What is wrong about the example?

The Language Reference says: The special flow pattern anyflow can be stated only in declarations of local predicates (i.e. in predicate declarations inside the implementation of a class). It means that the exact flow pattern(s) will be evaluated during the compilation. In accordance with the 1st sen...

Hit the Post Reply Button as you did before, if necessary login,
and have a look above the message editor box.

The reason of error several classes interfaces and/or namespaces have the same name "main" is that 'empty' projects already contain a class main and you have created a second class having the same name. Class names must be unique however (in each namespace). I think there are two issues about the ex...

To put a code grab into the post, click the "Code display" button pic.jpg which will insert a BBCode tag pair template into the text. Then place your code via copy/paste between the tags. When you create a new project, VIP makes a copy of a default project template to start with. For GUI style proje...

An example, which is obscure too, but cannot be de-obscured in same way as you have done above, is: open core class predicates test : (unsigned X). clauses test(X) :- tuple(A, X) = tuple(B, B), % throws errors: Variables "A", "B" are not completely bound stdIO::write(A, ", ", B). clauses run() :- te...

I have found an easier solution. In a newly created GUI style project do as follows: Add the declaration for a predicate displayStatus/1 in projectToolbar.cl: class projectToolbar predicates create : (vpiDomains::windowHandle Parent). predicates displayStatus : (string Text). end class projectToolba...

I have tried variations of my prior post , thereby I discovered it. I have even copied the wrong spelling 'unfiable' from there. :oops: Another example of notorious code, where unification has a problem (in build 902), is: open core clauses run() :- A = 1, tuple(tuple(A, A), tuple(B, B)) = tuple(B, ...

...continued from previous post I add a timer listener in the task window: pic6.jpg I insert some code in the onTimer listener which will display the time in the text field of the new toolbar: pic7.jpg In the onShow listener I add a line to start a timer: pic8.jpg I run the project, voilà! pic9.jpg