679
edits
Changes
Jump to navigation
Jump to search
Line 603:
Line 603: + + Line 621:
Line 623: − + − −
Contributing to Zynthian Development (view source)
Revision as of 16:00, 4 September 2024
, 16:00, 4 September 2024→Where do I put, what files to make it work?
Well there is one other thing that needs doing to ensure the file you have added is included in the scan the zynthian makes to detect device drivers it knows about and that is to add the details of your file into the rather peculiarly named __init__.py file . . THis is a default file that python likes to see in a directory to tell it what is and is not required elsewhere....
Well there is one other thing that needs doing to ensure the file you have added is included in the scan the zynthian makes to detect device drivers it knows about and that is to add the details of your file into the rather peculiarly named __init__.py file . . THis is a default file that python likes to see in a directory to tell it what is and is not required elsewhere....
As of (09/04/2024) it looks like this...
As of (09/04/2024) it looks like this...
The __all__ is a python directive to publish these modules and it means they can be seen as fully fledged members of the zynthian namespace.
# -*- coding: utf-8 -*-
# -*- coding: utf-8 -*-
]
]
This needs to match the layout of your script,which in my case I copied from Duo_piano
This needs to match the naming of your script, Which is the file zyngine/ctrldev/zynthian_ctrldev_behringer_motor61.py, which in my case I copied from the Duo_piano File...
====How do we know we are actively running our code....?====
====How do we know we are actively running our code....?====