|
2004-10-11 06:08
|
exampleassociationlabel.jpg (24,425 bytes) |
|
|
JVCL already contains a lot of components (too many some think), so adding additional specialized components isn't a good idea. Additionally, as soon as we decide to use TJvLabel, someone will say "I would like to use JvHTLabel instead". If we decide to do it with JvHTLabel, someone will say "I don't want to use JvHTLabel or JvLabel, I want standard TLabel instead". Frames are simple, you can design them as you like and reuse as much as you want, so that is what I recommend in this case. |
|
|
OK, i understand what you say. (i don't lnow good frames, it's for that!) But... in certain case....it's need/requiert no? often for JVFileNameEdit and JVDirectoryEdit a "label" title is necessary added (each time). but.....i unnderstand ! It's not possible to define in jvcl a set of default frames often used for user, possible it's good idea? or add a property to link 2 or more visual components for (all) components ? (example "published AssociatedControl:=tcontrol" and possibly "fixedControl:=boolean"), then we can associate any component with any other !? It's more simpler than frames no ? and compatible too with all actually components ! What do you think ? |
|
|
>What do you think ? Supplying a set of default frames is a good idea. In fact, I once thought about converting some of the JVCL dialog components to frames (DualListDlg etc) but never got around to it. Adding an "AssoicatedControl" property is also a pretty good idea. As everything else, it is a matter of available time :) |
|
|
okay, can you provide for testing only one (or two) component with this feature ? we Select for example JVFileNameEdit ( and JVDirectoryEdit) for test : -> with "AssociatedControltemporaryfortestingonly" tcomponent property if you put unit in cvs for public and for everybody test and send comment here (and why not help), OR, -> a modified file unit with "AssociatedControl" tcomponent property and you post here for me the modified file unit for i test and help-you/try to (me I) write code for other components, because i'm not very good in programming object and creating component,i'm good only for "traditionnal programming feature" with function, procedure, ...but for "destructor, constructor, object", .. hum, hum!.... -> or help me to code this feature (because see previously!) and i code and post here if it work. ps : can you get me your email please, if possible ? i don't have found your profile in mantis for find you email, thank. i think if this feature is implemented (or a derived) it will be very success for the user! :-) nanotonne (with no "s" for nanotonne at the end, not nanotoone too, or .... ;-) pether3 ouups peter3 ! ) |
|
2004-10-13 01:59
|
JvAssociatedControl.zip (2,744 bytes) |
|
|
I don't have time to do it myself, but I've uploaded a demo with an implementation that should get you started. The demo uses a helper class (so you won't have to implement the same code over and over again). The control (in this case a TEdit), creates an instance of the helper class, and calls its UpdateAssociate procedure at appropriate times (when a control is removed and when its own bounds are changed). I haven't tested it at design-time, but it works fine at run-time AFAICS |
|
|
ok, i will go to read/test your file this week (end). thank ! |
|
|
I'm considered this to be resolved, it's been over 6 months, the week-end is very long ;-) |
- Anonymous
