2019 Toolbars still not fixed??? This is unheard of.

[JamesMaeding]

In 2019, anyone who has custom toolbars (you know, like every serious company out there), will see ?'s for every button:

The ones that do show are "stubs" for flyouts.

I'm not uneducated on this. I know the horrible workaround of automating menu redisplay on startup.

I know that you can convert image to .ico and compile a dll with them in the RCDATA section.

That is super rediculous though, as .ico is not easy to edit like bmp or .png with native windows tools.

Toolbars are basics folks.

How can Autodesk let release 19 sit without a fix for this?

At least say we ain't gonna fix it, or fix it. I need 2019 as it fixes many basics that 2018 broke.

Of course I worry they shove this to the bottom of the list, hoping I give up and go ribbon. Well, how about I give up and go full Bricscad, instead of just partial so far?

[john.vellek]

Hi @JamesMaeding,

I agree that this is a major issue for many customers and it was brought to the attention of development as quickly as possible.  I do not have any further information on a resolution at this time.

[RobDraw]

Still can't your ducks in a row?

Toolbars are passe. It's a good thing AutoCAD cares about dinosaurs or they would have gone away a long time ago.

[JamesMaeding]

@RobDraw

I guess advanced beings like yourself would not understand the elegant simplicity of .mnu and toolbars.

I won't bother explaining.

[RobDraw]

---

@JamesMaedingwrote:

I won't bother explaining.

---

Thanks for that. 

[Anonymous]

Al my toolbars show up correctly, I don't see any problems.

[JamesMaeding]

@Anonymous

I said Custom toolbars. I know the ones in the OOTB acad menu show up.

This is not specific to me, anyone who loads toolbars they made gets the issue.

Do  search on this a bit to see the wonderful workarounds people are doing, which don't work if you have more than one row of toolbars.

People might say to go ribbon, but I refuse to destroy their wrists with the clicks needed to switch tabs to get to commands.

[Anonymous]

ALL buttons show up correctly on ALL my toolbars, I have a special folder with all the BMPs I created for my buttons in my hard drive with a path set in the Files section of Options. I haven't had a problem since I installed 2019.

[cadffm]

This technic should work well.
But there are many other situations (.dll, other filetyps, searching via normal supportpathes) and way (we are here in .net forum)
That can make trouble. It is needed to force a refresh, like unload/load the menu or switching the color sheme..

I didn't test for all, which works well and which not.
But be sure: Not all ways works well.
For example:
dll stored bmp

[TerryDotson]

We can confirm that what @JamesMaeding described is happening.  Numerous end users have reported the same to us and it's happening using files that worked fine for years.  This is a new BUG with 2019.

[JamesMaeding]

@Anonymous

I guess I have posted on this enough times before, that I left out a detail, and actually forgot .bmp does work.

Thanks for the reminder, but its bittersweet.

It only works with .bmp, not png.

Why do I *have* to have .png? Because it supports transparency.

Its rather trivial til you try to make the dark theme work, then you need the background to adapt.

So I went through my images and made.png, then replaced bacjground with transparency using Image Magick.

Once automated, it took a minute, that was easy.

The more cumbersome part was going through my menus and adding .png to every image name.

You do not do that if you use DLL, like I used to, but you cannot compile .png to a dll for acad, only .ico.

Anyway, I spent a few hours doing this for 2018, and it all worked.

Now 2019 is sending me on another goose chase, which is converting back to .bmp, replacing with light and dark colors, and editing the names so I will have a light and dark menu (I think, I need to reread on strategies for this).

Like I say, I've never seen basics like this get left for so long. Normally this would be a hotfix sent out in a week or two.

[peterm]

I get this every time I upgrade.

I've found that I can force AutoCAD to find the icons by editing just one of them in the customization interface.

I edit the image by drawing a line and then deleting it. Then I save it and apply changes and  - hey presto -  all the icons magically appear.

[pkolarik]

"In 2019, anyone who has custom toolbars (you know, like every serious company out there)"

I guess I'd better spread the news to our company that we're not a "serious company" since we haven't used toolbars in acad since tool palettes and then the ribbon came out.... 😜

[dgorsman]

---

@pkolarik wrote:

"In 2019, anyone who has custom toolbars (you know, like every serious company out there)"

I guess I'd better spread the news to our company that we're not a "serious company" since we haven't used toolbars in acad since tool palettes and then the ribbon came out.... 😜

---

If you're "serious" enough to be creating custom functions and buttons, then you're "serious" enough to be building Tabs and Panels in the Ribbon which work well with the desired workflow (you know, avoiding all those extra clicks), plus providing command-line versions to map using the PGP and multi-function mice/keyboards.

[JamesMaeding]

@peterm

I believe that is the same thing as the redisply code others are using, as it reloads the menu stuff.

If you are ok with that process, its much easier to do in the startup with code. Search for other posts on this and you will find lisp that does it.

[JamesMaeding]

@dgorsman

I agree I should make ribbon stuff for those that want ribbon, but the problem with ribbons is they tend to have so many icons you never use, and you pay the price by clicking different tabs to get to those you want.

With toolbars you can get just what you want on screen, and save about 1/2 inch of vertical screen space if you keep to 2 rows.

Many forget that .mnu still works great for menu definitions. I have one .mnu that works in all versions of autocad and bricscad. Try supporting a ribbon interface with multiple versions. You must open the cui for every version and play with its lovely bug ridden features. I will do it at some point though.

For the key-in definitions, I stopped using PGP file in the year 2000, when I realized I want one file to manage.

You cannot do many things with pgp, that are simple in a lisp, just commands. So I have one lisp with all key-ins (except transparent ones like z and p). I have so many key-ins we made a search prog that parses the code and finds the command names.

[JamesMaeding]

@pkolarik

"I guess I'd better spread the news to our company that we're not a "serious company" since we haven't used toolbars in acad since tool palettes and then the ribbon came out.... ;P"

Dont TELL them! You have them hoodwinked so don't blow it!

[JamesMaeding]

so nothing still from adesk.

I know toolbars seem like a minor issue to some, but this is a much more serious sign that autocad support is falling apart. Why they let this happen at the same time they want us to rent the latest version is insane.

Heck, the marketing seems to have wound down too.

I can't do the "menu redisplay" workarounds, I think the only thing that works was puuting them in a dll, in the RCDATA portion. Lovely. Makes briscad look like the new acad.

[JamesMaeding]

@john.vellek

How about now?

Can you check with the developers inside adesk.

This is just a bug no one needs. Its about the time companies will start trying 2019 - a bit past the release.

I actually like it more than 2018, but this dumb toolbar issue is a headache. The ribbon is worse, its not the answer.

[john.vellek]

Hi @JamesMaeding,

The fix for this is in the works and should be released in the next update which is coming quick.  I can't confirm a delivery date but hold on just a little longer as it is on the way.