Comment 31 for bug 702829

Revision history for this message
Thiago Teixeira (tvst) wrote :

Just to clarify: you are correct in assuming that I do not experience this buggy behavior when using a single screen. I use Cardapio on 3 very different computers and never encountered this issue before.

But since I *do* experience something very similar to this bug when using 2 screens, I will, of course, keep trying to fix it as I mentioned before :)

And, of course, you are more than welcome to go look into the code! I will answer any questions you may have, just post them here as they come up.

To get you started, the methods that may be of interest to you are:

- /usr/lib/cardapio/cardapio --> cardapio_show_near_docky()
This file is the main executable for Cardapio, and the cardapio_show_near_docky() method is what gets called when you click on the Docky anchor. This ultimately calls the two methods listed below.

- /usr/lib/cardapio/docky/DockySettingsHelper.py --> get_best_position()
It would be good to know what values that method is returning for you. For this, you can run Docky from a terminal and then use Python's "print" keyword to print values into that same terminal.

- /usr/lib/cardapio/Cardapio.py --> restore_dimensions()
This method is used to resize the Cardapio window and place it in the right location on the screen (which now makes me realize that its name is not really very good. I guess I'll rename it later on). There are all sorts of other important methods called from here, like choose_coordinates_for_window() and get_coordinates_inside_screen(). Another useful one that is called from here is move_main_window(), which actually belongs in the file CardapioGtkView.py.

That's it! Thanks for offering to help out, and let me know if you need anything else. I will keep looking into this issue from my side.