[MonoDevelop] Suggested change to navigation drop-down behaviour
mkrueger at novell.com
Sat Jul 3 10:10:09 EDT 2010
> 1) It would be nice to be able to click to show the list and click to
> hide. Currently the second click hides and re-opens the list, but the
> widget renders more like a toggle button.
I'll look into that - seems to be a bug.
> 2) Delegates seem to be handled a bit strangely. I've got one file that
> just defines three delegates that I use frequently and the nav shows an
> odd "Invoke" sub-item that I didn't expect. Is it necessary or can we
> merge them to just show the delegate name with its icon.
Ok put delegates on the list (the invoke is a method I internally
generate for delegate types - shouldn't show up).
> 3) If I add a region to my code then it breaks the click on the first
> button (the file). Clicking on the file only shows the region as an
> option, which means you can't use the nav to get to methods and classes
> outside regions
The first box just shows the regions and let's you select arbitrary
regions - but doesn't filter the following ones (doesn't make real sense
after trying it).
It's a bit tricky to show the regions - that's why it's a bit
unintuitive, but I think this behavior is the best solution. If anyone
has a better idea I would like to hear it.
> 4) Regions seem to show at the start of the list rather than where they
> are in the hierarchy. If I put a region inside the class and put my
> cursor on the class then I can't see the region in the nav, but if I
> click in the region then the nav shows the region first, then the class,
> then the methods of the class that are within the region.
That's because regions are more file specific than type specific ...
putting the regions into the type hierarchy wouldn't give a good
overview of the regions - wouldn't it ? I prefer to have the regions
separate for the files - is this wrong (I would like some opinions about
that after trying out the current SVN version).
> The general behaviour of being more flexible in length and looking more
> like a widget designed for a purpose instead of a bunch of widgets used
> to make something approximately right (even if that is what Visual
> Studio does) is definitely an improvement. The region handling is also
> going in the right direction, even if it isn't quite there yet. Overall,
> it looks good so far :)
Nice to hear that this is going in the right direction. The great
strength of the new control is that it is better than the old one
showing the current position & taking less space for the same job.
I'm not 100% satisfied with it yet, but I've some months left to
streamline it for the 2.6 release :)
(As well as the version control file views)
More information about the Monodevelop-list