Now, imagine I do:
A) Click on the red X while the program is frozen. Nothing happens, until the program unfreezes. Then BlueMaemo quits.
B) Wait, doing nothing, while it says "Trying to Connect to Mac". Something I never wanted to do in the first place. Once thats done, I go to 'Open Connection', fire up the hidd command on Linux, and voila -- I'm connected.
Ideally this should go much quicker. The need of hidd command on GNOME is not a problem due to your program, but what I described above is. IMO this is not logical for a user either. I've tackled what happens; but its odd behaviour IMO.
Well if you choose the auto-connect option, you probably don't expect wait or take other actions in the initial screen's, IMO.
But I agree with you that the cancel button in the auto-connect screen should redirect the user to the initial screen.
I can't make it work on MacOS Leopard. I'm having the same problems mfortner previously had.
I am able to connect to the n810 and MacOS does detect a bluetooth mouse and keyboard.
Both a bluetooth mouse and a bluetooth keyboard do show up in "Input devices settings" in MacOS.
Despite this, bluemaemo keeps showing the "Waiting for connection ... " screen.
I have tried in Windows and Linux and I didn't have this problem. It worked fine in those OSs
Anyone can give me a hand to make it work in MacOS?
Thanks in advance.
Gourmand, esc is the back key on the tablets (the one with the curved arrow).
Man, I know - but when I watch movie in the dark room i'ts much better have Esc in virtual keys
Originally Posted by
If you know EFL, you can
is that about Enlightenment? didn't work with it before...
where are picture files live? I suppose I can just change them, ya?
why not put out all key and picture assignments to one (or two) XML file(s)
sorry - if only I wrote this program, I'd create one structured XML file to describe control tree - with one background picture for each branching point (with possible images, texts etc), and with two pictures for each terminal (key) - one for pressed and one for released
in the XML there can be key combinations assigned and described key image positions and image filenames for each branching point like this: xpos, ypos, pressed_file_name, released_file_name, key_code(s)
program code for a such structure becomes fairly simple
but this just about how I see this program internally...
BTW: I'd like write another one suggestion - add ability to remote start assigned applications (for example run media player etc) - this can be done using "global macro" keys on host system, but this requires completely editable menu tree
why not put out all key and picture assignments to one (or two) XML file(s)
sorry - if only I wrote this program, I'd create one structured XML file to describe control tree - with one background picture for each branching point (with possible images, texts etc), and with two pictures for each terminal (key) - one for pressed and one for released
in the XML there can be key combinations assigned and described key image positions and image filenames for each branching point like this: xpos, ypos, pressed_file_name, released_file_name, key_code(s)
program code for a such structure becomes fairly simple
but this just about how I see this program internally...
BTW: I'd like write another one suggestion - add ability to remote start assigned applications (for example run media player etc) - this can be done using "global macro" keys on host system, but this requires completely editable menu tree
I noticed that BlueMaemo after auto switching BT off keeps N810 "visible". I don't like this so much... Please fix it. Othervise I have each time after using BlueMaemo switch N810 to standard mode, go to BT settings, turn off "visible". So annoying...
