Classical way, easy to understand: class predicates isSubSet : (T* CheckTerms, T* Terms) determ. clauses isSubset([H], Terms) :- list::isMember(H, Terms), !. isSubset([H | TT], Terms) :- list::isMember(H, Terms), isSubSet(TT, Terms). Another way using VIP list class predicates. Put your cursor on &q...

nothing(...) does nothing. It's a way of making the IDE capture an unused variable so you can see it when running the debugger. Unused variables do not consistently display in the Variables window when debugging without making them appear as being used to the compiler. It has no place in production...

One way would be to create a class database in your base class and store the object identifier information you need in that database when you create each object, something like that below. You will need to manage removing personObj/2 facts when objects are destroyed and you also should remember that...

domains myDomain = good; bad; ok. myDomainList = myDomain*. class facts myFactDB : (myDomain VarA, myDomain VarB, myDomain VarC, myDomain VarD). class predicates getMatchN_nd : (integer Count, myDomainList TestList) -> myDomainList MatchingValues nondeterm. clauses getMatchN_nd(N, TestList) = FactV...

You can use vpi::processEvents() to force immediate output to the Messages window. This may slow down processing so use it judiciously.

One way is the catch any failure of startExperiment() so it does not fail, although that may not be what you want to do: clauses runExperiment() :- startExperiment(), ! or succeed. or you can catch failure in runExperiment() , although that may not be what you want to do either: clauses runExperimen...

This would be a good time to learn how to use the debugger and walk through the code as it executes. Put your cursor on the line with culc(In) in your run clause and press F9 to set a breakpoint. Then press F5 (or click the single green triangle on the toolbar) to run the code in the debugger. Press...

Can you post some of the relevant code? Remember that you should format code in this forum using the [</>] button in the forums editor. It is a better practice to put the bulk of your code in a class other than main.pro or taskwindow.pro and invoke those class predicates from taskwindow.pro , but I ...

Facts can be declared only in a class's implementation ( .pro file) so you cannot make the facts themselves visible outside that class. However, you can easily put predicate definitions to manipulate those facts in the class's .cl file or .i file(s) to make them accessible from other classes as in t...

The default specification for predicate definitions is [in], so you don't need to specify that a parameter is an input. You may be surprised to see that the IDE will change a valid definition like this: demoPred : (integer Input , string Output) (i,o). to this preferred form: demoPred : (integer Inp...

[out] indicates that a value is returned from the predicate. For example: class predicates demoPred : (integer Input, string Output [out]). clauses demoPred(Input, OutPut) :- if Input < 0 then OutPut = "Negative" elseif Input = 0 then OutPut = "Zero" else OutPut = "Positive&...

wrapString : (string String, charCount HyphenLength, charCount MaxLength, string Indent) -> string* Lines. % @short % @detail #HyphenLength <= #MaxLength % @example % % All the statements below succeed: % ["123456","7890"] = string::wrapString("1234567890", 6, 6, "...

Is there a way to dynamically change the font in the projectToolbar beyond the options in the IDE wizard? I can change the text of the Static Text and can dynamically change a listButton's strings and font, but cannot figure out how to change the Text font. onTest(_Source, _MenuTag) :- vpiToolbar::g...

That is beyond my expertise, unfortunately.

cgi::init(stream::ansi(core:: ansi)),

Perhaps you want core::threadAnsi