For a more complicated scenario: mblsha, Monster and mbl-revolution are all sitting in same room. If you write m and press Tab it will not result in any noticeable action. This is because there are multiple nicks that start with m, and you can either continue to Tab to loop through all nicks that start with m or write more letters until there is a unique completion. When you press the b button, and then press Tab it would complete to mbl. The more you use this feature, the more you are likely to come to like it and rely upon it. Try nick completion on someone and you’ll realise how powerful it is.

The ones who have already tried Psi/Mac 0.11-beta1 probably noticed the sudden appearance of many little bothersome icons in all kinds of menus where they weren’t present in 0.10: icons in context menu, application menus and even in the menu bar itself! So it was decided that icons should not be able to live any longer.

With the help from kind engineers from Trolltech I discovered very handy one-liner that disables icons in the menu bar. I’m currently in a good mood so I will share it with you:

#ifdef Q_WS_MAC  
        qt_mac_set_menubar_icons(false);  
#endif

And the other half of the work — disabling icons in menus that are drawn by Qt — was done in a matter of minutes though overriding QMacStyle with my custom class.

And here is the sample screenshot from the running application:

Popup menus never looked this good before ;)

So what’s so new and exciting? Well, several things, and I’m going to list all of them here:

1. Ctrl-C and Ctrl-Ins shortcuts used to copy text are now more intelligent: if you have selected some text in chat log, and no text is selected in chat edit, and focus is in chat edit widget, these shortcuts will select the text from chat view. Sounds a bit complicated, but in reality probably you will start to use Ctrl-C shortcut more often.
2. When you select a region of text, emotions are also correctly selected, as shown on provided screenshot.
3. Selection is not lost when new text is appended to chat log. Very useful in Groupchats.
4. Also finally emoticons are copied correctly when you you issue Copy command. No more empty space instead of copying emoticon’s text.
5. Quite minor, but could also be useful: in Groupchat dialog there’s a handy nick completion, and now Undo command behaves correctly after you try to complete nick.

P.S.: And in case you’re wondering: no, it’s not Mac OS X shown on above screenshot. It’s actually Linux with custom window theme and unimpressive fonts. Emoticon package is called puzazBox.

But how to actually use it? The rest of the post will serve as the first bits on topic and as a reminder to myself. Be careful, it contains some techie stuff.

There was some background thinking, and we assumed that the best structure of directories would be like this: each directory with some C++ code in it would contain subdirectory named unittest, and there would be a base test directory, named unittest too, and it contains some helper scripts and files.

In order to run all available tests simple make check should be enough, and you’ll instantly see if something gone wrong.

There’s also a make valgrind target in order to run valgrind on test subjects (also as an added bonus, you could make valgrind even the Psi itself, and it would use the usual suppression file, and other useful tracing options). And if you get too many errors (and leaks, which sadly happen quite frequently with X11), make valgrind_supp to the rescue! It will generate suppressions that you can put into psi/unittest/valgrind.supp for later reuse.

In my grand plan all code (even Iris) should be tested, but as I’m probably the only one who’ll be working on it, it won’t happen very soon.

But if someone occasionally volunteer into writing some tests, here’s a small overview of the process:

1. Create unittest directory somewhere, and add relative path to it into psi/unittest/tests.txt, then run psi/unittest/update.rb script to update helper files (I hate duplicating efforts).

2. Create a qmake project file in that directory, which should follow this template:

   # unittest helpers
   TARGET = testname
   CONFIG += unittest # this way you'll save a bunch lines of code
   TESTBASEDIR = ../../unittest # relative path to the base 'psi/unittest' directory
   include($$TESTBASEDIR/unittest.pri)
   # test suite's source
   SOURCES += testname.cpp
   

3. Create a .cpp source file, according to the QTestLib Tutorial, and you’re set.

4. Now just run make check to compile and run the test. Simple.