I believe/think the installer will in any case first uninstall the old version and then install the new one.

And in any case you will not need to purchase another licenses.

No, there are no such plans. It seems that CUDA is a very huge set of libraries, which it would be very difficult to support.

The chainDB is mainly present for backwards compatibility. I don't think it is suitable as a real database, because it has no backup and recovery facilities. If anything goes wrong during operation all your data may be lost. But it can be used for internal purposes (e.g. caching or calculations) whe...

I am not sure I understand the question, subsequently anything I answer may be wrong :-). And I believe your code looks more like ISO Prolog in the sense that you seem to have a vague boundary between code and data. In Visual Prolog there is no term interpretation machinery, so you cannot pass code ...

Using timers like that is somewhat "old fashioned", it has the disadvantage that it "mixes" all your timers in a single handler. Using tickAction's (and delayCall for one shots) has a more direct handler approach: clauses new() :- applicationWindow::new(), generatedInitialize(), ...

Unfortunately, that dream will not come through. Interfaces define the interface of objects the implementation is written in the implementation. Also recall that though you think of a class and interface together, a single interface can be used for many classes. Likewise a class defines the "in...

Regarding string: I didn't supply a value. I assumed it would work since that worked for integer, etc.

Well, I have two "problems" with this suggestion. First of all it is a strict rule that implementation details are written in the implementation; interfaces only defines the interface. Secondly, the suggested auto code has exactly the same effect as implementing the property with a fact: i...

I think you should use the sciLexer instead of an edit control. So I have update a few files.
I have problems with string properties.

You should also notice that auto-formatting will write the code differently.

Ok .

Ok.

In future releases the sciLexer will have these key binding predicates, where the three last ones are new: predicates assignCmdKey : (unsigned KeyDefinition, integer SciCommand). % This assigns the given key definition to a Scintilla command identified by sciCommand. % sciCommand can be any SCI_* co...

In the sciLexer itself you can assign sciLexer -built-in actions to keys. But to perform your own custom commands you will need to handle the keypress before it reaches the sciLexer . We have done that in a "hard coded" fashion to deal with the tab mechanism we want(ed). I think it makes s...

Sorry, I overlooked some details .

The second argument of assignCmdKey is a command (sciLexer_native::sci_...) not a key:

It is a bug. Actually, this bug turns up over and over in different contexts, but I guess that it will eventually be solved for all contexts. The usual work-around also helps in this case. Redefine your domains like this: domains repDomain{T} = repDomain(arrayM{T} ArM, recoverableState State). And c...