Author
Topic: QOrbiter: Updated (Read 34647 times)

Create a new QOrbiter device as a child of the core. MAKE SURE to set the default user and location. Make a note of the device number

How do you do this? I know you can add qOrbiter from the Webadmin Orbiter page, at the bottom, but that creates the device as a parent. Once created I can see the template number (2186) but that gives the error "ERROR: the device template does not exist or invalid controlled via" when I try to add it as a child to the core.

How do you do this? I know you can add qOrbiter from the Webadmin Orbiter page, at the bottom, but that creates the device as a parent. Once created I can see the template number (2186) but that gives the error "ERROR: the device template does not exist or invalid controlled via" when I try to add it as a child to the core.

is your system up to date?

Also, what version of lmce are you running?

As far as bongo's question yes you will need to re-install for the moment when i update the apk

now off for my weekly swtor with friends!

-golgoj4

Logged

Linuxmce - Where everyone is never wrong, but we are always behind xbmc in the media / ui department.

OK- just an updated. I pulled down the latest svn (changeset 25456) and have great success on the HP Touchpad. Whereas before I had force the app to close to be able to get it to restart, now, it starts nearly 90% of the time on the 1st try. The other 10% i get stuck at a black screen and have to click a button to get back to the home screen.

Not so good with my samsung galaxy s2. I get the spashscreen, but then a black screen. When I rotate the from portrait to landscape, there is a white rectangle that appears. I would guess that rectangle is just where qorbiter isn't displaying an image. What's really odd, is on the 1st go at qorbiter after the update, the main UI appeared as expected, sort of. I was surprised not to see the phone UI and instead the desktop UI on my phone.

OK- just an updated. I pulled down the latest svn (changeset 25456) and have great success on the HP Touchpad. Whereas before I had force the app to close to be able to get it to restart, now, it starts nearly 90% of the time on the 1st try. The other 10% i get stuck at a black screen and have to click a button to get back to the home screen.

Not so good with my samsung galaxy s2. I get the spashscreen, but then a black screen. When I rotate the from portrait to landscape, there is a white rectangle that appears. I would guess that rectangle is just where qorbiter isn't displaying an image. What's really odd, is on the 1st go at qorbiter after the update, the main UI appeared as expected, sort of. I was surprised not to see the phone UI and instead the desktop UI on my phone.

FWIW

Im still hot on the case of the media grid problem. Thanks to sambucca, ive gotten some insight into how i need to approach it on this device plus im finding some underlying faults in my code that were not readily apparent in a desktop build for whatever reason.

-golgoj4

Logged

Linuxmce - Where everyone is never wrong, but we are always behind xbmc in the media / ui department.

I am trying to get a dev environment for this up and running, however there seem to be some recent updates to the qOrbiter class that haven't been committed to svn yet. Specifically on Saturday there was an update to orbitermanager that references a function registerDevice() in qOrbiter but there isn't any such function defined in the current qOrbiter class.

There are also a few signal and slot callbacks that aren't in the qOrbiter class that are referenced in the initial Q::Connect functions.

Let me know if this is just because the updates haven't been committed yet or if I am missing something else...

I am trying to get a dev environment for this up and running, however there seem to be some recent updates to the qOrbiter class that haven't been committed to svn yet. Specifically on Saturday there was an update to orbitermanager that references a function registerDevice() in qOrbiter but there isn't any such function defined in the current qOrbiter class.

There are also a few signal and slot callbacks that aren't in the qOrbiter class that are referenced in the initial Q::Connect functions.

Let me know if this is just because the updates haven't been committed yet or if I am missing something else...

They have been committed. Apologies but there is a bug in qt creator where it doesnt catch all the files that need to be submitted. Its been committed now though. Let me know if you have any questions!

Logged

Linuxmce - Where everyone is never wrong, but we are always behind xbmc in the media / ui department.

Domodude

Hi Golgoj, I run Dianemo on 11.10. I do not see the qorbiter template, and I get the same error when I just punch in the template number. Seems like it is not yet in Dianemo. Can you confirm that?Thanks,Mark