Replacement for standard OLE image control

[Richard Kaye]

I wish this had come up when I was at SWFox last week...

As we all should know, the VFP OLE image control is...a bit long in the tooth. I just ran across an issue today with a client who was complaining that just recently some of his beautiful images are turning into pixelated goo. Of course, trying to figure out what is the underlying root cause is problematic at best. The display mechanism is reading a file from disk and using it as the source for a standard VFP OLE image control. So whilst I once again start my research out on the greater internet, I look to the collective wisdom here. Anybody using a 3rd party image control that does not have the underlying problems that come with using a native Windows control stuck in ~2003? Or otherwise have any other solutions for displaying JPGs in their UI?

TIA

--

rk



--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---

_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/***@BN6PR10MB1299.namprd10.prod.outlook.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

[Tracy Pearson]

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 normal form. Then have a way to view the full size image.
Enabling scrollbars on a form?

Good luck on your quest.

Tracy


-----Original Message-----
From: ProfoxTech [mailto:profoxtech-***@leafe.com] On Behalf Of Richard
Kaye
Sent: Tuesday, October 23, 2018 6:21 PM
To: ***@leafe.com
Subject: Replacement for standard OLE image control

I wish this had come up when I was at SWFox last week...

As we all should know, the VFP OLE image control is...a bit long in the
tooth. I just ran across an issue today with a client who was complaining
that just recently some of his beautiful images are turning into pixelated
goo. Of course, trying to figure out what is the underlying root cause is
problematic at best. The display mechanism is reading a file from disk and
using it as the source for a standard VFP OLE image control. So whilst I
once again start my research out on the greater internet, I look to the
collective wisdom here. Anybody using a 3rd party image control that does
not have the underlying problems that come with using a native Windows
control stuck in ~2003? Or otherwise have any other solutions for displaying
JPGs in their UI?

TIA

--

rk



--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/000301d46ba3$62e4a560$28adf020$@powerchurch.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

[Richard Kaye]

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 what that something is; perhaps number of colors in the JPG but so far we just haven't been able to figure out what the breaking factor is. Which is why I was hoping there might be a 3rd party COM control out there that others here have used. The DBI controls focus more on composite controls like calendar. No luck yet finding an out of the box image control.

--

rk

-----Original Message-----
From: ProfoxTech <profoxtech-***@leafe.com> On Behalf Of Tracy Pearson
Sent: Wednesday, October 24, 2018 10:11 AM
To: ***@leafe.com
Subject: RE: Replacement for standard OLE image control

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 normal form. Then have a way to view the full size image.
Enabling scrollbars on a form?

Good luck on your quest.

Tracy


-----Original Message-----
From: ProfoxTech [mailto:profoxtech-***@leafe.com] On Behalf Of Richard Kaye
Sent: Tuesday, October 23, 2018 6:21 PM
To: ***@leafe.com
Subject: Replacement for standard OLE image control

I wish this had come up when I was at SWFox last week...

As we all should know, the VFP OLE image control is...a bit long in the tooth. I just ran across an issue today with a client who was complaining that just recently some of his beautiful images are turning into pixelated goo. Of course, trying to figure out what is the underlying root cause is problematic at best. The display mechanism is reading a file from disk and using it as the source for a standard VFP OLE image control. So whilst I once again start my research out on the greater internet, I look to the collective wisdom here. Anybody using a 3rd party image control that does not have the underlying problems that come with using a native Windows control stuck in ~2003? Or otherwise have any other solutions for displaying JPGs in their UI?


_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/***@BN6PR10MB1299.namprd10.prod.outlook.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

[Peter Cushing]

Post by Richard Kaye
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 what that something is; perhaps number of colors in the JPG but so far we just haven't been able to figure out what the breaking factor is. Which is why I was hoping there might be a 3rd party COM control out there that others here have used. The DBI controls focus more on composite controls like calendar. No luck yet finding an out of the box image control.

What do you have for the 'stretch' setting on the control?  There is
clip (default), isometric and stretch.  I use isometric on a few screens
and never had a problem with pixelating.  I used to get an occasional
problem with JPG output from adobe illustrator where the picture would
appear black in Foxpro but no problems viewing from the O/S.  We just
got them to save it a different way and that fixed it.

Peter


This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.

www.whisperingsmith.com

Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR.
Tel:[phone]
Fax:[phone]

London Office: 101 St. Martin's Lane,London, WC2N 4AZ Tel:[phone]




_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/64c8956c-be89-bb26-2f32-***@whisperingsmith.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see

[Ted Roche]

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 might like them to.

At least as a debugging tool, it might tell you if it's the app, the FoxPro
host, or that maybe the client's video adapter is set to 16-bit rather than
24-.

Post by Richard Kaye
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 what that something is; perhaps
number of colors in the JPG but so far we just haven't been able to figure
out what the breaking factor is. Which is why I was hoping there might be a
3rd party COM control out there that others here have used. The DBI
controls focus more on composite controls like calendar. No luck yet
finding an out of the box image control.
--
rk
-----Original Message-----
Sent: Wednesday, October 24, 2018 10:11 AM
Subject: RE: Replacement for standard OLE image control
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 normal form. Then have a way to view the full size image.
Enabling scrollbars on a form?
Good luck on your quest.
Tracy
-----Original Message-----
Sent: Tuesday, October 23, 2018 6:21 PM
Subject: Replacement for standard OLE image control
I wish this had come up when I was at SWFox last week...
As we all should know, the VFP OLE image control is...a bit long in the
tooth. I just ran across an issue today with a client who was complaining
that just recently some of his beautiful images are turning into pixelated
goo. Of course, trying to figure out what is the underlying root cause is
problematic at best. The display mechanism is reading a file from disk and
using it as the source for a standard VFP OLE image control. So whilst I
once again start my research out on the greater internet, I look to the
collective wisdom here. Anybody using a 3rd party image control that does
not have the underlying problems that come with using a native Windows
control stuck in ~2003? Or otherwise have any other solutions for
displaying JPGs in their UI?

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4tCWW5HKeYE0ELZ7b8hs=***@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

[Richard Kaye]

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 by stretching or clipping.

--

rk

-----Original Message-----
From: ProfoxTech <profoxtech-***@leafe.com> On Behalf Of Ted Roche
Sent: Wednesday, October 24, 2018 11:10 AM
To: ***@leafe.com
Subject: Re: Replacement for standard OLE image control

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 might like them to.

At least as a debugging tool, it might tell you if it's the app, the FoxPro host, or that maybe the client's video adapter is set to 16-bit rather than 24-.

Post by Richard Kaye
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 what that something is;
perhaps number of colors in the JPG but so far we just haven't been
able to figure out what the breaking factor is. Which is why I was
hoping there might be a 3rd party COM control out there that others
here have used. The DBI controls focus more on composite controls like
calendar. No luck yet finding an out of the box image control.
--
rk
-----Original Message-----
Sent: Wednesday, October 24, 2018 10:11 AM
Subject: RE: Replacement for standard OLE image control
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 normal form. Then have a way to view the full size image.
Enabling scrollbars on a form?
Good luck on your quest.
Tracy
-----Original Message-----
Sent: Tuesday, October 23, 2018 6:21 PM
Subject: Replacement for standard OLE image control
I wish this had come up when I was at SWFox last week...
As we all should know, the VFP OLE image control is...a bit long in
the tooth. I just ran across an issue today with a client who was
complaining that just recently some of his beautiful images are
turning into pixelated goo. Of course, trying to figure out what is
the underlying root cause is problematic at best. The display
mechanism is reading a file from disk and using it as the source for a
standard VFP OLE image control. So whilst I once again start my
research out on the greater internet, I look to the collective wisdom
here. Anybody using a 3rd party image control that does not have the
underlying problems that come with using a native Windows control
stuck in ~2003? Or otherwise have any other solutions for displaying JPGs in their UI?

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/***@BN6PR10MB1299.namprd10.prod.outlook.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

[Alan Bourke]

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: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/***@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

[Richard Kaye]

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 to a UI component I can just swap in for the standard OLE control.

--

rk

-----Original Message-----
From: ProfoxTech <profoxtech-***@leafe.com> On Behalf Of Alan Bourke
Sent: Wednesday, October 24, 2018 11:33 AM
To: ***@leafe.com
Subject: Re: Replacement for standard OLE image control

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: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/***@BN6PR10MB1299.namprd10.prod.outlook.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.