MAXToA Toolbar how remove?

MAXToA Toolbar how remove?

locblamov
Contributor Contributor
5,862 Views
25 Replies
Message 1 of 26

MAXToA Toolbar how remove?

locblamov
Contributor
Contributor

After installation Arnold 5.7.4  there is a toolbar that keeps popping up that won't remove and is always docked on the left side.
How to remove it permanently?

Accepted solutions (2)
5,863 Views
25 Replies
Replies (25)
Message 21 of 26

giuseppe.schiralli
Autodesk
Autodesk

Can you hide it as any other toolbar?

giuseppeschiralli_0-1727971646756.png

 


Giuseppe Schiralli
3ds Max - QA Analyst>
0 Likes
Message 22 of 26

spacefrog_
Advisor
Advisor

Yes, you can hide it but it reappears each 3ds max restart, even when you save the UI layout. The hidden state simply doesnt stick across 3ds max sessions


Josef Wienerroither
Software Developer & 3d Artist Hybrid
0 Likes
Message 23 of 26

masterzap
Enthusiast
Enthusiast
Accepted solution

Okay, this was an interesting one. Obviously, when I try this it is working as expected; hiding the toolbar is sticky.

After some debugging, it turns out, that it's an issue of timing; toolbars must be loaded in before max applies its "layout" (which is the stored state of any window, including any toolbar).

When Arnold is the default renderer, it is loaded early enough in the max startup process for this to work. But it turns out that when it is NOT the default, this gets run later, *after* the layout has been loaded. The toolbar will then be seen as a "new" one, and always pop up. Ouch.

I've fixed this now (by loading the toolbar based on a Notification that always happens at the right time) and it will be in the next release in a couple of weeks.

If you want to get rid of it in the meantime, a workaround would probably be to delete MAXtoA.cuix (in the MAXtoA plugin folder) and MAXtoA_user.cuix (in the user settings folder) files.

Sorry for this, it was not intentional and, well, "it works on my machine" 🙂

/Z

Message 24 of 26

spacefrog_
Advisor
Advisor

Thanks Zap for sharing the details , cool that it will be fixed 🙂


Josef Wienerroither
Software Developer & 3d Artist Hybrid
0 Likes
Message 25 of 26

JasonLuckett
Advocate
Advocate

Any reason this behaviour hasn't been removed since the 2 updates from the start of this message?

0 Likes
Message 26 of 26

masterzap
Enthusiast
Enthusiast
Accepted solution

Easy; we didn't know about it, because nobody had reported it. 

 

We stumbled onto this thread by accident just a few days ago. And no, this is not a monitored forum, if you though that. And I am fresh out of flux capacitor fluid in my time machine to go back in time to fix it before I knew about it.... 🙂

Here's what I keep saying to people; if you find a bug, report it.
Not write it on some forum, complain about it to a friend, or write about it on X... that does nothing.  

There's a handy link in the Help menu to report a bug. Help -> Feedback -> Report a Problem

 

Also, if you have reported a bug, and it doesn't seem to get fixed, one of two things have happened:

a) It was down-prioritized for some reason (we only have so much resources)

but much more likely is:

b) The report was not reproducible.

We can't fix a bug we can't reproduce. A bad bug report that does not have clear steps, is useless, and will get thrown in the bin, a report has to be reproducible.

But above all: Report. The. Bugs.

 

You have no idea how many times this chain of event has happened:

1) We work hard on a release, think we've done something good.

2) We release it

3) Five minutes after, someone is saying on some forum "Oh my god, I can't believe they didn't fix the X bug. The X bug has been there for YEARS"

We all look at each other confused and go "which X bug?".
We search our bug database, and nobody has EVER reported it. (At least not reproducibly).
We contact the user, who invariable is agitated and says "how can you not know of this bug, everybody knows of this bug".
And we ask "Did you report it?"
And they either say "No, coz everybody knows about it", or they say "Yes, six years ago".
And I bet if we had every trashcan saved, we might find a six year old bug report that didn't reproduce because it was badly described. 
And the worse irony, 90% of the time, it's a 5 minute fix... had we only ever been told about the problem...

So here's my message to you all:
If you find a bug, report it.
If it doesn't get fixed in the next major release, report it again
There is no harm in reporting twice, think of it as giving another "vote" to that bug.
There is HUGE harm in reporting too little.

So report the bugs, report all bugs, proper channel, one problem per report, clear, reproducible steps.

Don't write on forums.

Don't run up to someone with an ADSK badge at a conference.

Don't email someone.

Don't DM someone.

Don't talk to someone.

Report it, through the proper channel, so it gets properly into the bug database. 
If you don't, it will get lost.

And bugs we don't know exists, we can't fix.
Like this one, which I fixed the same day I knew about it, and will be in the next release, Real Soon Now(tm)

Does that answer your question? 🙂

/Z