
Peter Redei wrote in Source Code forum:
Wayne,
Congratulations! This is an excellent idea, and it actually did the translation the first time I tried it. So far (after 5 minutes) I discovered two problems:
1. Listboxes are translated with a empty string as placeholder where the optional array should be
2. The Menu Add String translates as CONTROL ADD MENU.
Peter Redei
Congratulations! This is an excellent idea, and it actually did the translation the first time I tried it. So far (after 5 minutes) I discovered two problems:
1. Listboxes are translated with a empty string as placeholder where the optional array should be
2. The Menu Add String translates as CONTROL ADD MENU.
Peter Redei

I haven't added support for the .List property yet, but that's definately on the cards for the next update. Menu support will come a bit later, I didn't initially have them in mind for this but it should be easy enough to incorporate - I'll see what I can do.
One quirk I've noticed is that when you have controls inside a frame on your VB form, their .Top and .Left properties are calculated by VB from the Frame, not the Form. This will cause those controls to be at abnormal positions. The easy workaround: Select and cut the controls out of the frame, then paste them onto the form - you can then move them into the same position over the frame, but they will no longer be inside it, and as such FRM2DDT will be able to calculate the positions correctly.
If anybody using FRM2DDT feels like modifying/adding code, feel free to post here, I can use all the help I can get as spare time is hard to come by!
Cheers,
Wayne
------------------
Leave a comment: