Just another Foxite.COM Community Weblog site
this version has minor bug fixes and some help updates.
read the help file in outlook2003bar\vcx folder to know how to use the control.
please, feel free to make comments, send suggestions or request bug fixes.
this control is part of vfpx, a visual foxpro community effort to create open source add-ons for visual foxpro 9.0.
vfp 9 introduces a new reporting system based on listeners (object-assisted output).
listeners can be customized in a variety of ways and there's a lot of amazing things you can do with it.
if you combine the power of gdi+ with customized listeners you can highly increase the reporting capabilities.
i'll show how you can customize the report listener to create a watermark in all report pages and how you can customize report preview to change the language of report preview toolbar buttons and display the preview window maximized.
set classlib to (addbs(home()) + "ffc\_gdiplus.vcx") additive *… Continue reading
in the last days, i worked on a new version of the outlook2003bar control, making some adjusts and adding new features.
the look has minor changes...
1) now you don't need to add the buttons manually! the only thing you need to do is add the pages in the panes pageframe control inside outlook2003bar and set: caption, picture16 and picture24 page's properties and the control will automatically create the buttons at runtime.
2) added predefined color schemes that follows blue, silver and olive windows xp themes. if you change the active windows xp theme, the control color scheme is changed too!… Continue reading
here is the beta version of my outlook2003bar control (that has the same look and features found in microsoft outlook 2003 left bar), entirely written in vfp 9.
if you have any suggestion or wants to report a bug, contact me.
as soon as i can, i'll post a help and more details on how to use outlook2003bar.
do you want to refine your code for performance and ensure that you've adequately tested the code?
the easiest way to track wich lines of code have been executed and how long it took to execute them is logging code coverage information.
this information can help you identify areas of code that aren't being executed and therefore aren't being tested, as well as areas of the code that you might want to fine tune for performance.
you can toggle coverage logging on and off programmatically (at design time and runtime) by using the set coverage to command.
you could, for example, include… Continue reading