re:
!my custom control uses a glyph that needs to be displayed at design time
Why ?
Design is design and runtime is runtime.
You can't expect runtime functionality at design time.
A similar example is using a querystring.
You don't need to see a querystring at design time.
You only need to be able to program against it.
re:
!That glyph is different depending on the theme
I had gathered as much.
You'll have different glyphs in each theme's directory, right ?
Then, all you need to know is the path to the directory which contains
the specific glyph you're interested in displaying with the active theme.
I think what I outlined should suffice, and don't quite understand
why you'd need to actually see a glyph at design time.
At design time, themes are neither enabled nor displayed.
That's done at runtime.
As a developer, all you need to do is insure programmability.
If it works...that's all you need as a developer.
Juan T. Llibre, asp.net MVP
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
======================================
"greg" <gr**@metastorm.no.spam.comwrote in message news:%2****************@TK2MSFTNGP06.phx.gbl...
>You wouldn't have to, would you ?
*You* don't need to know the path; the application's *users* do.
In my case I would, as my custom control uses a glyph that needs to be displayed at design time as
well as run time. That glyph is different depending on the theme.