Brass Tilde wrote:
>>I'm not sure, but are the frx files really necessary? I always thought
>>you could compile a VB6 program even without those. AFAIK, those files
>>are just auto-generated by the form designer for internal use (i.e. it
>>keeps the guidance grid, lines, ... but not the actual form).
>
>
> Unfortunately, they sometimes are necessary. Depending on what controls are on the form, the IDE may save some information about
> one or more of those controls in the FRX file. The compiler needs that info to compile the form. Sometimes the IDE creates an FRX
> file, even when it's not needed. You can safely delete those types, but figuring out which ones are necessary and which aren't can
> be...involved.
>
> I haven't taken the time to figure out what controls actually require them to be present.
In case anyone gets the idea I had of writing a program to merge frm/frx
pairs by adjusting the offsets: don't bother.
At least one of the possible formats that is stored in the frx file is
actually sensitive to its position within the file. For more
information, see this link:
http://www.whippleware.com/VBLM/webhelp/vblm/the_oleobjectblob_problem.htm
If you've got the time to separate out the logic, I would go with
Robin's planned approach. It also allows for unit testing of the logic,
but it's a pain in the arse. Michael Feathers did a good write up of
this technique called "The Humble Dialog Box".
http://www.google.com/search?q=humble+dialog
Sadly we've not been given the time at my work, so we are stuck on a 6
month release cycle with no branching. :-(
James
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Jun 29 14:57:26 2005