Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[@l@n]

JRiver, there has been an outstanding question in the Plug-In Development forum for a while that has gone unanswered.

Please see http://yabb.jriver.com/interact/index.php?topic=27790.0

The problem that some of us are having is that we are unable to skin our interface plug-ins (like my aTagger plug-in).  Hopefully you guys will be able to help us out.

Thanks... @l@n

[Matt]

For compatibility reasons, MC doesn't tag some classes of windows.  aTagger's main frame must fall into this category.  What is the window class of the main window? (you can use Spy++)

Thanks.

(p.s. I couldn't get to the aTagger site, so couldn't test and give more details)

[@l@n]

Matt, I'm not too famaliar with Spy++.  Here is what is displayed when I select the aTagger plug-in:

Window 00420B7C "aTagger v1.3.2" WindowsForms10.Window.8.app4
    Class Name is WindowsForms10.Window.8.app4
    Class Style is 00000008 CS_DBLCLKS

I do open a couple of windows -- one of them is skinned and the other isnt.  Both of them have the same class name and style as the main control.


I'm finding that some firewalls are blocking access to http://aTagger.auldridge.biz (which is a masked address).  Please try the real address of http://auldridge.biz:81/atagger.

Thanks...  @l@n

[@l@n]

I'm finding that some firewalls are blocking access to http://aTagger.auldridge.biz (which is a masked address).  Please try the real address of http://auldridge.biz:81/atagger.

Matt, now the Internet connection (cable modem) to my server is down.  They are working on it now and it should be back up later today.

Thanks...  @l@n

[@l@n]

Matt, now the Internet connection (cable modem) to my server is down.  They are working on it now and it should be back up later today.

Ok, it looks like my server is up and running again...

[@l@n]

bump...

[@l@n]

bump....   last try

[JimH]

Sorry, we'll try to look at this.  Thanks for the reminder.

[John Gateley]

    Class Name is WindowsForms10.Window.8.app4

Hi @l@n,

I think the class names are the problem. Instead of a class "Button", you have "WindowsForms10.BUTTON.app4".

Where'd these class names come from? What development environment are you using?

j

[John Gateley]

I did some quick checking, and it turns out there are further problems.
Your buttons have the BS_OWNERDRAW style set. This style tells us to let the button owner draw the button, so we can't skin it. Can you check to see if there's a way you can turn off this style? If so, I may be able to put support in. If not, it's a lot tougher...

j

[@l@n]

I think the class names are the problem. Instead of a class "Button", you have "WindowsForms10.BUTTON.app4".

Where'd these class names come from? What development environment are you using?

John, thanks for your attention to my question!!!

aTagger is developed using C# .Net with:
    Microsoft Development Environment 2003  Version 7.1.3088
    Microsoft .NET Framework 1.1  Version 1.1.432 SP1

The base class is "System.Windows.Forms.UserControl" and all of the controls are from the "System.Windows.Forms" namespace.

I don't see any button properties that even slightly resemble the BS_OWNERDRAW style set that you mention.

Thanks again for your time...  @l@n

[Matt]

It looks like the CLR window forms stuff is a sort of owner-draw skinning engine. 

So for the time being, the look of .NET window forms will be up to the .NET skinning engine, not the MC skinning engine.

Thanks @l@n.

-Matt