VXCMD 1.x and Revolution 2.1

[Robert Brenstein]

>
>Hmm, I think here some misunderstanding.
>
>VXCMD 1.11 support BOTH ways. REVDB and standard Valentina API.

Yes, it is misunderstanding... by you :)

>Revolution guys cannot disable Valentina way I think.
>Can you call Valentina() function ?
>Then you must have access to all functions of VXCMD.

When using vxcmd way, all works. When using revdb way, only what 
revdb has preprogrammed works.

>  > You do not really need to worry about revdb IMHO. RR will just have
>>  to add support for val2 in revdb at some point.
>
>Please note, that we have work together. We have made C++ sources then I
>have compile them. So VXCMD have both ways.

I meant that V2 will have some changes in the functions calls which 
will need to be accommodated by revdb, so they will probably need to 
support both V1 and V2 versions vxcmd at the same time.

I wonder whether the issue with replacing vxcmd inside rev now has to 
do with differences between 1.9.8b4 and 1.9.10. Which version added 
additional parameters related to locking?

The swap worked at some point in the past but haven't tried it for a 
long time since all I do currently with Rev/Val combo must work in 
OS9 only and there is no problem with swapping there. But I will be 
dealing with this under OSX real soon now.

>P.S. Kevin, I continue CC to you in hope that you will redirect this letters
>to your engineers that will help us.

This should probably me added to Bugzilla, their bug tracking system, 
and possibly mailed to support at runrev.com for faster attention. Kevin 
may not the optimal "entry point" although getting his attention 
would clear things faster.

Robert