9.0.179.3

manifold-9.0.179.3.zip

SHA256: c5460208023cbe8e952b7f91bb78eae3bc0920bed6cadb5cd6895073a7fd0bab

manifold-viewer-9.0.179.3.zip

SHA256: d5ce772d4e0943009a0c526d4f83c86bfa85fd4d96dd210ce4d9f2c3785e17f9

sql4arc-9.0.179.3.zip

SHA256: 3b37657212022fa063a348a9bb71a62dc647864ca5885bcfad68ce9ff44e05d6

Changes

(Fix) Commands switching between different modes for the Position status bar pane show their descriptions in the status bar.

The Scale status bar pane supports different modes:

• absolute -- show scale as an absolute value, eg, '1:24000', the default,
• pixel size -- show scale as pixel size in coordinate system units, eg, '5 m / px',
• view size -- show scale as view size in coordinate system units, eg, '500 x 300 m'.

The Scale dialog invoked using the context menu for the Scale status bar pane allows specifying the scale either as an absolute value, a pixel size or a view size.

The Position status bar pane reports the coordinates under the cursor for the active layout frame that contains a component.

The Scale status bar pane reports the scale of the active layout frame that contains a component. Reporting the scale of a layout frame in the 'pixel size' mode reports the number of coordinate system units per millimeter. If the layout that contains the frame is writable, the scale can also be changed.

(Fix) Reading data from a TIFF file no longer sometimes incorrectly places pixels in the last row of tiles, pushing some pixels down and making a horizontal strip of pixels invisible.

End of list.

(We have also been working on extending Save as Image to cover layouts and on several improvements to labels, including callouts. These things are not yet completely finished, they will appear in future builds.)

This is great! Very nice to directly control the scale in a layout and also know the amount of land covered. This really makes making quick maps more enjoyable. Really helps make the software approachable for novice users.

Glad to hear labels are being worked on. In case it isn't on the radar, please consider a goal of supporting all the label variables (rotation, size, font, etc.) that ESRI makes available in their file geodatabase in order to round out support for file gdb.

Looking forward to the label improvements. Callouts will certainly be helpful. My biggest frustration is with labels being automatically hidden. For much of my work, I don't have the option of not showing all labels. And while the "move to avoid overlap" option has helped, there will still be instances where labels that too close willl get hidden. Unfortunately these are easy to miss until a client calls and says "why isn't xyzzy shown?" Since most of my labels are based upon points that I've created so that I can easily adjust them, what I can't see I can't adjust!

Same from me, with labels usually based on areas. I would like to have the option to show all of them, even if they overlap. (And also to have the option to show a label for each branch when the area has multiple of them.)

I would like to have the option to show all of them, even if they overlap.

We will do this, yes. Then you will be able to reposition the labels that overlap manually.

It would be nice to see horizontal and vertical text align stiles work on label components and not only on layout label items. I guess that is planed as the controls are active but without effect.

Do you really want to ruin economy only to save the planet?

Horizontal align works on labels with multiline text.

But in general, if you mean to use align to place a label relative to its geometric location -- for point geometry -- that's done using the Move parameter group (angle + distance to go from the origin).

But that is not useful for labels imported from AutoCAD for instance that are left/right aligned in the original data. As long as there is no Move parameter mode refering to the extend of the textbox I see no way to (re)align point labels in a lable component.

An extended (CAD-)importer could reflect properties of the original single lable in record specific stiles. This could include angle, font, alignment, ...

But for an elaborated feature request I'm interested to hear others ideas to a flexible origin of point labels in lable components dependent on the chosen font stile and direction. It might be appropriate to have some features for all types of labels and others features located in importers. For instance a knowledge of the text box depending on font and direction would allow for a precise hiding of lables that really overlap. So that might be of overall interest on one hand and a deep change in the technical structure of labels on the other hand that's better done early in development.

Do you really want to ruin economy only to save the planet?

I understand now.

The labels coming from CAD formats sometimes are placed using boxes and the alignment is within those boxes. I think we convert boxes into points, possibly ignoring the alignment. But even if the alignment wasn't ignored, there would be a loss of data -- for example, because a box tells the label to stay inside of it, and if the box is converted to a point, however well that point is placed, when you zoom out, eventually the label will go outside of the former box. I guess the long-term solution would be keeping the boxes as areas and adding a style option that would try to paint labels how CAD tools do it: never going outside of the box, scaling the text according to the box size similarly to render scale, etc. That's not super-easy to do, but that will probably make labels from CAD formats look much closer to the originals.

I will add a couple of notes to the wishlist so that we at least keep these things in mind.

Sounds like the solution for label import from CAD and ESRI might be fairly similar. Generally both are most useful if they match their box, although converting to a point is a useful option for when not using the render scale.

Anything that would help automate their import would be appreciated. At a minimum, we need more parameters that can be thematically set. We get the following fields from ESRI when importing labels and only a few can be currently set thematically: font, font size, bold, italics, underline, vertical alignment, horizontal alignment, xoffset, yoffset, angle, font leading, word spacing, character width, character spacing, flip angle, and override. Hopefully a means can be found to allow the Style pane GUI to set all these parameters to a field.

I have installed 9.0.179.3 and there is a strange behavior. The status bar - Selection - shows nothing. In the info pane all selections show everything as expectetd. But even more strange now if I open 9.0.179 the same effect appears: no information in the selection status bar.

Uninstalled and reinstalled 9.0.179 with no success. Whats going wrong here? Any help is appreciated.

(System Windows 11).

I cannot reproduce it on a new MAP file. Could you post example file with a component that exhibits such behavior? (Can erase all other components, remove all fields, etc, as long as the behavior stays.)

here is a example map-file with areas and points. You can select whatever you want, nothing shows in the status bar

Attachments:
Statusbar_Problem.map

I just tried and the number of selected objects shows for me (in any window):

Can it be that you accidentally hidden the relevant status bar pane? If so, to show it back on, right-click the left side of the status bar (the area with the menu prompts), then make sure Counts is checked.

Attachments:
shot-selected.png

yes, that was it. I did not realize that I can switch on or off the elements of the status bar.

Thank you

Getting "Save as Image" nailed down will be great. I discovered last week that M9 did not have that capacity. I had to export the relevant layers to be imported into M9 in order to get a georeferenced tiff file (I read the georeference portion of the M9 manual. Creating the image requires associating the image with a table. Since I am trying to make an image based on a particular view, I have no tables with which to reference. Choosing a table will give me an image of the layer associated with that table.

I am not sure I understand. When you are saying that Manifold 9 does not have some capacity, what are you referring to? Save as Image is already in Manifold 9, it works for maps. The note after the list of changes says that we are working to extend it to work for layouts, too.

You are correct that Manifold 9 has the ability to save as image. I was looking for it under Tools where it is on Manifold 8. This is the result of trying to do something new in haste.