[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ gpsdrive ] feature request: fullscreen map



> > On Sat, 2007-02-03 at 08:44 +1000, info@4x4falcon.com wrote:
> > > Hi David,
> > >
> > > The changes stretch the map image whereas the maximise button does not.
> > Ok I see what you mean now.  By streaching out the image the way you
> > mention do track and waypoints still get drawn in the correct place?
> 
> I havn't followed the discussion completely. But we should not try to strech
> 
> the images with other functions than the zoom and size values.  The reason 
> for this is, that it would make a switch to grass/gdal even more complicated.

I probably did not put this very well.  It does not change the map itself what 
it does is increase the size of the map window. So you see more of the map 
displayed and it shows up in the small map window correctly as well.  Try it 
and see.


 
> One thing however would be great. If someone would be abel to catch the 
> gtk-resize-window event and try to adjust the picture size variables 
> appropriate. This way we could resize the gpsdrive window after having 
> started.

See below.

 
> > The calculations behind matching up the tracks and waypoints for
> > different scales and projections are quite complex and I'd be supprised
> > if everyting still worked.
> 
> That's  true. I wouldn't classify it as complicated, but as historically 
> grown ;-)

Using map_ projection it displays tracks and waypoints perfectly.  ie I have 
it on my laptop with a usb gps and drove accross three maps I have and it 
displayed the track exactly over the roads I drove on and changed maps as 
required.  I have not tried it with any top_ maps as I don't have any in this 
projection.  (Someone got any for north queensland between Mackay and 
Townsville.)



> If you want; this part of the code can be moved out with code change by 
> someone else and you can then develop in this file.
> 
> > >From previous discussions here adding new values to the gpsdriverc file
> > seems to be preferd over adding more command line options.
> 
> I personally would really prefer to see the --geometry parameter working and
> 
> would throw away the -s and -r options for this.
> <Wishlist>If we then also could ask the windowmanager about the desired 
> default setting for our programm and act on these it would be 
> great</wishlist>

Ok.  I've now got the geometry being read in from the command line and 
adjusting the window size correctly.  Hovever it does not yet correct the 
displayed map size and is the same as when you maximize the window and this is 
probably associated with the gtk-resize-window event.

It's not as --geometry just -g at this stage as need to change to getopt_long
() function as well.


 
> > > Unfortunately it's been about 15years since I have done any C
> programming
> 
> This sounds good. You even where programming C some time ago ;-)

Still been programming (mainly perl and php) during this time as I 
predominantly develop web applications and user interfaces to databases.  
That's one reason I started playing arround with the display for gpsdrive to 
get it more to how I wanted to see it on screen.

> 
> > > and have never used automake/autoconf etc 
> 
> If you have any problems with automake/autoconf. Just tell us. we can 
> hopefully solve this together.


I think I have automake/autoconf sorted now after reading through the 
documentation for them.  Nothing much else to do when you are flooded in.


> > > and I'm still coming to terms 
> > > with using svn so don't want to move it to another file just yet.  
> 
> If you want to I can start the new file for you and make all the 
> automake/include/external changes you probably need for this. Just make a 
> suggestion for a new Filename.
 
If you create the files display.c and display.h that should do.  No need for 
any functions etc in them as I'll need to work out what is needed in them as I 
go.

What I have so far worked out with the parse geometry changes is that it 
needs to be in gpsdrive.c anyway but other display setup and resizing parts 
should be in a separate file so easy to separate out from the functionality of 
the program.  I guess this is part of the code clean up on the wish list, I am 
happy to work on the display/user interface section.

 
> > My understanding of svn is that is has all the standard functions of CVS
> > with a whole lot of extra features.  If you only have anonamous acces to
> > svn you can create a patch of your sugested changes and if it all looks
> > good someone on the list will apply it to the source and submit it for
> > you.

Thanks.  I had not even used CVS before so like I said its still a learning 
exercise.
 
> That also my understanding. So the only commands which are probably 
> interesting for you are:
> 	- svn co http://svn.gpsdrive.cc/gpsdrive/trunk gpsdrive-work-1
> 	- gpsdrive-work-1 ;svn up
> 	- gpsdrive-work-1 ;svn diff

Can you explain what these commands do.  It's easy to type them in parot 
fashion but if I don't know what's supposed to happen then how do I know if 
somethings gone wrong.


Regards
Ross



----------------------------------------------------------------------
This mail sent through Horde-Toaster (http://qmailtoaster.clikka.com/)
-- 
This message was part of the gpsdrive mailinglist
unsubscribing can be done by sending a mail containing a body of:
-quote--
unsubscribe gpsdrive
-unquote--
to majordomo@warbase.selwerd.nl