Ideal Absolutes

Howto stop cairo-dock from hiding.

I realize that this screenshot does not show that it has stopped hiding, but I had already uploaded the images.

=)

First start by visiting GPH’s tutorial when you get to the part for to make clean, make (for the cairo-dock – not cairo itself) then follow below. I’m running this with fairly bleeding edge Edgy. If none of this makes sense then don’t worry and stick with metacity. How does this compare with Beryl & Kiba-Dock? This seems faster and more GNOME’ish overall.

cd /opt/cairo-dock

sudo gedit /opt/cairo-dock/cairo-dock.c

lines 713 and 821 (on my version) contain the following line:

g_uiHideHandlerId = g_timeout_add (15, move_down, (gpointer) pWidget);

simply comment them out to stop autohide:

// g_uiHideHandlerId = g_timeout_add (15, move_down, (gpointer) pWidget);

sudo make

./cairo-dock –no-glitz

while still in /opt/cairo-dock do this:

cp *.sh ~/
cd
vi *.sh

now change the path you see to /opt/cairo-dock

note that we are changing directory to /opt/cairo-dock and then the code runs ./cairo-dock –no-glitz

now save

alright, let’s add a button to the gnome-panel to easily start cairo-dock. right click on the gnome-panel and select Add to Panel. when the ‘add to panel’ window appears you will need to click on the second button ‘Custom Application Launcher’. when the ‘Create Launcher’ window appears fill it in like so:

Name: Cairo-Dock
Command: /home/macewan/start-cairo-dock.sh

now click the ‘OK’ button to close the ‘Create Launcher’ window and then click the ‘Close’ button to close the ‘Add to Panel’ window.

this will work. yes, you can just leave it in the /opt/cairo-dock area if you like.

*continued

if however you try to run from ~/ you might get scrolling error messages (shown below) with possibly no icons and an odd size to its background.

macewan@moc:~$ /opt/cairo-dock/cairo-dock –no-glitz

(cairo-dock:25282): librsvg-CRITICAL **: rsvg_handle_get_dimensions: assertion `handle’ failed

(cairo-dock:25282): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone’s code. You must ensure an error is NULL before it’s set.
The overwriting error message was: Failed to open file ‘clock.svg’: No such file or directory

(cairo-dock:25282): librsvg-CRITICAL **: rsvg_handle_get_dimensions: assertion `handle’ failed