This project is read-only.

xTools Updates

Topics: Bug Information
May 28, 2008 at 12:14 PM
How do we want to go about making changes to the various xBase tools like Task List, Toolbox, etc?

Separate projects or some other way?

I just proposed some updates to the Task List manager but we may want to identify a different approach.
May 28, 2008 at 10:13 PM
I believe what will happen is that things will get slightly reorganized as we get project managers for all of these individual tools, class libraries, etc. For now the source is checked in to source control here. As new releases containing enhancements and bug fixes are ready to go I will create a new zip release at this end and/or I will reorganize at that time to provide granularity that is needed to move components forward seperately. That all having been said, the VFPX admins are completely open to any other ideas the Community may have for handling this type of thing. So, any thoughts or ideas on how best to handle this?
May 29, 2008 at 3:36 PM
What's a little bit confusing right now is that in Releases we have the XSource from SP2 whereas the one in the repository on the Source Code tab seem to be the one from SP1 or the RTM release.
May 31, 2008 at 10:12 AM

I'll check into this. Thank you for the heads up.
Jun 5, 2008 at 1:05 PM

Thanks for letting us know. I was unable to do an accurate compare to determine what version the files where, but after verifying that there had been no checkins since the original post, I resubmitted everything using the latest SP2 files.
Jun 6, 2008 at 9:34 AM

I'm wondering if you could enlighten me as to what you looked at in the XSource and were able to ascertain that it wasn't the SP2 source? Just curious what change(s) you looked for.
Jun 6, 2008 at 10:27 AM
Edited Jun 6, 2008 at 10:29 AM
I was looking at the report applications. The ones that are available as XSource SP2 download ( have the bug that you can't hide the preview window and show it again without raising an error ( The ones available in the source code repository  (http://localhost:8081/ did not have that code (the CreateCanvases) method. The VCA files where up-to-date, only the VCX files was outdated. Hence, if you did a Diff inside VFP you wouldn't have noticed the problem, only when you actually looked at the VCXes (what I did).