is tolerable "borrow" dependency properties separate classes?


i'm minute category renders calm wpf, i wish give user control over calm rendered. digest mostly rub-down lines, i solid feeling system.windows.forms.shapes.line category an thought properties i competence wish implement. led me exercise many strokexxxx properties, it's lot drudgework given any requires metadata impact rendering.



a co-worker suggested i only "borrow" properties figure this:



shape.strokethicknessproperty.addowner(typeof(mytype));


this seems graceful good idea. i guess doing i'd remove ability set duress ability altered callbacks, nonetheless looks profusion takes propertymetadata allows this. wholly downside i doing figure changes, impact the class, nonetheless i'm capricious mostly i design .net interfaces change significantly.



what think? decent by-pass defining properties obvious category function wish quick interface, sure-fire proceed play glow while gasoline bath?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?