From: Mark J. <mj...@we...> - 2005-12-13 20:02:02
|
This is a ,Global' Concept. What you do afterwards with the Shapes/Connections is up to you. - Goal 1 is to set the desired Font at the start of an Application. - Goal 2 is that the User can set everything when desired. At the moment the concept is that all Shapes use the same Font. The changing the Property of the Entity.Font will decide how far this can be allowed - inside the Class (as it is now) [private] - inside the Dll (this suggestion) [internal] - inside a derived Class [protected] - outside the class (the best solution) [public] For a specific Shape / Connection the override Property of Font can be used to prevent Font : - Name - Size - Style to be changed. - this should be possible (and desirable) The final Goal should be the balance of - the User having the freedom to decide which Font (Name, Size and Style) should be used - the Developer having the freedom to determine that certain Properties must be retained o WHEN this is really needed (for whatever reason) In my opinion (short before the 'one beer to many'): Font should be 'public' - so that the User see it the way he wants it - the developer can (when really needed) prevent what is not desired Using a Public Property in the Shape/Connector gives the developer everything he needs. As it is now (Protected) the User can do nothing. Mark Johnson, Berlin Germany mj...@mj... |