wee! i finally made it!
With some help from Jaak (and some nice ppl in a c++ help channel ), i translated AVSTrans to C++!
After doing this, it was only a minor step to integrating AVSTrans into my existing eeltrans.ape (which used the VB AVSTrans via COM before).
Now, eeltrans.ape is completely self-contained and can thus be spread along with a preset for example
Also, it can now be used without admin rights and should also run fine on wine.
This APE should do the same as the latest VB version. if it doesnt, or if it crashes or outputs strange errors that the VB version doesnt, plz send me the code piece that causes the problems and I'll see what i can do about it.
The APE also has a code logger that writes all your code into various files in c:\avslog
[edit]
04.11.05
- major fixup: code saving and displaying works now. crashes less often.
28.06.05
- I fixed and changed the behaviour of global code. You can now have multiple instances of AVSTrans concurrently and even specify global code for each one. The code will simply be concatenated in this case. There should be no more "Instance conflict" dialog boxes or lost code.
30.03.05
- gmegabuf loading should be much faster with this new version and the upcoming version 1.1 of Jheriko's Global Variable Manager
02.02.05
- You can now include external files using "#include filename". Refer to eeltrans.txt for more information and an example.
- log path is now customisable
14.12.04:
- allowed things like a=b=c; (assigns the value of c to a and b)
07.12.04:
- crash bug fixed that would occur if "*)*(*;*)*" was entered, where * is any combination of characters (except brackets) including no characters at all. thx fsk for first reporting this (very vaguely though )
- some optimisations
06.12.04:
- hopefully everything in the #defines fixed
- fixed a bug that prevented loading the settings when switching from one eeltrans preset to another
04.12.04:
- added documentation
- fixed config dialog grabbing focus when loaded
- fixed a (stupid) bug in the #defines that prevented using token identifiers longer than 1 character
- fixed another bug in the #defines that prevented some uses of the token insertion operator (##) not to work
03.12.04:
- fixed freezing when entering incomplete #defines
- fixed freezing when having bracket errors while using macros
- fixed a stupid bug in the code logger that caused it to crash when entering code with "%" in it
02.12.04:
- improved preset changing behaviour (will not delete the AVSTrans component anymore)
[/edit]
I've had a thought, ya know what'd be nice? If you could translate the preset then save a translated version, for distribution in packs, since at the moment it's still kinda unstable for me... at least on this computer, I know I could use the VB version and do it by hand, but I've got a preset with rather a lot of separate components that all use AVStrans features... (mostly control stuff)
is what I have right now, and there are things that I'm gonna use those in that it wouldbe nice to be able to one of these macros inside another... not to mention that the above would be nicely simplefied to:
it is indeed possible, you just have to reverse the order of your #defines
#define triLin(px,py,pz,v1,v2,v3,v4,v5,v6,v7,v8) lin(pz,biLin(px,py,v1,v2,v3,v4),biLin(px,py,v5,v6,v7,v8))
#define biLin(px,py,v1,v2,v3,v4) lin(py,lin(px,v1,v2),lin(px,v3,v4))
#define lin(pos,v1,v2) (pos*v1+v2*(1 - pos))
explanation:
#defines are applied to the code, in their order of appearance in the original code
C++ is an object-oriented programming language built from the structured language C
its advantages are speed and complete/real OO
Visual Basic (VB) is a pseudo-object-oriented Rapid Application Development language basing on the Syntax of the well-known "BASIC" language
it doesnt have real Object orientation in version 6. the reason i use it anyway is that it makes application development faster by doing all the interface stuff for you.
but if you just want a library and dont need a user interface, you have a problem, since VB is not capable of making a simple DLL and exporting some functions and you must use the component object model (COM) instead. COM is a bitch to use in C++ though, with a hugely complex interface.
all i need for that would be a complete format description for .avs files
#define lin(pos,v1,v2) (pos*v1+v2*(1 - pos))#define biLin(px,py,v1,v2,v3,v4) (py*(px*v1+(1-px)*v2)+(1-py)*(px*v3+(1-px)*v4))
#define triLin(px,py,pz,v1,v2,v3,v4,v5,v6,v7,v8) ((py*(px*v1+(1-px)*v2)+(1-py)*(px*v3+(1-px)*v4))*pz+(1-pz)*(py*(px*v5+(1-px)*v6)+(1-py)*(px*v7+(1-px)*v8)) )
is what I have right now, and there are things that I'm gonna use those in that it wouldbe nice to be able to one of these macros inside another... not to mention that the above would be nicely simplefied to:
#define lin(pos,v1,v2) (pos*v1+v2*(1 - pos))#define biLin(px,py,v1,v2,v3,v4) lin(py,lin(px,v1,v2),lin(px,v3,v4))
#define triLin(px,py,pz,v1,v2,v3,v4,v5,v6,v7,v8) lin(pz,biLin(px,py,v1,v2,v3,v4),biLin(px,py,v5,v6,v7,v8))
#define triLin(px,py,pz,v1,v2,v3,v4,v5,v6,v7,v8) lin(pz,biLin(px,py,v1,v2,v3,v4),biLin(px,py,v5,v6,v7,v8))
#define biLin(px,py,v1,v2,v3,v4) lin(py,lin(px,v1,v2),lin(px,v3,v4))
#define lin(pos,v1,v2) (pos*v1+v2*(1 - pos))
explanation:
#defines are applied to the code, in their order of appearance in the original code
its TWO years old...damn it, i feel stupid.
but before it was like Frankenstein's creature: half VB half C++
i dont even no what C++ is.
im guessing its a type of programming thing? ive heard been said a few times.
its advantages are speed and complete/real OO
Visual Basic (VB) is a pseudo-object-oriented Rapid Application Development language basing on the Syntax of the well-known "BASIC" language
it doesnt have real Object orientation in version 6. the reason i use it anyway is that it makes application development faster by doing all the interface stuff for you.
but if you just want a library and dont need a user interface, you have a problem, since VB is not capable of making a simple DLL and exporting some functions and you must use the component object model (COM) instead. COM is a bitch to use in C++ though, with a hugely complex interface.