At least for me the following behaviour is reproducable:
- open some Qt application which has at least one QComboBox or some menus on top bar to tap to
- run "killall hildon-desktop" or "dsmetool -k /usr/bin/hildon-desktop; dsmetool -t -U user /usr/bin/hildon-desktop"
Now try to get away without rebooting the device... only option is to killall the qt app(s) that were running in the background via SSH connection.
Is this a bug in Qt or is there another more "gentle" way to restart hildon-desktop than ones above?
To refresh the icons in Hildon launcher menu?
For me it's usual behavior.
Actually to refresh about everything (this is actually Theme Customizer related question) without having to reboot the device. Built-in theme choosen app (personalisation_app) seems to do this without actually restartin the hildon-desktop. If I only knew what that closed source app is doing when applying new theme I would be very happy.
Actually to refresh about everything (this is actually Theme Customizer related question) without having to reboot the device. Built-in theme choosen app (personalisation_app) seems to do this without actually restartin the hildon-desktop. If I only knew what that closed source app is doing when applying new theme I would be very happy.
So, in reality, you want to mimic, or replicate, the behaviour of another application?
Since dbus is used for many things, I'd suggest that you listen in on it while the other application "does its magic" to see what's happening. If you're lucky, it's a simple command that is sent that you then can implement in your own application.
If some other communication is used, you'll have to get more creative and that's perhaps too big a scope.
So, in reality, you want to mimic, or replicate, the behaviour of another application?
Since dbus is used for many things, I'd suggest that you listen in on it while the other application "does its magic" to see what's happening. If you're lucky, it's a simple command that is sent that you then can implement in your own application.
If some other communication is used, you'll have to get more creative and that's perhaps too big a scope.
I don't want to replicate the behaviour, but it would indeed be nice to know how the personalisation_app is doing the things.
I already tried scanning the DBus and there's no (extra) activity there.
