> Where is klog? I haven't found it in any console/terminal. Let mi elaborate about this in a little more detail. I already described in the main email that if there is some application running in the console and such application is not aware of possible resizing during its lifetime, its layout will break. Apart from bdsh (where I added some experimental support), all interactive applications (klog, tetris, edit, top, ...) are suffering from this limitation. However, if it is necessary to resize the console, you can terminate the interactive application, resize the console and then start the application again.
Another problem arise when you close the console in which there is some application running. If the application is not prepared to support such event, it will simply stay running in the background and often cause something to go into infinite loop, because the whole system significantly slows down (you can try this by e.g. closing console window with running tetris). Similarly as with resizing, I added support for termination into bdsh and getterm, but other apps were out of my scope. So you should always close applications in all console tabs before terminating the vterm application, otherwise the system will likely become practically unusable. Now, klog of course does not support resizing, but more importantly, it cannot be terminated because there is while(true) loop in its main(). And when one klog is running, you cannot start another one because it was always considered as system singleton. So I decided it would be better in current situation to start just getterm instances by default. User can always run klog application in one of the console tabs if it is needed. However if you would insist that klog should be running by default, it could be done by changing single logical value in the vterm application source code and recompiling the system. > When playing tetris 90 deg rotated, a single-pixel line remains drawn > in previous position of the falling block. Screenshot is attached. But > I am not sure that this is not something related rather to Qemu than > to your server. I am also not sure. But my guess is that it is caused by off-by-one error in damage region calculation inside console server. Another suspect is nearest-neighbor filtering when it is applied on damage region coordinates. I will look into it when I will resume working on my thesis, which I have to put aside for some time because of other commitments. So for now, let's consider it a known issue. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
