I like fridays, I think it’s the best day ever, your weekend ends, you are free, you are able to enjoy some beers, I just love it!. However I’m planning, this weekend, to finish MonoCanvas migration, I don’t really like being like this, I’ve haven’t yet finished this API, must be finished sooner! MUST IT!!!

BTW. I need to buy a new mouse, set some some details for buying linux-like stickers and printing XMI Specification. I can’t wait for tomorrow!!

Learning BASIC causes permanent brain damage. – Edsger Dijkstra

I’m currently rewriting MonoCanvas (Yes! One more time!!), but now using Gtk#, Gtk.DotNet, Gdk#, Pango# and GDI+, however that’s not the main discussion here. With this newer development I began writing some NUnit tests, that obviously assures compatibillity between revisions.

However with my most recent project I will code with ANSI C and C#, and I, obviously, will do Unitary Tests, so I need to get an application for doing that in C and I did it, is called Check (apt-get install check). So there I am, ready for coding!

I spent, yesterday, half-day receiving an explanation of my newest project at work, will spend one year coding a new C-and-C#-based application and, if everything goes nice, will code in Linux rather than QNX, I would love doing it in Linux, but both are nice OSs to play with.

In the other side I’ve, finally, set my xorg.conf to act as older, when I was able to scroll using touchpad, now click-and-move for selecting works and scroll also does, the trick is here:

Section "InputDevice"
	Identifier    "Synaptics Touchpad"
	Driver        "synaptics"
	Option		"CorePointer"
	Option        "Device"        "/dev/psaux"
	Option        "Protocol"        "auto-dev"
	Option "Edges" "1900 5400 1900 4000"
	Option "Finger" "25 40"
	Option "MaxTapTime" "180"
	Option "MaxTapMove" "110"
	Option "MaxDoubleTapTime" "210"
	Option "TapTime" "10"
	Option "ClickTime" "0"
	Option "EmulateMidButtonTime" "75"
	Option "VertScrollDelta" "100"
	Option "MinSpeed" "0.20"
	Option "MaxSpeed" "0.18"
	Option "AccelFactor" "0.0010"
	Option "Emulate3Buttons" "false"
EndSection

You also need:

Section "ServerLayout"
	Identifier	"Default Layout"
	Screen		"Default Screen"
	InputDevice	"Generic Keyboard"
	InputDevice	"Synaptics Touchpad" "AlwaysCore"
EndSection

I’m starting to think that we need to do some tests to MonoUML.

I still remember when programming in Java was nice and very efficient (before of C# of course), Gargabe Collector was (and still is), in that time (and before of that time) an awesome thing. However memory leaks aren’t like that, I mean, not literally, because later of using the objects and setting them to be finalized takes too much time being released. I remember that same behavior in Java’s GC when using JMF and the solution was the same. Nodaways while doing final performance tests in my current development, at work, and I notice this behavior. The solution is simple: System.GC.Collect(); System.GC.WaitForPendingFinalizers ();, but it needs to be used carefully, calling that two sentences everytime increases CPU usage and of course reduces application performance. The idea of using the GC every time needed (NOT EVERY TIME) (lets say every minute) stops “eating your memory“.

I don’t usually send emails to mailing lists that am subscribed to and wait for an answer, when I do is because I couldn’t find any solution to my problem or, in the other way, want to announce something (like our Mono Hispano ezine!). However I (think that) finally find the answer (’cause still needs further testing) for bringing-to-front widgets drawn in a Gtk.Layout, using the following code as primary sample:

using Gtk;
using System;

public class Sample
{
public static void Main ()
{
Application.Init ();
Window window = new Window ("");
Layout layout = new Layout (new Adjustment (IntPtr.Zero),
new Adjustment (IntPtr.Zero));
Button b1 = new Button ("1");
Button b2 = new Button ("2");
layout.Put (b1, 10, 20);
layout.Put (b2, 15, 15);
ScrolledWindow scrolled = new ScrolledWindow ();
scrolled.AddWithViewport (layout);
window.Add (scrolled);
window.ShowAll ();
Application.Run ();
}
}

You will notice the overlap of b2 over b1, if you switch lines b1 overlaps b2, however, there isn’t a solution for doing this after showing the Gtk.Window.

Solution? Use Gtk.EventBox, after reading gmane’s archive I figured it out! However I didn’t know Gtk.Button doesn’t owns a Gdk.Window, by don’t owning a Gdk.Window, Gtk.Button draws over anything (or any other Gdk.Windowless-widget) so, that might the problem am facing recently. Using Gdk.Window.Lower (), sends to back, Next code shows solution:

using Gtk;
using System;

public static void ButtonClick (object o, EventArgs a)
{
Button b = o as Button;
b.GdkWindow.Raise ();
}
}

Nice!. By the way, Rodolfo and I improved MonoUML a little bit, now MonoUML gots its history navigator

Después de la caida de 3 días del servidor donde estamos hospedados, enzo nos hizo el grandioso favor de ponernos de vuelta al aire, es extraño quedarse sin casa.

La base de datos de mediawiki esta corrupta, mañana con más calma y ganas haré la corrección por mientras hacía forge.novell.

GNOME 2.14 is here!!

I don’t like most recent Ubuntu‘s default theme.

BTW. I’ve finished MonoCanvas.Element’s implementation by subclassing from Gtk.DrawingArea, and it looks very nice.