Screenshots

[incoronado]

I have posted some screenshots of the system that I have created using Housebot here http://picasaweb.google.com/mike.larson ... omeControl I think it is sometime difficult for visitors to understand the exact potential of Housebot can do and how powerful it is. More than that most of these graphics provide both visual feedback and control with various systems. I'm really looking forward to 3.0. I hope Scott is thinking of adding even more functionality on the graphics side. wink wink.

My wish list...

* layered buttons / alphablending
* same buttons can both indicate and control or changed to indicate new status when pressed ***Really nice to have.
* some form of animation?

[ScottBot]

* same buttons can both indicate and control or changed to indicate new status when pressed ***Really nice to have.

Can't you do that now with multi-state property change buttons?

BTW, awesome graphics!

[incoronado]

You're right. Typing before thinking again. I don't know why I thought that. I'm using multi-state buttons for many things. I just remember running into limitations with using them. When I run accross the problem again I will make sure I pose the question.

Maybe I was thinking of this post...

It would be nice if HB 3.0 would allow the same objects to be used for status and control with the ability to turn off the sending of a serial command if it was the result of receiving a status command. It would also be nice if you could link received serial commands, or multiple commands, directly to a value without the use of tasks or scripts. Just seems like a logical progression of a good concept. That would be extremely useful and very efficient.

Also, I remember having a problem with using a group of buttons as radio buttons.

One other legitimate thing...

Support for non-rectangular buttons.

[vcruz77]

I am inlcuding a link with my updated screenshots: http://homepage.mac.com/victormcruz/PhotoAlbum4.html

I wanted to give it a Flash-based look so I combined graphics from the Housebot Library with some graphics (converted to png) from MainLobby. I am using Housebot for Home Automation (lights, security, cameras, sprinklers, etc.) and Media Player. For Music I am still using Meedio in a transparent screen. I know it is not a complete integration but it works great since I am using VNC in the Airpanels to access the server so the Client is always running in the server and not in the Airpanel. Connected to the server I also have a touchscreen panel that is wall-mounted in the living room. With this setup I don't need the media management capabilities to be integrated in Housebot. I will be trying the integration with Housebot thanks to Mike that has shared his hardwork.

Victor

[Richard Naninck]

* same buttons can both indicate and control or changed to indicate new status when pressed ***Really nice to have.

Can't you do that now with multi-state property change buttons?

BTW, awesome graphics!

I built my own status buttons where the button has a transparant hole in which an indicator is placed. This indicator can have it's own state independent of the button states.

Example:
Receiver DVD Source Button. Indicator colors (for states) are Green (DVD is selected AND Receiver is Power state On), Grey (DVD is selected or lastly selected, but Receiver Power state is Off) and Same color as button to blend in (DVD is not the selected source).

I could never do this with state buttons because the indicated state is independant of the button commands. Also I didn't map any commands under my buttons since they all address the same property "Action" and a script parses the commands. Therefore the states also get set by a script.
= DVD On (Green), = DVD Off (Grey), != DVD On (button color to blend in with button). All of this just requires a button with some transparant room in it for an indicator and some logic.

My request at the time was to give indicators a layer as well (just like dynamic and static images) so they could float on top of a button and get redrawn automatically after a button was pressed because they sit in a higher layer. Now I have to redraw they indicator myself (using the script again) to keep the indicator from disappearing underneath the button (even when the button has a transparant hole).

When I get home I need to check on how I managed the three states for the indicators and will report back. I think this is an interesting discussion since indicators and buttons are often used together and should be as flexible as possible. Having layer control over indicators, will fix many problems.

http://www.cebotics.com/phpbb2/viewtopic.php?t=855684

[Richard Naninck]

Also, I remember having a problem with using a group of buttons as radio buttons.

I have this working just fine. What is your problem? I might be of some help.

I take it you want to have a group of buttons where if you select one button, you deselect the previously selected one.
If so, you should put two states in each button.

Example: Using a calender with a repeat function and you have radio buttons for Hour, Day, Week, Month, Year

Hour Button:
State 1: = Hour
State 2: != Hour

Day Button:
State 1: = Day
State 2: != Day

Etc etc.
This way, selecting Day while previously having selected Hour, will deselect Hour because State != Hour and select Day because State = Day.

If this is not what you mean, please let me know what your problem is.

[incoronado]

I think I finally remember the specifics of my issue...

I was trying to create a series of 7 buttons aligned in a horizontal row that indicated A/V source on my receiver by placing a red box around the button/text. This is how my receiver indicates which source is selected. When I selected one of the other source images it would change the that graphic to having the red box and all other to the graphics without the red box. I couldn't get this to work consistently or without significant lag. I think it might have been a problem with the receiver both receiving and sending a status change affecting the state of the button. Richard has since given me a great tip/script that handles the send receive dilemma problem. Before that I was using tasks and mode to block incoming status changes from my receiver by disabling the mode/task before sending the command.