[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: RE: Slim Conduit Feature request vs. GUI Plugin bits feat. MC
Booth and the plugin boys
- Subject: RE: RE: Slim Conduit Feature request vs. GUI Plugin
bits feat. MC Booth and the plugin boys
- From: Edward Pearson
- Date: Sun, 28 Mar 2004 20:13:00 +0000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<TITLE>Message</TITLE>
<DIV><SPAN class="968501119-28032004"><FONT
face="Arial" color="#0000ff" size="2">Very
swish! All based on FileSystemWather I
assume.</FONT></SPAN></DIV>
<DIV><SPAN class="968501119-28032004"><FONT
face="Arial" color="#0000ff"
size="2"></FONT></SPAN> </DIV>
<DIV><SPAN class="968501119-28032004"><FONT
face="Arial" color="#0000ff" size="2">Just
mention the framework classes involved and I can go and have a snoop
around...</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV></DIV>
<DIV class="OutlookMessageHeader" lang="en-us"
dir="ltr" align="left"><FONT
face="Tahoma" size="2">-----Original
Message-----<B>From:</B> Stuart Booth [mailto:lists@xxxxxxx]
<B>Sent:</B> 28 March 2004 18:39<B>To:</B>
xAP_developer@xxxxxxx<B>Subject:</B> Re: [xAP_developer] RE:
Slim Conduit Feature request vs. GUI Plugin bits feat. MC Booth and the
plugin boys</FONT></DIV><TT>On Sun, 28 Mar 2004 17:06:00
+0100, "Edward Pearson"<edward.mailgroup@xxxxxxx>
wrote:>wish - it'd be nicer to get a call from the runtime when the
properties have>changed (dialog was Accepted not cancelled) - right now
I have to do all the>actions resulting from the change in the OK button
click handler of the>dialog which feels a bit messy (there's serial
comms, unit detection etc>going on)What I do is setup an event handler
that monit
ors changes to theconfiguration file. I check the event to see if it
contains details ofsomething I'm particularly interested in, and if it
does, I look atthe new value contained in the event and update myself.This
is how I propagate changes to the SlimServer the Connector isworking with
around the system. It then disconnects from the currentSlimServer and binds
to the new SlimServer.Anybody that is talking to the SlimServer can then
detect thisparameter changing and react accordingly. This change could come
fromanything, be it a dialog edit, an external file change, a toolbaredit,
or even an inbound targetted xAP message. Each of these changesthe
configuration settings and the event that this change generatesdrives the
rest of the update.All this is currently available from xFx and its
associated DLLs rightnow - you just need to know where to unlock this I
guess. More soon...S-- Stuart Booth <stuart@xxxxxxx>xAPFramework.net
- a xAP software development framework for .net<A href="http://www.xapautomation.org/";>http://www.xapautomation.org/</A>
<A href="http://www.xapframework.net/";>http://www.xapframework.net/</A></TT>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|