Ok, a couple of things:

>>Allow dynamically to change the look in design time, according to the properties selected.

Not sure I understand what you mean by this. The properties all fire _Assign methods, which
cause the look to be changed at runtime.


>>Embed the default pictures to the VCX/

As far as the images go, the issue I have is that the way we have it now, the paths to the
images are hardcoded into the class. The problem is that it prevents the user from putting the
images somewhere else wherever they want them.

For example, when I create a project, I create a Classes folder and a seperate Media folder in
anothere location, seperate from the Classes folder, with a Graphics folder under it.

With our method, we are forcing the user to have "Graphics\Thumbs" and "Graphics\Tracks" under
the classes folder. One idea to mitigate this is to crete a GraphicsPath property and set it
by default to "Graphics", then move all the default thumbs and tracks into it.

Then the user could move graphics where they want and change the property. This seems a bit more
flexibile to me. What do you think?


>>Using GDI+, automatically create greyscale images, and also brighter images for the thumbs if
>>the user does not provide for Disables and active modes
I'm ok with this, but as I said before, I have no experience with GDI. Can you handle this part?


>>Create some memberdata Scrips to be fired when users change some properties values
Can you explain this more clearly? I don't understand.

One other thing I want to do is create a builder for it.


>>Wanna submit it to VFPX ?
Absolutley!!, as well as post it to the downloads section here on the UT



>>Ok, looks good. Is there anything else we're missing?
>
>Hi Kevin,
>
>Some few things:
>
>- Embed the default pictures to the VCX
>- Automatically update the pictures when the user changes the style - eg If "left", then the thumb should be an arrow to the left
>- Using GDI+, automatically create greyscale images, and also brighter images for the thumbs if the user does not provide for Disables and active modes
>- Create some memberdata Scrips to be fired when users change some properties values
>
>
>
>Further,
>- Allow dynamically to change the look in design time, according to the properties selected.
>
>
>Apart from this, I think we're done !
>
>Wanna submit it to VFPX ?