raisjn

awesome, thank you - i am trying it out, now! previously, i just used qmake (no need for qt creator) inside docker images, like in https://github.com/toltec-dev/toolchain/blob/v2.x/qt/Dockerfile

``` $ docker run rain92/kobo-qt-dev /launch.sh: line 7: 7 Aborted (core dumped) $executable $ docker run rain92/kobo-qt-dev -v .:/umr/ kobo-qt-dev /launch.sh: line 7: 8 Aborted (core dumped) $executable $ docker...

no luck for me :-( - still get the same core dumped message. i'll investigate more on nights and this weekend

thanks so much for the patience and the updated images! i'm able to compile for desktop through the docker image but having trouble compiling for kobo from CLI. some things...

thanks! in order to get qt creator displaying on my local machine, i had to run `xhost +` (disable access control) on the host machine before the guest could connect...

the intent is that Scene takes ownership by using shared_ptr when a raw pointer is passed in, but Scene can also take a shared_ptr to add(). the current ownership model...

> I think you could get the same behavior with Dialog if it kept a weak_ptr instead of a shared_ptr to InnerScene, to break the Scene -> Dialog -> Scene...

dialog as innerscene makes sense to me. the separate event loop is interesting but i don't want to implement that just yet

i spent some time last night looking at the hamburger menu and at other dialogs to get an idea of what's going on. to summarize (for my own benefit): *...

nice! is there anything rmkit can do to make the pattern easier / used in more cases? i think there could be ui::MainLoop::release(scene) (which does the simple check you have...