Pro: GP Inputs should display full path to sources (as does Arc)

448
3
04-27-2018 11:39 AM
Status: In Product Plan
Labels (1)
MVP Frequent Contributor

In Arc, when I'm dragging or selecting feature classes into a GP input, the full path of the source is displayed. This is helpful, say, if I'm merging stuff from many different folders (Did I already add the feature class from the thumbdrive? Wait, is that last one from the laptop? )

In Pro....I have to hold the mouse over each input UI, or click on it, to get the same information: 

Mickey Mouse? Yes. More steps? Yes. Is that as efficient, or as fast, as I can get the same information in Arc? No......Let's say I'm merging 10, or 50, feature classes. How is holding the mouse over every one of those is going to clue you in as to which ones are in the "box", and which ones are left to grab?

3 Comments

I too do not like this method of reducing the file path down to the table name. Why did they even implement it, no other application I'm aware of does this? As Pro is following in the footsteps of Microsoft office with ribbons why have they introduced this confusing, non-intuitive, non-standard dumb-it-down approach?

We need to see the full path.

Yes a long path is just as irritating, but at least you know what you are looking at and the idea of placing the full path into the tool tip is a good solution. 

We have a staging database where feature classes are staged using the same name as the one in the master database.  Our existing tools have inputs for the target fc and the source fc then doing a truncate-append.  If the user has update rights to both locations this could be disastrous if they get mixed up!  Once both are set I always double check to see that I didn't get the target and source backwards.

Is it planned to be released in 2.7?