Closed GoogleCodeExporter closed 9 years ago
the problem persist also after a udig restart.
Original comment by mesca...@gmail.com
on 23 Mar 2011 at 3:01
p.s. the database was created with 1.0.2 beegis version and the new annotation
is drawn with 1.0.3-1 version.
May be that there's a change in the way as annotation is stored in database ?
Original comment by mesca...@gmail.com
on 23 Mar 2011 at 3:05
No, there shouldn't be problems with the version. Would you mind to send me the
db in order to reproduce the problem. I had to change a couple of things in the
annotations drawing in order to remove the strange line that appeared, it is
possible that I didn't fix everything.
Original comment by andrea.a...@gmail.com
on 24 Mar 2011 at 6:47
The database in in the 2011.03.zip file
Original comment by mesca...@gmail.com
on 24 Mar 2011 at 8:06
Outch, thanks, I didn't see it. On it.
Original comment by andrea.a...@gmail.com
on 24 Mar 2011 at 8:08
As usual we are not lucky enough to make it happen also for me :(
I do not miss any annotation. Tried to zoom around like hell and change the
scale factors like crazy. No way to loose pieces around.
Do you have any more info about how I could reproduce that?
Original comment by andrea.a...@gmail.com
on 24 Mar 2011 at 12:55
Attachments:
mmm... the problem for me persist and is not linked only to zoom scale but also
with position. When I pan from a position to another, at 1:15000 scale for
example, the annotation appear and disappear. I'll try to keep this bug under
observation in the future so I can give you more details.
Original comment by mesca...@gmail.com
on 24 Mar 2011 at 8:19
Could you try to run udig as:
udig.sh -consoleLog -debug
and see if errors are thrown once the lines disappear?
Original comment by andrea.a...@gmail.com
on 28 Mar 2011 at 8:12
does it work also with udig.bat ?
Original comment by mesca...@gmail.com
on 30 Mar 2011 at 2:21
ok, the problem is due to the projection system. If I use the map view in
WGS84(DD) it works fine, but when I change the map projection to WGS84/UTM32
(32632) the problem magically reappears.
I can't move to the debug mode for windows. I try to modify the .bat like this:
@call C:\Programmi\OSGeo4W\bin\o4w_env.bat
@set GDAL_DATA="%OSGEO4W_ROOT%\apps\udig-dev\gdal_data\"
@set GDAL_DRIVER_PATH=%OSGEO4W_ROOT%\bin\
@start /B "uDig-dev" "%OSGEO4W_ROOT%\apps\udig-dev\udig_internal.exe" -vm
"%OSGEO4W_ROOT%\bin\javaw.exe" -Xmx400m %* -consoleLog -debug
is it correct ?
Original comment by mesca...@gmail.com
on 30 Mar 2011 at 2:39
Yes your change is correct and should work.
Anyways I will check into the crs problem. Good catch. If I solve it I make a
release with the new splashscreen.
Original comment by andrea.a...@gmail.com
on 30 Mar 2011 at 8:21
Can you define a workflow?
I.e. you draw the annotation in which projection and then when transforming to
which projection do they disappear? That would help.
Original comment by andrea.a...@gmail.com
on 31 Mar 2011 at 7:20
ok. I always work in the same projection system (32632) an I notice that at
some scales or with some positions the a annotations disappear. If I move to
the general projection (WGS84-DD) the annotations is always drawn at all scales.
Original comment by mesca...@gmail.com
on 31 Mar 2011 at 8:14
I am not able to reproduce this. grrrr. Tried to reproject back and forth. No
way to get annotations lost. Any luck in the console log?
PS: a new verson with splashscreen and own icon and launcher is up in osgeo4w.
Can you try it?
Original comment by andrea.a...@gmail.com
on 31 Mar 2011 at 12:31
the starter doesn't work.
you must change the field "da:" from '\' to a valid windows directory as
'C:\Programmi\OSGeo4W\apps' or 'c:\'
Original comment by mesca...@gmail.com
on 31 Mar 2011 at 1:58
What do you mean?
It works for me and also all the udig start links have the "da:" set to '\'.
Can you check the uDig ones?
Original comment by andrea.a...@gmail.com
on 31 Mar 2011 at 2:31
Original comment by mesca...@gmail.com
on 31 Mar 2011 at 2:49
Attachments:
Hmmmm, this seems more a problem that with the cd command it doesn't change the
drive. Can I ask you to add to the beegis.bat that is executed one line before
the
cd "%OSGEO4W_ROOT%\apps\udig-dev" line
that simply does: c:
The two should then change to c: disk, and then be able to do the cd to the
folder.
Original comment by andrea.a...@gmail.com
on 31 Mar 2011 at 2:53
OK, i understand the problem:
you have to use the full path like :
'%OSGEO4W_ROOT%\apps\udig\udig_internal.exe'
to start the program.
If you want tu usethe command 'cd "%OSGEO4W_ROOT%\apps\udig-dev"' you must add
a row in bat with command c: 'cause if your shell doesn't open itself in c:\
disk but in another disk (for me z:) the batch doesn't work
Original comment by mesca...@gmail.com
on 31 Mar 2011 at 2:59
Yes exactly. It doesn't happen for udig, because only beegis needs to be
customized to have its own splashscreen. And it only works if I launch the
program from within the installation folder. Hence the decision to do the cd to
the folder.
I am glad that your configuration is a bit particular, else I would have never
noticed that.
I will add the c: on the line above the other. But then I am not sur ethat one
will have installed osgeo4w in the C: disk. What if one installs it in another
disk? Then with c: I would break it.
I will ask in the osgeo4w list. I'll let you know. Anyways you confirm me that
by adding the c: it works?
Original comment by andrea.a...@gmail.com
on 31 Mar 2011 at 3:05
I got some help. The solution is to use pushd instead of cd, so that there is
no need for the c:.
pushd "%OSGEO4W_ROOT%\apps\udig-dev"
It works for me. Could you try that out just to see if it works for you also?
Original comment by andrea.a...@gmail.com
on 31 Mar 2011 at 4:36
ok, it works also for me !
Original comment by mesca...@gmail.com
on 1 Apr 2011 at 7:08
Great, I uploaded the new version right now. If you could give it a test, that
would be great. Thanks.
Original comment by andrea.a...@gmail.com
on 1 Apr 2011 at 7:41
I am lowering priority for now, since we have no way to reproduce it.
Original comment by andrea.a...@gmail.com
on 27 Apr 2011 at 12:57
From our chats I guess this should have been solved with the latest versions.
Closing it here. If it appears again, we can reopen it.
Original comment by andrea.a...@gmail.com
on 27 May 2011 at 8:52
Original comment by andrea.a...@gmail.com
on 27 May 2011 at 8:52
Original issue reported on code.google.com by
mesca...@gmail.com
on 23 Mar 2011 at 2:59Attachments: