Author Topic: Tool Palettes  (Read 12044 times)

0 Members and 1 Guest are viewing this topic.

Kerry

  • Mesozoic relic
  • Seagull
  • Posts: 11654
  • class keyThumper<T>:ILazy<T>
Re: Tool Palettes
« Reply #15 on: February 12, 2006, 07:49:49 PM »
jeeze Glenn, I just had a look at the inheritance chain for the Palette class

.. there has to be a books worth of info tucked into that little beastie ..

kdub, kdub_nz in other timelines.
Perfection is not optional.
Everything will work just as you expect it to, unless your expectations are incorrect.
Discipline: None at all.

Glenn R

  • Guest
Re: Tool Palettes
« Reply #16 on: February 13, 2006, 06:35:07 AM »
Hehehe...welcome to my world of pain Kerry ;)
Thanks for looking though.

MickD

  • King Gator
  • Posts: 3636
  • (x-in)->[process]->(y-out) ... simples!
Re: Tool Palettes
« Reply #17 on: February 13, 2006, 03:50:42 PM »
Try as I might I can't seem to find anything either, I tried a few things that 'looked' like they should work but... nada!
From what I have read elswhere the api isn't finished for tp's, looking through the arx api though I'd still like to give PaletteSet's a go but again...
http://discussion.autodesk.com/thread.jspa?messageID=4952797
"Programming is really just the mundane aspect of expressing a solution to a problem."
- John Carmack

"Short cuts make long delays,' argued Pippin.
- J.R.R. Tolkien

Glenn R

  • Guest
Re: Tool Palettes
« Reply #18 on: February 13, 2006, 07:05:38 PM »
As I suspected. Thanks Mick.

Draftek

  • Guest
Re: Tool Palettes
« Reply #19 on: February 15, 2006, 03:44:20 PM »
Not sure this applies but I'm doing similar with a custom context menu system.
I'm deriving from the MenuItem base class, adding my own data along with event delegates.

I'm not interested in removing any yet but the method is available. I would assume if you are making your palettes in code, you should be able to manipulate them likewise. I could be wrong because I've not had time to view those objects in depth.

Personally, I'm treating the palettes like I did toolbars - I'll produce them for the user if they want to use them - statically. I'm also deploying the .xml files along with the .atc files so I can re-sync all tool palettes in case the user hoses them.

It sounds like you need more of a dynamic interaction so I'd stick with 100% code generated items and stay away from the tool palettes. Just my opinion.

If you figure it out, be sure to let us know.