Re: [Pipmak-Devel] another way of measuring the mouse speed

[Christian W. <cwa...@gm...>]

Aidan Gauland wrote:
>  I see it does the same on my system, now that I look more closely.   
> But, I have NO IDEA where to start looking in the source code for  
> this one.  Maybe, not grabbing the mouse as soon as Pipamk starts,  
> but grabbing the mouse when it is moved into the window, just as  
> would be done for the rest of the session, would remove this  
> problem.  But when in the code does Pipmak grab the mouse for the  
> first time?

The first grab happens on main.c line 484, just before entering the  
main loop. I have no idea why that would prevent later ungrabbing when  
the mouse was outside of the window at that time. Let me know what you  
find out.

>  And what do you all mean when you say "revision 170".  I'm using  
> the source tarball I got from a link on this page:
> http://pipmak.sourceforge.net/downloads.php
> I'm sorry if this seems like a silly question, but I haven't been  
> involved with an open source project before.

Not a silly question. Welcome to the world of revision control, a very  
useful tool in collaborative (and even solitary) software development!  
A revision control tool stores the whole history of the source code of  
the project, it lets you go back and forth in time and review who did  
what, when, and why. It also makes it easy to review (and undo) the  
changes to the code you have made in your personal copy.

Pipmak uses Subversion (SVN) for revision control, like many other  
projects nowadays (Side node: I've played with the idea of setting up  
a Bazaar branch mirroring our Subversion repository at launchpad.net.  
Would anyone be interested in this?). A very good resource for  
learning about Subversion is the SVN Book ("Version Control with  
Subversion") at <http://svnbook.red-bean.com>.

To get started, you need to install a Subversion client. On Linux, you  
will probably want to use the command line client. You're on Debian,  
right? Try "apt-get install subversion".

Run "svn checkout https://pipmak.svn.sourceforge.net/svnroot/pipmak/trunk/pipmak 
" to download a copy of the current Pipmak source code. This will get  
you approximately what you have in your source tarball, but with the  
addition that you can run "svn status" to see your local changes, "svn  
update" to update to the latest code from the repository, "svn diff"  
to generate patches, and many more. You can't currently do "svn  
commit" to send your changes back to the repository (only I can do  
that), but I will give you that privilege if I come to the conclusion  
that your contributions are of sufficient frequency and quality that  
it would be more work for me to apply your patches than to let you  
commit them yourself.

   -Christian