topic Re: Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big in Inventor Forum

Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big

riedeld5696 — Tue, 30 Jan 2018 22:34:09 GMT

Do not like the new browser tree! Using it at work with Win. 7. In 2017 it went to bottom of screen and pushed all open files to the right of it where they could be seen. It also could be collapsed as much as desired. Now it takes up all kinds of space, covers up information at the bottom of the screen, and limits how much it can be collapsed. I have to actually put it on my second screen now just to get it out of the way. This is really a pain. Talk about going backwards. This needs to be fixed! Hard to believe that updates make things worse. Does anyone even test this coding before it's released? Much prefer 2017. Dave

kelly.young has edited your subject line for clarity: Browser tree in 2018

Re: Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big

johnsonshiue — Tue, 30 Jan 2018 22:34:56 GMT

Hi David,

Many thanks for the feedback! I would like to understand your concerns better. Do you mind taking a snapshot of a browser and articulating the issues? Are you on 2018 RTM build or 2018.2?

Thanks again!

Re: Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big

riedeld5696 — Tue, 30 Jan 2018 22:38:26 GMT

Dont know how to do this. I think I explained it well. The browser tree is terrible! It cannot me manipulated like it could in 2017. It is tooooo wide, and cannot be collapsed enough.

Re: Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big

Mark.Lancaster — Tue, 30 Jan 2018 22:39:02 GMT

@riedeld5696

Have you applied any updates to Inventor 2018 as @johnsonshiue pointed out?

Yes the browser has some issues when 2018 came out but as far as I know everything has been fixed. Make an Autodesk Screencast (https://knowledge.autodesk.com/community/screencast) of your workflow so we can see what you are talking about.. Perhaps there's room for improvement but its hard to go by your words. They can mean many things and the screencast will help us understand what you are talking about.

Re: Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big

JDMather — Tue, 30 Jan 2018 22:40:19 GMT

@riedeld5696 wrote:
... It is tooooo wide, and cannot be collapsed enough.

I agree!.

The issue is so obvious that I hesitate to waste my time to document with screen captures or Screencast.

Surely others have noticed this issue?

Re: Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big

Mark.Lancaster — Tue, 30 Jan 2018 22:40:39 GMT

Disregard my reply.. I guess I never needed to make my browser window so small for real estate graphics.

Re: Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big

kelly.young — Tue, 30 Jan 2018 22:41:06 GMT

@riedeld5696 thought it was too tight, got out our paint roller

made it a wide lane, so luxurious...

Seriously though, will forward to development team for further inspection.

Thanks for the feedback!

Please select the Accept as Solution button if a post solves your issue or answers your question.

Re: Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big

JoyceZhou — Wed, 31 Jan 2018 02:03:10 GMT

Thanks for reporting the issue, this has been fixed in R2019 Beta2 build (invgen-11830), and the development team is investigating to backport the fix to R2018.3.

I will inform you if there is any progress.

Thanks,

Re: Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big

riedeld5696 — Wed, 07 Feb 2018 02:08:14 GMT

Thanks for the reply,but what does your answer mean in non-techy talk, and what is the estimated time frame for a fix? Thanks again. Dave

Re: Browser Tree Inventor 2018 Minimum Collapsible Width Is Too Big

kelly.young — Wed, 07 Feb 2018 02:29:11 GMT

@riedeld5696 The 2018.2.3 was just released on 1-22-18 so without any promise or new actionable info, I would say that some time in the summer is what we would be shooting towards based on the history of updates.

I cannot guarantee it will be included in the next update, but I did forward to the development team and as you can see they quickly addressed the issue for 2019 Beta2 and are investigating to backport the fix to R2018.3.

Again, nothing set in stone from me but that's as transparent that my crystal ball can be.

Get involved and join in the Beta group to get the most up to date information!