-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dragonfly scripts without aenea #32
Comments
It looks like I accidentally introduced the hard dependency when upgrading to the latest aenea. In the meanwhile, try checking out the pre_aenea_reorganization tag. |
I took the files from the pre_aenea_reorganization repository and copied them to the NatLink NATLink MacroSystem folder.
resulting in this error:
But then if I "install" Aenea client, then its requesting jsonlib I appreciate any hint as to use the scripts without aenea. Thank you |
I guess this has been tied to aenea for longer than I've realized. You can keep digging back through history, but until I'm able to spend some time to split the two apart, you may be better off just installing aenea as well. |
I copied Aenea client and somehow adjusted aenea.json. Error loading vocabulary from C:\NatLink\NatLink\MacroSystem_vocabulary.py So I copy jsonrpclib to the macrofolder Then I do not need proxies etc. |
I stripped all scripts I require from aenea by hand, so I can start working with the scripts. Could you inform me as soon as you might have deconnected aenea from the scripts? Thank you |
is anyone working on this? These scripts seem really useful but I can't use them because of this. |
Hello,
I copied all the scripts in the corresponding natlink folder and they all require Aenea to run. I copied some Aena Client and now its requesting jsonlibrpc .....
But I want to work only locally on my windows 8 machine without any Virtualmachine doing coding in Visual Studio.
Is there a switch to set like "do not use aenea", so that all the scripts run locally without aenea?
Thank you
The text was updated successfully, but these errors were encountered: