Keyboard layout switching in Qt, not just in Qt for embedded Linux
-
Thanks for the welcome.
I am using Qt 4.7.4 (32 Bit) and QtCreator 2.4.1.
I work on Ubuntu 12.04, 64 Bit on a Virtual Machine. -
There's something I'm not sure to follow. You wan't plug e.g. an QWERTZ keyboard and then change for e.g. an AZERTY and let Qt handle that ?
Another question, what window manager will you be using ? Ubuntu's unity ?
-
Yes, I want to let Qt handle it. I would've liked to just call some qmap-handler-functions like you can apparently do if you use Qt for Embedded Linux, but for some reason it's not that easy in other Qt versions.
The whole thing will run on a hardware with a specialized Linux-Kernel without Unity. The display is a permanent camera stream und Qt takes up a portion of the screen. I don't know how exactly this happens, but I can ask around if it's important.
-
Because it's not useful outside Qt Embedded since it's done e.g. through Xorg. But that doesn't answer the main question: what do you use as graphic server ?
-
We have no graphic server. We use an Atmel SAM9G45 board. On the following pdf on page 1052 is a block diagram:
http://www.atmel.com/images/atmel_6438_32-bit-arm926ej-s-microcontroller_sam9g45_datasheet.pdf
The "DISPLAY IF" output is connected to a display.
-
Seems like my last answer disappeared, did you got it ?
-
No, sorry, I didn't receive it. Can you post it again, please?
-
The question was: what will you be using (software speaking) to draw the video and the Qt GUI ? Linux frame buffer ? Also what distribution will be running on the device ?
-
We use the Linux frame buffer. It's a self-compiled distribution based on kernel 2.6.38 armv5tejl GNU/Linux (with udev).
-
Then if you don't have any graphic server/window manager and are using the linux frame buffer then you have to use Qt for Embedded Linux. Or there's something I'm missing
-
Ok, too bad. I guess we'll have to try to switch our Qt version after all.
Thanks for the help!
-
Before that, can you tell me what software setup you had planned ?
-
Can you elaborate on what you mean exactly?
-
Simple what are the software architecture you want to use. Until now you wrote that your were using a self-built distribution with a custom kernel and not wanted to use Qt Embedded, but don't have any window manager nor graphic server.
So what would your software stack be ?
-
I don't know the exact software stack, but our Atmel board has frame buffer support and that's what we use for the graphics.
-
So all in all quick version: -> kernel -> busybox -> Qt Application ?
-
Yes, that's right.
-
Well, then Qt for Embedded Linux is the only option. Why did you want to use it in the first place ?
-
Ok, we'll try that.
Assuming you were asking: "Why did you not want to use it in the first place ?"
Well, the project has been running for a few years now, requirements kept changing and keyboard layout switching was added to the specification just recently.I have a question about the tutorial on http://doc.qt.digia.com/4.6/qt-embedded-install.html:
How do I switch between my two Qt versions? I use Qt Simulator for simulations and when compiling our stuff on the hardware, we use a makefile without QtCreator. Do I only have to change $PATH?
If possible I'd like to keep the code working for both versions by using a #compileflag -
Indeed, the was a word missing :D
Just create one kit for each Qt version and use both for you project, then you can switch at will from Qt Creator