intérêt pour l'application

I see... If I can be of help in making this (English manual) happen, let me know.

@Noel,
I've track your gitHub account and the only thing you've merged are .DS_Strore files, I guess that's not what you want to share.
Commit is not enough as it commit to your account, you need to ask after for a pullRequest.

about dlight-book,
happily, there's enough people that know how to use DL to help others that do not. So it's more or less that the dlight-book will never emerge....
before dlight-tools on GitHub, there was an attempt with the wiki, but not enough take time to write stuff there to make it usefull.
it would be great to start it on gitHub, but I do not have enough free time to initiate it.

feel free to commit stuff if you have time and after we can discuss/improve/merge/write.

++

did you tried to set the writer address wit 255 at the end?
x.x.x.255 means broadcast in wich case, all device registered on the network x.x.x should receive the information.

I tried that, but -alas- it didn't work.

also,
we have created a page to register DL tools here
github.com/dlight-tools
If you register an account on github, I think you should be able to ask for a pull-request to upload your work in the dlight-pad/touchosc section.

I have 'committed' my templates again. Can you please check it you can see them now ?

Merci,
Noel

Hi

noelvd wrote:
...

also,
we have created a page to register DL tools here
github.com/dlight-tools
If you register an account on github, I think you should be able to ask for a pull-request to upload your work in the dlight-pad/touchosc section.

I have 'committed' my templates again. Can you please check it you can see them now ?

Merci,
Noel

I think you still haven't sent a 'Pull Request' to the DLight-Tools account from which you fork. If you look at this Network graph screenshot from GitHub, you'll see that your fork (bottom, Yellow) only has an arrow going away from the DLight-Tools repo. If you hover the mouse over each 'point' in the graph it pops up the Commit number and any notes. (So the popup with your changes in it for the first point in your fork). When a Merge back to the master happens, the black lable is appended. So your 'Commit' has merged back to *your* master, but your master has not yet merged with the DL-Tools master, whereas mine(blue dots) has

You can check it out yourself by clicking the 'Network' button on your own repo, or on the DLight-Tools repo.
But as I say, you will still need to click the Pull Request button to get Nico to merge into his master





Hope this helps

Colin

Noel,
I do not received yet a pull request from your fork.

++

Sorry for the delay.
Been too busy (with my new toy: the Electron Design Artnet node...)

So, I have just done a 'pull-request'. Fingers crossed that I got it right this time :ohmy:

Thanks !
Noël