has anyone tried it on the htc hd2? So far no matter what resolution I put (currently n770) it never fits on the screen. Opera always zooms in...if I zoom out again, I can see that there is some cropping on the right side too.

Hi,

On my HTC desire I had to set zoom to "far away" (or something like that as my HTC is danish) in the browser settings to show it full screen.

has anyone tried it on the htc hd2? So far no matter what resolution I put (currently n770) it never fits on the screen. Opera always zooms in...if I zoom out again, I can see that there is some cropping on the right side too.

Hi,

On my HTC desire I had to set zoom to "far away" (or something like that as my HTC is danish) in the browser settings to show it full screen.

Seems to work well in Opera on the WebDT 366. Sucks to need a keyboard to login all the time. Not quite as responsive as the padOrbiter but pretty good. Not showing elapsed track time display in the remote screen.

Seems to work well in Opera on the WebDT 366. Sucks to need a keyboard to login all the time. Not quite as responsive as the padOrbiter but pretty good. Not showing elapsed track time display in the remote screen.

J

Performance would be improved by porting Touch Orbiter to the WebDT 366. Anyone up for that? ;-)

Can I just ask; is there a way to change the default room on the web orbiter? Whenever I open the orbiter, it seems to default to "Closet" (I assume because it's the first in the list of rooms alphabetically?) - can I change it to "Living Room" for example?

Or another suggestion/question, could it be set up to display the room selection screen first, so that you can choose? This would be useful for my mobile phone, as I could be anywhere when I use that.

Can I just ask; is there a way to change the default room on the web orbiter? Whenever I open the orbiter, it seems to default to "Closet" (I assume because it's the first in the list of rooms alphabetically?) - can I change it to "Living Room" for example?

Or another suggestion/question, could it be set up to display the room selection screen first, so that you can choose? This would be useful for my mobile phone, as I could be anywhere when I use that.

Hi Purps,

This is a bug in proxy_orbiter that we plan to fix soon...the bug makes the Web Orbiter default to the 'Room' that the Core or MD that has your ZWave interface is located in...it should default to the Room that the Orbiter has been set to default to of course.

Can I just ask; is there a way to change the default room on the web orbiter? Whenever I open the orbiter, it seems to default to "Closet" (I assume because it's the first in the list of rooms alphabetically?) - can I change it to "Living Room" for example?

Or another suggestion/question, could it be set up to display the room selection screen first, so that you can choose? This would be useful for my mobile phone, as I could be anywhere when I use that.

Hi Purps,

This is a bug in proxy_orbiter that we plan to fix soon...the bug makes the Web Orbiter default to the 'Room' that the Core or MD that has your ZWave interface is located in...it should default to the Room that the Orbiter has been set to default to of course.

All the best

Andrew

OK, thanks. Out of interest, what happens if you don't have z-wave? Would it then just default to the room containing the core?

Can I just ask; is there a way to change the default room on the web orbiter? Whenever I open the orbiter, it seems to default to "Closet" (I assume because it's the first in the list of rooms alphabetically?) - can I change it to "Living Room" for example?

Or another suggestion/question, could it be set up to display the room selection screen first, so that you can choose? This would be useful for my mobile phone, as I could be anywhere when I use that.

Hi Purps,

This is a bug in proxy_orbiter that we plan to fix soon...the bug makes the Web Orbiter default to the 'Room' that the Core or MD that has your ZWave interface is located in...it should default to the Room that the Orbiter has been set to default to of course.

All the best

Andrew

OK, thanks. Out of interest, what happens if you don't have z-wave? Would it then just default to the room containing the core?

Ignore that... I answered another question and got both responses mixed together! Your problem has nothing to do with ZWave :-)

But the bug is in proxy_orbiter and we are looking at a fix for it asap.

been using your weborbiter with great pleasure on my iphone 3GS,the thing i noticed is that the images get blurry, for instance the green area around a trackname gets 'artifacts' and the text isn't always readable,i did set the standard iphone resolution,

is there anyway to get this better?

br,Raymond

Logged

When you were born, you were crying and everybody else was laughing. Live your life so when you die, you are laughing and everybody else is crying.