Sorry, deleting all the posts from one thread bar the original one is Bull*****.
Want a clean thread start a new one.
If we started doing this then we would probably have to delete 30% of the forum.
*bump* for a clean thread and a new release. Please let me know what you think, I know it's kinda ugly but I'm not an artist. I'm hoping that people like this. Please if you check this out and download it leave some kind of comment, any feedback is good. Skinners willing to help is even better :-D
Sorry, deleting all the posts from one thread bar the original one is Bull*****.
Want a clean thread start a new one.
If we started doing this then we would probably have to delete 30% of the forum.
nice work malcom2073.
Never let the truth get in the way of a good story
marine corps,
woops sorry talking about something else...
New Age Garmin - Skin for RR
New Age Slider - RR SKin In Progress
"It's called CODE because I don't want you to know"
Update: I noticed the visual c++ 2008 runtime may be needed to run CarPal:
http://www.microsoft.com/downloads/d...displaylang=en
I've posted an update to V0.30. Embedded applications are now working, and iGuidance is CONFIRMED as working. This means CarPal now has navigation! Woo!... Dunno if anyone else is as excited as I am. This has also been tried out on a FitPC, the 500mhz one and confirmed as being "very quick" to quote Tidder. I will be working with him to ensure that CarPal remains quick on even the slowest hardware.
As I said I'm still working on the .net functionality, I've gotten one way communication working (CarPal->.net) but not the other way. I'll move that closer to the top of the list now that embedded apps are working and see if I can't get it running.
The entire basis behind the plugin system are messages that have several parameters. I'll list them here just so you get an idea what you'll be dealing with.
Sender - name of the plugin sending the message
Target - target of the message. Plugin name, window name, or "core"
Class - top level "Type" of message. For example this could be "window" to deal with window commands, or "playlist" to deal with playlist commands.
Method - Actual command to run, eg: show for a window class, or play for a mediaplayer class.
Arguments - Each message can have a list of arguments as strings. This is used for whatever you want. For instance, the MediaPlayer uses this to send a list of current playlist filenames.
The system is also event based, you can "subscribe" to events by sending an IPCMessage to the core, and you will recieve an IPCMessage when that event is thrown. I will provide a list of what events are provided by what plugins once I get the .net interface up and running.
What do your plugins require in the way of external information? I can make sure the interface is there.
Bookmarks