At 04:08 2018-10-24, Ted Roche wrote:
[snip]
"Throw it over the wall and see how loud they scream" is not a testing
methodology.
Sure it is. It works great for testing a heuristic-based
targeting system.
Sincerely,
Gene "straight over or with a bit of a curve?" Wirchenko
No, not useful at all, except if you want to make the EXE bigger and allow
decompiling them too.
Regards,
Fernando D Bozzo
El mié., 24 oct. 2018 19:32,
escribió:
> VFP9SP2
>
> Since .h #INCLUDE files are only utilized at build time, is there any
> reason you'd want to include the .h files in
VFP9SP2
Since .h #INCLUDE files are only utilized at build time, is there any
reason you'd want to include the .h files in the EXE? I'm thinking
"no."
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance:
"Throw it over the wall and see how loud they scream" is not a testing
methodology.
Love it!
John Weller
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list:
Another good thought. I'm also cruising through the WW docs since Rick has an
image handling DLL as part of the package. If I go this route I probably have
to write my own wrapper around the Windows API calls since most of what I've
seen so far are more for manipulation of the image as opposed
The GDIPlusX project on Github
(https://github.com/VFPX/GDIPlusX/blob/master/documents/GDIPlusX_Library_Reference.md)
might have something.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
___
Post Messages to: ProFox@leafe.com
Subscription
Thanks, Ted. I was thinking of trying the browser control. I'm still not
certain that any graphics handling that VFP might call is going to do anything
other than use the image handling code from Windows 3.x but it's worth a shot.
Peter, I have it set to isometric so the problem is not caused
It's overkill, but you could embed a webbrowser control. MS and other
vendors have a bad habit of shipping proof of concept controls we base
production applications on, or go out of business or otherwise cease
supporting an app, but it's unlikely MS will go out of the browser
business, much as we
On 24/10/2018 15:43, Richard Kaye wrote:
Thanks for the reply, Tracy.
Very high res images but some display fine while others pixelate. I am storing
directly in the file system with no transforms. They look fine if you preview
in OS but the ancient OLE image control doesn't like something.
Thanks for the reply, Tracy.
Very high res images but some display fine while others pixelate. I am storing
directly in the file system with no transforms. They look fine if you preview
in OS but the ancient OLE image control doesn't like something. The tricky part
has been determining just
Testing is done differently today than it was 20 years ago.
It doesn't replace real people from final testing but it does reduce their
need on early bugs that is for sure.
I don't allow your code to be saved if your code breaks the build we have
in place. You get notified of it right after you
I use the built in image control to view imported pictures.
I use an old LeadTools product to resize the image to 800x600 before storing
it.
Is your customers images from a 12 megapixel or higher camera?
You could use one of the available ways to reduce the image size for
displaying in your
On 2018-10-24 04:51, Alan Bourke wrote:
I think Windows has gotten too complex for MS to understand. Shadow
directories and fake redirections and everything dependent not on the
OS or
the File System, but the Registry, may just be a step too far.
What's actually happened is described pretty
Hey ProFox Community,
Just wanted to give an endorsement to Rick Schummer's and Frank Perez'
automatic VFP backup product, CleverFox: https://cleverfoxbackup.com/
I use it for some of the Sylvan franchisees I support and it's been
great. Not only is it affordable but it's super easy too. I
On Wed, Oct 24, 2018 at 4:51 AM Alan Bourke wrote:
>
> What's actually happened is described pretty well in this article -
> basically they laid off a load of traditional QA and testing professionals
> in 2014 and are now relying on some sort of crowdsourced bullshit for QA,
> using people who
> I think Windows has gotten too complex for MS to understand. Shadow
> directories and fake redirections and everything dependent not on the OS or
> the File System, but the Registry, may just be a step too far.
What's actually happened is described pretty well in this article - basically
16 matches
Mail list logo
