There's a new build coming out this weekend (yay!) with a variety of features, some bugfixes, etc.

One of the new features is a File - Info dialog prompted by a user suggestion that reports the project's full path, size, and last-saved date. What else would you find useful in it? (Component counts by type? Data size breakdown? ... etc.) There are a couple of days left before the weekend so we can squeak a few requests in.

If you have an idea and miss this weekend's release, there's another build coming up in 2-3 weeks.

a heads-up on some of the new features would be helpful so that we might identify somelow hanging fruit that isn't on the new feature list.

Well, the low hanging fruit for today is what you'd like to see in the File - Info dialog. :-) Any ideas?

I sent a couple of things in through other channels. But, anything you do with File -> Info, I wonder if you could do it through a right click/properties from the folder. Sort of like how a word document will tell you how many words are in it without opening.

File - Info is for the project, and there's something already a bit like what you suggested for items in the Project pane in that you can right click anything in the Project pane and choose Properties. That will show things like the initial text in a comments field. It's basically a read-out of properties for that item from the mfd_meta table and their values.

But that's a more technical thing that's info on the plumbing, and not a report of metrics like total size. To get metrics like that I think it's a good idea to add a more expanded "Info" entry to the context menu for anything you can see in the Project pane... folders, components, data sources, etc. I've contributed that as a suggestion.

That's an extremely easy feature to add from a technical perspective. What moves it up or down in implementation priority is the difficult part: deciding what exactly *what* info you want to show for various items. The info you'd want to show for a folder, for example, would have some differences from what you'd want to show for info on a drawing or a drawing's table and yet again different for data sources.

So, if somebody sits down and draws up a list of metrics or other things to display in an Info display for each possible item that might be found in the Project pane, then technical implementation is trivial. But if you don't have that list then implementation doesn't get done because the response comes back, "Sure. Easy to do. What do you want to report?"

In that respect File - Info is a trial run. If anybody gives a hoot about getting more expanded info in an easy to copy form (just one click to grab the full path for the project...), then it will get populated with more items than just the three in the initial version this weekend. If nobody gives a hoot about File - Info, then that's an indication extending that idea to context menu Info on individual items in the Project pane isn't worth doing. I think that's OK because there are zillions of ideas and the ones people care about should get done first.

Within theexpanded "Info" entry, status of linked projects, or data sources.

In my case, that's services no longer alive, or data sources that are on other drives not connected. (If that makes sense)

How about a column in the Project pane, say, by the right margin, that could be cycled through readouts of

interest, such as total size, date/time of last change (for KlauseDE's note, below), status in terms of connected or not, etc. ?

That would be perfect.

I am with Dale on this but beyond that Manifold files are for me ongoing records of projects that are still current but in some cases have been in progress for a long time (often working with colleagues). During this time I have had to update my computer setup, replace disks, etc. I never throw away any of this gear now that it has such a small footprint, but if File-Info could contain clues to the machine-source of files imported to a project .MAP file that would be tremendously helpful.

Well, File - Info is about the project. It sounds like the source from which a component was import might better be a property of that component, or automatically written into the description for that component, such as "Imported from ARCHIVES C:\data\shapefiles\lakes.shp on <date>". How does that sound?

Automatically adding this information to description with the opportunity to edit is a god place to capture theses data.

I often copy/paste queries from one project to another via clipboard. However this doesn't allow for keeping this information and I should then change workflow to Import from mfd project.

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

Not necessarily: if you copy a component and paste it, then the description should also be copied and pasted too.

I would like to see two additional rows indicating the item and date of last changes in File-Info:

First row: Changes of components: [Date+Time], [Component], Action

'Action' is:edit component (style, ... any property ) | add component |deleted component

Second row: Changes of data in local tables

'Action' refers to records:edit table;mfd_id | add table;mfd_id| delete table;mfd_id

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

User chooses a 'zoom scale' option in preferences for 'Zoom to selection' when the selection is a point or points. (See Zoom to Selection for a single point zooms out to max extent - contrary behaviour)

That doesn't have anything to do with File - Info, the topic of this thread, but here are two comments anyway:

First, if a single point is selected, say, in a "Cities" layer, then right clicking the layer tab and choosing Zoom to Selection will *not* zoom out to maximum extent. It simply zooms to that one selected point.

Second, if you want to zoom to a specific scale, zoom to selection and then click the scale setting in the status bar at the bottom of the Manifold application window and choose the scale you want.