Search found 294 matches

by Martin Meyer
9 Jan 2020 20:20
Forum: Visual Prolog
Topic: memoryAccessor
Replies: 2
Views: 241

Re: memoryAccessor

Ah, thank you Thomas! I have updated memoryAccessor to your code.
by Martin Meyer
7 Jan 2020 19:07
Forum: Visual Prolog
Topic: memoryAccessor
Replies: 2
Views: 241

memoryAccessor

Hello Thomas, the debugger has a problem in this console application (in build 902): implement main clauses run() :- ArM = arrayM::new(1), ArM:set(0, ""), stdIO::write(ArM). %set a breakpoint here end implement main goal console::runUtf8(main::run). To cure that I have changed the memoryAccessor cla...
by Martin Meyer
16 Dec 2019 14:34
Forum: Visual Prolog
Topic: Source file too large?
Replies: 2
Views: 433

Re: Source file too large?

Yes, it was reproducible. The error message box appeared also when I tried to only save the file. Thus I suppose, it was not a compiler problem but some IDE/editor issue. I am writting 'was' because now I have split the implementation up into two files (by an additional inherited/supported class/int...
by Martin Meyer
15 Dec 2019 4:14
Forum: Visual Prolog
Topic: Source file too large?
Replies: 2
Views: 433

Source file too large?

Hello Thomas, adding some code lines to a large file (named lambda.pro , having 3319 lines) and clicking 'Compile' I am getting below error. It looks like the file size is exceeding some limit. Do I have to split the file into smaller parts or what could be the cause of the error? pic1.jpg ---------...
by Martin Meyer
5 Dec 2019 19:30
Forum: Visual Prolog
Topic: Default for a boolean component
Replies: 1
Views: 528

Default for a boolean component

Hello Thomas, please check this (in build 902) when building next VIP version: domains rec = rec(integer Number, boolean Flag = false). %error c520 : Impossible to determine the type of the term %rec = rec(integer Number, unsigned Flag = 0). clauses run() :- Rec = rec(1), stdIO::write(Rec). With the...
by Martin Meyer
31 Oct 2019 0:21
Forum: Visual Prolog
Topic: Progress Bar status indicator
Replies: 37
Views: 3797

Re: Progress Bar status indicator

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...
by Martin Meyer
28 Oct 2019 23:47
Forum: Visual Prolog
Topic: Progress Bar status indicator
Replies: 37
Views: 3797

Re: Progress Bar status indicator

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...
by Martin Meyer
26 Oct 2019 17:45
Forum: Visual Prolog
Topic: Compiling error
Replies: 8
Views: 1240

Re: Compiling error

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...
by Martin Meyer
25 Oct 2019 18:42
Forum: Visual Prolog
Topic: Progress Bar status indicator
Replies: 37
Views: 3797

Re: Progress Bar status indicator

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...
by Martin Meyer
23 Oct 2019 22:22
Forum: Visual Prolog
Topic: Progress Bar status indicator
Replies: 37
Views: 3797

Re: Progress Bar status indicator

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...
by Martin Meyer
21 Oct 2019 18:14
Forum: Visual Prolog
Topic: Progress Bar status indicator
Replies: 37
Views: 3797

Re: Progress Bar status indicator

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 ...
by Martin Meyer
20 Oct 2019 19:38
Forum: Visual Prolog
Topic: Progress Bar status indicator
Replies: 37
Views: 3797

Re: Progress Bar status indicator

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?
by Martin Meyer
18 Oct 2019 8:50
Forum: Visual Prolog
Topic: Using "anyflow" works in "pro" file but seems to need all declared iterations in the "cl" file.
Replies: 2
Views: 1111

Re: Using "anyflow" works in "pro" file but seems to need all declared iterations in the "cl" file.

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...
by Martin Meyer
14 Oct 2019 16:34
Forum: Visual Prolog
Topic: Progress Bar status indicator
Replies: 37
Views: 3797

Re: Progress Bar status indicator

Hit the Post Reply Button as you did before, if necessary login,
and have a look above the message editor box. :D :D :D
by Martin Meyer
13 Oct 2019 21:23
Forum: Visual Prolog
Topic: Compiling error
Replies: 2
Views: 1052

Re: Compiling error

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...