📄 readme
字号:
This is "qtmico" alias "korba", a qt/mico-adaptor. It is havily basedon the a x11/mico-adaptor by Kay Roemer and was modified by Lars Doellefor Qt 1.1 or newer. I (kay) changed qtmico.* to get along withoutpatching Qt. This required an ugly hack which will go away when Qt 1.3is released.// Examples ////////////////////////////////////////////////////////////// qthello1 runs a server and client without using micod. qthello2 uses micod, that is you can terminate the server by closing its window and the next invocation from the still running client will then activate a new server and restore the Hello object.// State of the implementation /////////////////////////////////////////// Allmost done. This runs with multible clients, too. I was also able to validate the client operations using the micod. I could validate that Q_OBJECTS and *_impls go well together by multiple inheritance. This is usefull when working with qt. The eventloop is placed such, that both server nor client consume idle time. The remaining major concern has to deal with the execution loops. These are both started by MICO *and* QT for several reasons. I feel quite confused about this topic, since i do not understand precisely, when these loops are started (especially in MICO). To have things running smooth, they must be made properly interoperating. Further, i feel, that the package should offer it's own 'exec', but i'm too unexperienced (both with qt dialogs *and* with mico) to be able to design a proper interface, that matches the needs of both packages. So i expect things to be changed most likely in this area.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -