mapwindow6 Issue Tracker Rss Feed

Created Issue: Solve crash on .NewLayer() [12719]

jjmonot — Sat, 12 Jan 2013 19:04:40 GMT

Crash when using multiple .Newlayers ()

Created Issue: Solve crash problem on the 6.1.2 version [12718]

jjmonot — Sat, 12 Jan 2013 19:01:52 GMT

Crash when loading extensions.

Closed Issue: Plugins autobuild, but MW6 does not. [11753]

mudnug — Mon, 13 Feb 2012 21:33:11 GMT

After downloading and running MW 6.1 I got exception
http://www.everfall.com/paste/id.php?ezj078m9vy4g

A permanent solution is to setup the extension loader so that it gets only a version that will work with it (instead of the latest version)

A fix is to publish a clickonce update.
Comments:

An update has been released that works with the new MenuBar extension.

Commented Issue: boolean error [11753]

mudnug — Mon, 13 Feb 2012 21:27:18 GMT

After downloading and running MW 6.1 I got exception
http://www.everfall.com/paste/id.php?ezj078m9vy4g
Comments: ** Comment from web user: mudnug **

Thank you for posting.

Created Issue: boolean error [11753]

igeek — Sun, 12 Feb 2012 08:14:12 GMT

After downloading and running MW 6.1 I got exception
http://www.everfall.com/paste/id.php?ezj078m9vy4g

Commented Issue: Initial comments on user interface issues [15]

danames — Fri, 23 Sep 2011 17:30:09 GMT

I've created several issues in the DotSpatial project regarding UI comments; that is probably where the corrections will have to be made, however the MW6 project allows me to see things that weren't apparent when just utilizing the DotSpatial libraries in my project. Please take these comments as being constructive---you guys are doing a great job!

1. Add Layer menu item to duplicate function of layer toolbar
2. Make menu entries Windows standard notation: "Save As...", etc.
3. File menu should have "Exit", "Print", etc.
4. Add View menu to duplicate zoom toolbar functions; everything on toolbars must have corresponding entry on menu.
5. Consider utilizing nice ribbon control like Hydro Desktop does in addition to/instead of lots of individual toolbars.
6. Recommend Start menu entry to be "MapWindow 6"
7. I understand that About is a plugin, but some plugins can just be required and non-removable--need Help | About!
8. The progressbar is always visible on the status line
9. Recommend that split panel on left be fixed size when resizing form--i.e., user can resize, but it does not shrink when form shrinks.
10. When selecting, still need to be able to pan in real time using mouse wheel (roll it to zoom, click to pan)
11. FeatureIdentifier form needs better title and icon.
12. Toolbar "Table Editor" name inconsistent with rt-click on layer "View Attributes"
13. Layer Properties form:
a. needs icon
b. don't let it be resizable or allow it to properly resize contents
c. "Use color range" checkbox should have opaque background
d. All the controls are beautiful, but should have transparent background because will look ugly with different themes (always gray)
e. When select Quantities, field drop-down does not include numeric fields in attribute table I'd want to use for thematic mapping (e.g., area).
f. Tab order is wrong
g. Hot key assignments not used for all controls
h. Need tooltips on HSL/RGB tabs, dice button, etc.
i. Property grid on Detailed Prop not quite right at bottom.
j. All the properties need descriptions (this is generally sorely needed in library too for development!)
k. ? icon on title bar doesn't do anything. Suggest implementing at least rudamentary help sentences for each control.
14. Join dialog resizing needs work.
15. Order of OK/Cancel buttons not uniform.
16. Join should be model dialog, not appear on taskbar or allow maximize/minimize.
17. Recommend "layer properties" item on menu & toolbar so don't need to know to right-click to set layer properties; is disabled if no layer selected.
18. What is relationship (if any) between toolbox tab and Extensions menu. Are all toolbox items in a single extension or are they part of core product?
19. Some spelling errors in toolbox lists "avrage"
20. Double-clicking on toolbar items non-intuitive; at least include rt-click menu that says "Activate tool" or button at bottom that says "run tool" when one is selected.
21. Tools have lots of spelling errors (Ouput?).
22. Tool help non helpful
23. I would vote for these tools being on a Tools menu, not adjacent to Layers tab; would also be similar to way MW6 does it and remove double-click issues.
24. If really in love with treeview approach to selecting tool, put that treeview in a single Tools form (just extend existing form design) where the contents change depending on item selected; that way can browse what each tool does without having to open dialogs.
25. Look at "Add Raster Layers" that name is repeated three times on the form, and the hammer is in there twice. Doesn't look very professional.
26. Put OK/Cancel buttons on lower right for consistency; tab order and hotkeys needed.
27. Tool progress form needs work (resize, title, icon, etc.) Cancel button broken?
28. Aggregate tool doesn't seem to work; in fact, most tools don't appear to be hooked up correctly.
29. Dynamic visiblity mode resizing bad
30. Attribute table editor Tools | Append Field... causes error

Hope these comments help.

Chris

Comments: Chris, thanks for this very nice detailed feedback on this "work in progress" project. I am very much interested in seeing this become the main end user GUI for DotSpatial, so this really helps... - Dan

Edited Issue: Initial comments on user interface issues [15]

jirikadlec2 — Thu, 22 Sep 2011 20:11:49 GMT

Created Issue: Initial comments on user interface issues [15]

lloydchriswilson — Thu, 22 Sep 2011 16:33:42 GMT

Commented Issue: towgs84 parameter not supported? [13]

chinkuan — Thu, 05 Aug 2010 19:16:43 GMT

Is towgs84 parameter not supported in MapWindow6 ? It works in MapWindow4.
Comments: Yes. The 'towgs84' parameter defined in shapefile prj file seems to not be recognized in MapWindows 6.

Created Issue: Bad Shapefile implementation? [14]

halmaia — Wed, 04 Aug 2010 11:09:51 GMT

I used the MapWindow6's Shapefile editor plug-in to create a new point shapefile without Z or measurement data. I added 30 points to the shapefile and I saved it with the right-click --> data -->export data.
Then I tried to read the file with my own shapefile reader, written in VB.NET, followed the ESRI's Shapefile whitepaper. When I read the "File Lenght" (described on 4. page in whitepaper) I always get 100.
This "100" means the file is 100 16-bits dwords long (200 bytes).
File Length(Point) = File Header (100 bytes) + N * (Record header [8 bytes] + Shape type [4 bytes] + Coordiante [16 bytes]); where N is the number of points.
File Length= 100 + 30 * (8 +4 +16) [bytes]
File Length = 940 bytes (= 470 16-bits dwords)
So the File Length sould be 470!

If I use the ArcGIS-ArcMAP 9.2 to create a file and add 30 points, then I read the File Length, I got 470!

Then I tried to create files and add more or less than 30 point both in MW or in ArcGIS. The MapWindow always writes 100; the ArcGIS always writes the logically correct length.
Is it a bug in the shapefile writer?

The code in PointShapefile.cs (from line 40) (Release June 14.)
public PointShapefile() : base(FeatureTypes.Point)
{
Attributes = new AttributeTable();
Header = new ShapefileHeader();
Header.FileLength = 100; //Here is!
Header.ShapeType = ShapeTypes.Point;

}

I attached the files.

Ákos Halmai
GIS Student
Hungary, Europe
Sorry for the possible grammar mistakes.

Commented Issue: towgs84 parameter not supported? [13]

AlamoMan — Wed, 14 Jul 2010 19:01:58 GMT

Is towgs84 parameter not supported in MapWindow6 ? It works in MapWindow4.
Comments: chinkaun, are you wanting to project features to a GCS WGS1984? If so, the projection libraries are currently undergoing a comprehensive test (http://dotspatial.codeplex.com/wikipage?title=ProjectionTestResults&referringTitle=System.Spatial.Projections) and bugs are currently being fixed. When the projection library was ported over from MapWindow4 to MapWindow6 there were some transcription errors,however, at this time most the there errors have been fixed. If this is not what you are attempting to do, could you please provide detail information on what you are attempting to do?

Edited Issue: towgs84 parameter not supported? [13]

chinkuan — Mon, 05 Jul 2010 09:13:03 GMT

Is towgs84 parameter not supported in MapWindow6 ? It works in MapWindow4.

Created Issue: towgs84 parameter not supported? [13]

chinkuan — Mon, 05 Jul 2010 09:12:04 GMT

Does MapWindow6 not support towgs84 parameter?

Created Issue: The las subversion version doesn't compile correctly [12]

geofran80 — Thu, 24 Jun 2010 08:13:04 GMT

The last version of subversion code doesn't compile correctly in Visual Studio 2010.

I got aproximately 617 code errors. To much of this related with Mapwindow.dll because is not found.

Any sugestion?

Thanks.

Francisco J.

Created Issue: Big Polygons with Small Holes Fill Incorrectly When Zooming In [11]

Shade1974 — Wed, 23 Jun 2010 15:35:57 GMT

Polygons with holes do not fill correctly when zooming in. If the outer polygon is completely outside the viewable area, there is a good chance that it gets eliminated from the drawing instructions, in which case it will fail to fill the polygon correctly.

Created Feature: Rename ClipWithPolygon to ClipGridWithPolygon [10]

Shade1974 — Mon, 14 Jun 2010 23:10:01 GMT

Aaron would like us to rename ClipWithPolygon to ClipGridWtihPolygon. I will try to get on this tomorrow but am out of time today.

http://www.mapwindow.org/phorum/read.php?13,18598

Commented Issue: One Null Attribute during intersect causes null output attributes. [9]

Shade1974 — Fri, 11 Jun 2010 21:42:21 GMT

Hey Ted,

I think I've found a bug in MW6. If I do:

IFeatureSet bob = Featureset.Intersection(myotherDataset, FieldJoinType.All, myProgressHandler);

then look at

bob.Features[0].DataRow

All of the cells are DBnull if one of the cell values in one of the FeatureSets contains a null value. I've got a sample shp file that does it if you need to see.

Thanks for the help,

Brian Marchionni

Comments: As long as I made sure to call "FillAttributes()" on both shapefiles before calling the intersection code, it worked ok. The code should be filling the attributes when it accesses the DataTable automatically, but it isn't doing so here for some reason. I'll try to see if I can find out why it isn't.

Created Issue: One Null Attribute during intersect causes null output attributes. [9]

Shade1974 — Fri, 11 Jun 2010 21:22:40 GMT

Created Issue: Add Multiple Datafiles [8]

sindizzy — Sun, 16 May 2010 21:51:12 GMT

When I add datafiles to the map through the "+" icon it allows me to select only one datafile. Typically i want to load 5 or 6 in one shot and that means I have to use this function 5 times. The drag and drop already allows loading of multiple data files. It probably is just the file selector component that needs to be tweaked. Speaking of modifications...I think I would like to contribute my time on some of this stuff. Where do I sign up?

AGP

Created Issue: Group checkmarks [7]

sindizzy — Sun, 16 May 2010 06:18:19 GMT

I'm just starting to test MW6 and I can say it looks great so far. Am looking forward to seeing a great product. One thing I have seen is that within a group if only a certain number of items are checked then the main group should have a gray check mark. if you collapse the group there is no indication that some of the sub-layers are turned on. I always struggled with this in MW4. Maybe its not supported in the control but i think it makes sense to do so.

AGP