27th December 2010, 02:14 PM
Easy to diagnose which..
If you send the xAP mute message manually from xFX Viewer does it work ? If not then likely to be a SqueezeServer plugin issue. If it does work then look at what is different in xAP Flash. Maybe it is sending the mute on press and then cancelling it again on release ? I.e. Not toggling
Low speed iPhone link only for a couple of days so my be erratic replies
27th December 2010, 11:37 PM
Automated Home Sr Member
Thanks, didn't know I could do that from xAPViewer.
Seems like xAP plugin not working...blast, don't think developer supports that anymore.
5th January 2011, 10:50 PM
Automated Home Lurker
Pages and buttons
Firstly, well done to all those involved in getting this project where it is, your effort is well worth it, and appreciated.
I've read through the documentation and this thread, and am just looking for some clarity on button usage. I've setup a page, similar to the one here, http://www.automatedhome.co.uk/vbull...58&postcount=3, when I click one of my menu buttons on the left hand side the relevant buttons/information is displayed on the main area. But if I then press a second different menu button, the relevant buttons/information aren't displayed. So a button only seems to toggle it's own grouped items.
I was expecting a different button press to hide/toggle a previous page and display it's own grouped items.
If I've misunderstood the button/toggle function, sorry. Can someone give me an example or explain what I need to do,
5th January 2011, 11:31 PM
Automated Home Lurker
Just a quick observation, the internal blue buttons don't centre their text or labels properly, they're slightly to the left. The black and red are fine.
6th January 2011, 01:15 PM
Last edited by Kevin; 7th January 2011 at 02:52 AM.
6th January 2011, 01:47 PM
Originally Posted by Boxing Orange
The modes pagehide, pageshow and pagetoggle are now deprecated although they do still work in beta 5. Instead the buttons should be set to <mode>link</mode> and then include the following within your button.
Now when you click on a button the matching page will hide/show. Make sure that your pages are all named with unique names. <type> is not currently used but may be later.
Pages in xAPFlash are always layered in the order that they appear in the XML - they are never re-ordered so if pageA appears before pageB it can never be displayed on top of pageB. However depending on the content / size of pageB some elements of page A might still show through from behind. Instead pageB should be hidden to fully display page A.
What I expect you are doing above is just showing pages and hence later ones obscure earlier ones giving the appearance the page link toggle isn't working (it is but it's hidden behind).
To make buttons and/or pages mutually exclusive so that buttons operate like radio station selectors or only one page is visible they should be grouped. Place each button in the same named group - same for pages. Buttons and pages are usually in different groups. eg for a group named 'leftmenu'
Grouped buttons will only allow one to be highlighted / active at any one time and pages will only allow for one of the pages within the group to be visible (automatically making others invisibleif needed).
This should give you the behaviour you are wanting.
7th January 2011, 02:24 AM
Just to reassure people that I am still working hard to resolve an issue that I have with beta 6 on the Joggler . This unfortunately involves an essential commercial component that I am using in the code and it isn't working (yet) on the Joggler. It does work fine on the PC and I am working with the developer to try and fix this, but they are unfamiliar with the Joggler where an app is contained within another Flash app and there is no 'stage' object. Currently on the Joggler the xAP app runs but upon exit the main Joggler UI is unresponsive so you have to reboot it.
Although I didn't have too much time over Xmas / New Year I should have a bit more next week when I hope to make progress. If I am still stuck I will likely post a beta 6 release for PC's only for those chomping at the bit.
I do have pending beta requests from a lot of people eager to go - please be patient. I haven't wanted to repost beta 5 because it will require you to rework your XML and graphics when beta 6 is released. Also I hope I've already caught most beta 5 issues and beta 6 is such a change internally that I just know there's many more things for you to discover there that'll need attention - so it'll be far more fun ;-)
25th January 2011, 11:11 AM
Automated Home Lurker
Just wondered how Beta 6 was coming along . I have just started down the hah route, what Derek and Brett have done with that piece of hardware is simply amazing, and xap flash will be the perfect interface for it.
13th February 2011, 03:25 PM
To keep you updated - I have a (Joggler only) issue that is requiring support from another commercial company and it's taking way longer to resolve than it should. As the Joggler is no longer available , and not supported by O2 / OP I can quite understand it's low priority. Very frustrating...
This doesn't effect the PC based version of xAP Flash and if nothing progresses shortly then I shall post this version of beta 6 for those that have a PC based interest.
Very frustrating - thanks for bearing with me...
14th February 2011, 07:46 AM
Automated Home Jr Member