thanks - that works
Here is an example of a textbox using your schema and recovering the read messages number :
I have included a text prefix and suffx - I have used CDATA tags because there is a trailing and leading space required and this will be removed otherwise.Code:<textbox NAME="Asterisk_read">> <gridX>1</gridX> <gridY>4</gridY> <width>200</width> <height>60</height> <border>true</border> <alpha>0.8</alpha> <html>false</html> <visible>true</visible> <background> <visible>false</visible> </background> <fontcolour>0xffAA66</fontcolour> <textprefix><![CDATA[There are ]]></textprefix> <textsuffix><![CDATA[ read messages]]></textsuffix> <mode>text</mode> <xAP> <schema>generic</schema> <uid>FFE80003</uid> <source>liming.axc.house:vm.default.500</source> <generic> <Class>CTI2.info</Class> <body>Messages</body> <parameter>readmessages</parameter> <type>text</type> </generic> </xAP> </textbox>
There are 7 read messages (cf There are7read messages)
Also - you are recognising a CTI2.info message - I don't know how Gregs schema works but if there is a CTI2.event message then that is probably what you want - and I am not sure if you can query his schema at startup to solicit the current state - if not you will see the following displayed until a messages is sent.
There are read messages
HTH - I know we do need to get out some fuller XML examples....
Last edited by Kevin; 11th October 2010 at 02:14 PM.
I'll check this out and see if fixed IP is the way to go.
To be honest Kevin I'm not sure now what issues I'm seeing are Joggler, xAPFlash or HAH. I'm seem to be having issues with all three. i.e. just upgraded from classic CurrentCost to CC128 and after working fine at the beginning, it's now gone TU, SMS has stopped working and I'm getting random RF device switch offs.
At this point I don't want to be throwing spurious issues in that aren't xAPFlash related.
Also re the device status issue, Brett is re-writing the xAP library that the HAH uses, so I'll wait for that update and retest, I think it more likely to be a HAH specific issue.
The HAH is about to get a whole smarter as they're bringing in 2-way RF comms, a xap-serial interface to talk with external microcontrollers and an extension to xap-CurrentCost that allows for connection to CC dev boards.
I'll then be testing xAPFlash with xap-plugboard controlled screen changes, audible alerts, OSD(hopefully) etc. So will really be able to put beta5 through it's paces then. Expecting the HAH update soon.
** EDIT **
Fixed my SMS and Current Cost issues...user error!
So now just random reboots, random RF shutoffs. I'll try recording some xAP messages ans see what I can see.
Last edited by BodgeIT; 12th October 2010 at 10:25 AM.
I can't say I've seen this behaviour myself, and have tested pretty thoroughly where sliders are concerned!
A timestamp is taken when the button is first clicked (mouse_down) then a second is taken when the button is released (mouse_up), the difference is calculated and compared against whatever is set for the delay in your xml.
The popup event shouldn't fire if the elapsed time isn't the same or greater than the delay, I'm not sure what could be affecting that, but will do some more testing here.
Sorry..one other thing I did notice Kevin is that the Layout function has changed.
When I press the layout button, I see all the IDs as expected but then when I press a button that "pagetoggles" to another page, the layout function is turned off.
This never used to happen, I used to be able to switch through all my pages with the layout function still active.
Being able to page through your design within layout mode,and redraw the now visible tags is possible to do I guess, but it likely didn't work that way as coded and so leaving layout mode is a solution - however I didn't intentionally make it do that . I'll take a look
Gary has done some great work reformattting and proof reading some of the docs - thanks Gary
However they've evolved in a rather spurious way and we need to produce something more useful to new users and less Joggler centric. This is something that takes time, diverts from development and is always left to last minute , and hence delays releases, as it is now.
If anyone could help here we'd much appreciate it , it's a great way that a non coder but a good communicator could really assist.
I've been sitting down and trying to work out what items I want controlled from each Joggler/PC flash interface.
One of the things i'd like to do is control the RGB leds I have.
I think i could find an RGB actionscript colour wheel that outputs the RGB values (0-255) plus an intensity or luminance value.
What I was wondering is if this could be incorporated as a 'bolt on' SWF to the existing beta or whether you'd have to code something to allow it to work?
Do you currently allow an external button SWF to pass any values or not?
My thoughts are that it could work as a popup slider but with the colour wheel instead of the simple slider - just like this:
That's a bit too complex, but it's the general type of thing I mean.
What do you think?
The quick answer is no - an external SWF can display the 10 or so button states and can pass click on/off and long press information but that's about it. We don't currently support external SWF sliders and even if we did they are single channel only whereas your RGB wheel uses 4 or 5 analogue channels.
At some future time we might define an API for linking external AS3 based SWF's with xAPFlash and passing values, then if you have the Flash coding ability you could then create or adapt an existing FLA and use it. Handling 4 or 5 analog channels in a linked two way fashion is fairly specialised though. The SWF would really have to be AS3 as well.
Just considering this from the xAP side do you already have in place a xAP schema that can control and report /event the colour lighting ? Is this a BSC breakapart of the RGB channels or a specific colour schema ? If it's the former then you've also got the issue of generating multiple control messages , or even better multi body BSC messages which will provide coherent commands - and then synchronising back multiple event messages to one device status. Currently each button/slider has only one associated xAP endpoint / schema.
All in all it's a pretty specialised and awkward thing to implement - not impossible but custom. Maybe better to just have RGB presets (scenes) that you can trigger from buttons - which you could do already.
Many thanks Kevin,
I thought that would be the case - I guess I can use 3-4 individual sliders for now although it's a bit messier but doable I think.
Yes - I'm using Lehane's xAP DMX512 plugin with the milford inst DMX controller - that allows BSC control.
Not sure about reporting - never used that as this is the only control, so nothing else changes the RGB LED's and I've not needed status reporting yet.
I send single messages as each DMX channel is set to a R,G or B value for each light - not sure it supports multi-body messages - probably not I'd have thought.
A future API would be great to allow others to develop on top