A Marchini wrote:There was plenty of source code around for a few of the different plugins. There wouldn't be much point of having a discussion forum about plugin development if we couldn't publish the code.
Aah, excellent. I had a quick look and couldn't see too much available, but I didn't dig too deep. Now that I know there's stuff around I'll poke through it all more thoroughly. 🙂
There are some "howtos" around here somewhere... basically how to setup the plugin project and things like that. I am sure there is code around here too. If not I can set you up.The main body of the code is closed, but the plugins were open last I checked.
Cool -- I was initially worried when it was only the example parallel port driver that was available, but it looks like I need not worry. 🙂
Any idea why Vixen is closed source? I'm not complaining, please don't get me wrong, I just usually associate software that's free and having such a good support community with being open-source.
I have enclosed a pre-lim document describing the class structure. The big things to get going are the Initialize and Event.
Event gets passed in to your channel set (I believe only the channels your plug in is assigned) at refresh intervals described by the vixen programming grid.
Wow -- that's really great! Thanks for that -- it helps having the API around, or just something to know how it all fits together. 🙂
Anyways,
...hi?
Tony M.
Eek, I must apologise -- I set this thread to "subscribe", visited when there was one reply, and never got any more emails, so I assumed it wasn't getting replies! Why it didn't clear the "visited" flag, I'm not sure..... anyway, so I apologise for the delay in replying.
A Marchini wrote:I have enclosed a pre-lim document describing the class structure. The big things to get going are the Initialize and Event.
Event gets passed in to your channel set (I believe only the channels your plug in is assigned) at refresh intervals described by the vixen programming grid.
Hrm, quick question about that -- is the Event function called for *every* time slice (ie. every 100ms, or 50ms, etc.) -- and when it is called, is it fully populated with all channels?
Basically, I'm trying to figure out if it's smart about it at all -- ie. not calling it for time slices when nothing changes, or only sending events for channels where something has changed.
Cheers!
Michael
sallz0r wrote:Hrm, quick question about that -- is the Event function called for *every* time slice (ie. every 100ms, or 50ms, etc.) -- and when it is called, is it fully populated with all channels?Basically, I'm trying to figure out if it's smart about it at all -- ie. not calling it for time slices when nothing changes, or only sending events for channels where something has changed.
Cheers!
Michael
That is a real good question. I am not sure at this moment. I was hoping that some of the other players in the software realm would pipe up at this point.
I think that the list is only populated with the channels that you select for the control,but I also believe that it sends data to the control on the event time, no matter what.
Again I am not too sure. A PM to KC to ask that he weigh in on the site may help here.
He could answer these two questions in about a half second.
Sorry it took so long to reply! Been moving.
Hrm, quick question about that -- is the Event function called for *every* time slice (ie. every 100ms, or 50ms, etc.) -- and when it is called, is it fully populated with all channels?Basically, I'm trying to figure out if it's smart about it at all -- ie. not calling it for time slices when nothing changes, or only sending events for channels where something has changed.
The Event method is called whenever there is a change in the state of the channel values. With each call, the method receives the data for every channel that's being sent to that plugin.
A Marchini wrote:There was plenty of source code around for a few of the different plugins. There wouldn't be much point of having a discussion forum about plugin development if we couldn't publish the code.
Hrm, is anyone able to point me in the direction of said code for output plugins? I had a dig through the rest of the forum, and have found a few snippets and example chunks of code for some things, but I haven't found anywhere that has the code for any of the actual production plugins that are used in vixen (ie. fully implemented ones, that do stuff from start to end).
Does anyone know if these are available anywhere? The documentation provided by A Marchini is great, as well as the sample things that are floating around, but I just wanted to analyze what some of the "real" plugins did. 🙂
Thanks to all!
Cheers,
Michael
