Re: Join command & Subpage

Should this work even without a processor? Been having a heck of a
time trying to get subpages to work on a demo panel.

On Apr 24, 6:07 pm, Nahshon Williams <spc...@gmail.com> wrote:
>   You can have as many control points (buttons) as you like.
> What do I mean by that?
> Well you can have a button to show the page and another button to hide
> the page and another button  to do the same thing as often as you like
> so long as you have the same digital joins on all the buttons will act
> as one button.
>
> _*On way to do it*_
> For what you are trying to achieve. (show and hide more controls to your
> interface) A maximum of 2 buttons is ideal.
> You would put one button on the Main Page (Page A) let us call this the
> "More" button.
> Another button on the New Page (Page B) let us call this the "Less" button.
>
> The More button will have a digital join of say 7 (simulate feedback,
> Toggle).
> Page B will have a digital join of  7.
> The Less button will also have a digital join of 7 (simulate feedback,
> Toggle).
>
> The "active" state of both buttons should be labelled "Less" and the
> inactive state should be labelled "More" (you basically copy and paste
> the more button to page B as assume it is the less button)
> When you press the button Less is shown, when you release the button
> More is shown (but they are the same button in different states and places)
> You can have as many as you like. (but that would be silly)
>
> *One button or two?*
> The reason I suggested Way One was that apple use a navigation bar to
> reveal different aspects to their gui.
> When you go to the ipod application for example, u always have access to
> artist, album, songs and so on (at bottom of the page). The buttons are
> never obscured.
> So in this case only one button is needed in the toggle state to reveal
> and hide a page.  (well not exactly but I hope you get my point)
> (You can replicate the ipod app behaviour by using the feedback example
> in the wiki, I answered a similar question this week about feedback
> without a control system.)http://www.commandfusion.com/wiki/index.php?title=GuiDesigner:System_...
>
> *Back to this topic.*
> I prefer to use the full and small remote because I have *"maximum
> space"* (the whole page) and I do not to lose any functionality.
> So with the basic remote, I have navigation volume and channel control.
> (WITH BIG BUTTONS)
> Then on the full remote I also havenavigation volume and channel control
> and I can make the buttons as big as possible. Win win for me.
>
> Hope this helped
> Nahshon
>
> P.S.
> When you press the button,  the subpage will show. When you press the
> button again. The subpage will vanish.
>
> On 24/04/2010 21:27, Paul wrote:
>
>
>
>
>
> > Thank you very much Nahshon.
>
> > One question however - How do I then toggle back to the Basic Control
> > from the Full Control page if I do it using Way One?
> > Also, why do you prefer Way Two?!
>
> > On Apr 24, 9:17 pm, Nahshon Williams<spc...@gmail.com>  wrote:
>
> >> Hi Paul
> >> I do this all the time.
> >> Exactly as you suggest. . .
> >> Depending on what you want here are 2 ways.
>
> >> Way One
> >> Using a subpage which is smaller in size than the page in question (the
> >> page with the "more" button).
> >> So let us say you create a subpage half the size of the original page.
> >> 320px by 240px we will call this subpage b.
> >> You anchor subpage b to the main window and give it digital join ( say 7)
> >> Create all the extra buttons you want on subpage b and you remove the
> >> "visible" attribute to the subpage. (so it does not show when you start
> >> the app)
> >> You give the more button a digital join of 7, simulate feedback, and
> >> toggle. If the more button is still visible you can make the "active"
> >> text for the button less :)
>
> >> Now each time you press the "more" button, subpage b will appear. (you
> >> can select transitions on the attributes of the page)
>
> >> The second way is to have a mini remote and a full remote (this is how I
> >> do it).
> >> So I have basic navigation, volume and channels. Then things like
> >> brightness and contrast reside on the full remote.
> >> As above you select transitions and put a button on the main page with
> >> the same attributes as the more button.
>
> >> Good luck
>
> >> Nahshon
>
> >> On 24/04/2010 20:37, Paul wrote:
>
> >>> We want to be able to have a seldom used set of buttons appear when a
> >>> 'more' button is pressed.  Can we achieve this using the 'digital
> >>> join'&    'Subpage' capabilities?  Or can we achieve this another way?
>
> >> --
> >> You received this message because you are subscribed to the Google Groups "CommandFusion" group.
> >> To post to this group, send email tocommandfusion@googlegroups.com.
> >> To unsubscribe from this group, send email tocommandfusion+unsubscribe@googlegroups.com.
> >> For more options, visit this group athttp://groups.google.com/group/commandfusion?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups "CommandFusion" group.
> To post to this group, send email to commandfusion@googlegroups.com.
> To unsubscribe from this group, send email to commandfusion+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://groups.google.com/group/commandfusion?hl=en.

--
You received this message because you are subscribed to the Google Groups "CommandFusion" group.
To post to this group, send email to commandfusion@googlegroups.com.
To unsubscribe from this group, send email to commandfusion+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commandfusion?hl=en.