Marker Details

[GoogleCodeExporter]

Hallo,

i'm a python newbie, so can somebody help me with the marker?
i would like to have maker with tooltips or something where I'm able to 
store details to the markers(e.g. name,...).


lg s

Original issue reported on code.google.com by sebastia...@gmail.com on 18 Aug 2009 at 6:06

[GoogleCodeExporter]

 Once upon a time I was a python newbie, and there are many many things a newbie could 
do, if you are interested we could help you get started...

I started working on some tooltips on Issue 36, take a look that might get you 
going.

Auf Wiedersehen 

Original comment by heldersepu on 18 Aug 2009 at 11:23

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

thanks!
my problem is, how i connect a tooltip to a pix_buf (marker drawing)
can you give me some references or tutorials!

i only know to add buttons tooltips.

i start to read and understand the cheesegame

serwas ;)

Original comment by sebastia...@gmail.com on 19 Aug 2009 at 6:53

[GoogleCodeExporter]

Now that I think about it, the "map" is a gtk.DrawingArea() and we draw the 
tiles, 
marker & GPS on top of it.
 Honestly I have no idea if a tooltip can be connected to a section of the 
DrawingArea; we could potentially draw out own "tooltip" but are we reinventing 
the 
wheel?

 I will recommend you to look at what other project are doing see if it can be incorporated.

Original comment by heldersepu on 19 Aug 2009 at 11:15

[GoogleCodeExporter]

the drawingArea object cannot connected to a tooltip
i thing i have to implement a custom widget with draws and store the data in a
tooltip. i haven't got the howto to this.
is it posible to but a button on the map with x and y coordinates?

a workaround was to add a mouse event (java=listener) and on click i calculate 
the
coordinates with the resolution and the mouseposition. if there is a marker i 
display
the information in a textbox!

what's your opinion?





lg sebi

Original comment by sebastia...@gmail.com on 21 Aug 2009 at 8:56

[GoogleCodeExporter]

i also read that gtk.eventbox is able to responds to mouse clicks,

Original comment by sebastia...@gmail.com on 21 Aug 2009 at 9:02

[GoogleCodeExporter]

the data for the tooltip could be read from the "markers" file see:
def read_file(strInfo, filePath): 
http://code.google.com/p/gmapcatcher/source/browse/trunk/src/fileUtils.py

Of course there is a way to display any widget at any location  gtk.Fixed()
this is an example:
http://www.zetcode.com/tutorials/pygtktutorial/customwidget/

we already have many "events" (signals is the proper name) in the drawing area, 
you 
could try one of those, see all the "da.connect(" in the def 
__create_right_paned(self):
http://code.google.com/p/gmapcatcher/source/browse/trunk/maps.py

Have Fun...

Original comment by heldersepu on 21 Aug 2009 at 12:57

[GoogleCodeExporter]

thx 4 the links!

can i get some help with the maputil "class"?
i have the mouse coordinats x,y and i would have long and lat.
so i calc. the offset beween the mouseposition and center.
i get the coordinats from the center but i don't know the scale for 
multipication the
offset. is it km_per_pixel(coord)??

is this the right way to get the mouse coordinats?


lg 

Original comment by sebastia...@gmail.com on 26 Aug 2009 at 10:39

[GoogleCodeExporter]

If I understand correctly, you want to convert from "mouse coordinats x,y" to 
"long 
and lat"

I give you a hint :)

 There are a few times when we use the "mouse coordinats" such as when user double 
clicks on the Drawing Area to Zoom In in that case we do_scale(to the pointer).

Is it OK if I add you as a developer to the team?

Original comment by heldersepu on 26 Aug 2009 at 12:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Let's take a step back...

We have 2 things that we need to compare:
 - the (x, y) coordinates from mouse
 - the (Lon, Lat) from the marker 

I will recommend you converting the Marker to (x, y) coordinates, we already do 
that 
when we draw the markers, look at def draw_overlay.

hope that helps you

Original comment by heldersepu on 28 Aug 2009 at 1:31

[GoogleCodeExporter]

Issue 125 has been merged into this issue.

Original comment by heldersepu on 12 Feb 2010 at 1:04

[GoogleCodeExporter]

Issue 131 has been merged into this issue.

Original comment by heldersepu on 22 Feb 2010 at 1:25

[GoogleCodeExporter]

Issue 127 has been merged into this issue.

Original comment by heldersepu on 4 May 2010 at 2:26

[GoogleCodeExporter]

Since markers file is tab separated, it will be tricky storing marker details 
into the same file. Will work on tooltip for markers and need suggestions for 
storing marker details.

Original comment by benx...@gmail.com on 27 Sep 2011 at 5:17

[GoogleCodeExporter]

markers file can use any separator, It actually works without separators, that 
is 
because we read using regular expressions.
See def read_file here:
http://code.google.com/p/gmapcatcher/source/browse/trunk/gmapcatcher/fileUtils.p
y

I used Tabs for readability but that is all.

Original comment by heldersepu on 27 Sep 2011 at 5:26

[GoogleCodeExporter]

Issue 165 has been merged into this issue.

Original comment by heldersepu on 13 Oct 2011 at 8:26

[GoogleCodeExporter]

Issue 140 has been merged into this issue.

Original comment by heldersepu on 13 Oct 2011 at 8:39

[GoogleCodeExporter]

Issue 253 has been merged into this issue.

Original comment by heldersepu on 13 Oct 2011 at 8:43

[GoogleCodeExporter]

I just submitted changes that I am using in my own copy of gmc, which I think 
is relevant to this issue. The change results in the nearest maker name being 
printed to the status bar when the map is click and when the mouse status 
option is selected under Settings. The changes only affect maps.py and are 
listed here:
https://code.google.com/p/gmapcatcher/source/detail?r=1525

Original comment by cjre...@gmail.com on 13 Oct 2012 at 10:26

[GoogleCodeExporter]

The changes in r1525 are fine, but we should start looking into moving away 
from drawing everything, instead we should use separate widgets so we can 
attach triggers and handle the click, right click, or any other mouse events.

Original comment by heldersepu on 13 Oct 2012 at 11:55