ShellExecute window size ignored

List overview All Threads
Download

newer

older

Online Dues Payments

MSXML.DomDocument

Paul Newton

11 Apr 2016 11 Apr '16

9:48 a.m.

Hi all

I am trying to view a PDF in a maximized window

ShellExecute(lcCallingWindow, "Open", lcFileName, "", "", 3)

The last parameter _should_ force the application window to be maximized but it doesn't :(

The default application for PDFs on my system is Adobe Reader XI V11.0.09 and I am running Windows 7. Has anybody else had a similar issue?

Thanks

Paul Newton

Show replies by date

Fernando D. Bozzo

11 Apr 11 Apr

11:03 a.m.

Hi Paul:

lcCallingWindow should be numeric, and normally is 0.

Try if this makes any difference El 11/4/2016 11:49 a. m., "Paul Newton" Paul.Newton@pegasus.co.uk escribió:

...

Hi all

I am trying to view a PDF in a maximized window

ShellExecute(lcCallingWindow, "Open", lcFileName, "", "", 3)

The last parameter _should_ force the application window to be maximized but it doesn't :(

The default application for PDFs on my system is Adobe Reader XI V11.0.09 and I am running Windows 7. Has anybody else had a similar issue?

Thanks

Paul Newton

[excessive quoting removed by server]

Paul Newton

11:27 a.m.

Thanks but I tried that and it still didn't work - it was another developer who wrote the code and assigned a numeric value to lcCallingWindow instead of lnCallingWindow

-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Fernando D. Bozzo Sent: 11 April 2016 12:04 To: profoxtech@leafe.com Subject: Re: ShellExecute window size ignored

Hi Paul:

lcCallingWindow should be numeric, and normally is 0.

Try if this makes any difference El 11/4/2016 11:49 a. m., "Paul Newton" Paul.Newton@pegasus.co.uk escribió:

...

Hi all

I am trying to view a PDF in a maximized window

ShellExecute(lcCallingWindow, "Open", lcFileName, "", "", 3)

The last parameter _should_ force the application window to be maximized but it doesn't :(

The default application for PDFs on my system is Adobe Reader XI V11.0.09 and I am running Windows 7. Has anybody else had a similar issue?

Thanks

Paul Newton

[excessive quoting removed by server]

Dave Crozier

12:27 p.m.

Paul, I don't use Adobe it is a pain but the equivalent runs with FoxitReader PDF reader. Set up cParams to be path to the PDF to open.

DECLARE INTEGER ShellExecute IN shell32.dll ; INTEGER hndWin, ; STRING cAction, ; STRING cFileName, ; STRING cParams, ; STRING cDir, ; INTEGER nShowWin

cParams="" cFileName = "C:\Program Files (x86)\Foxit Software\Foxit Reader\foxitreader.exe" cAction = "open"

*nMode = 1 && Standard Window nMode = 3 && Full screen ShellExecute(0,cAction,cFileName,cParams,"",nMode)

-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Paul Newton Sent: 11 April 2016 12:27 To: profox@leafe.com Subject: RE: ShellExecute window size ignored

Thanks but I tried that and it still didn't work - it was another developer who wrote the code and assigned a numeric value to lcCallingWindow instead of lnCallingWindow

Hi Paul:

lcCallingWindow should be numeric, and normally is 0.

Try if this makes any difference El 11/4/2016 11:49 a. m., "Paul Newton" Paul.Newton@pegasus.co.uk escribió:

...

Hi all

I am trying to view a PDF in a maximized window

ShellExecute(lcCallingWindow, "Open", lcFileName, "", "", 3)

The last parameter _should_ force the application window to be maximized but it doesn't :(

The default application for PDFs on my system is Adobe Reader XI V11.0.09 and I am running Windows 7. Has anybody else had a similar issue?

Thanks

Paul Newton

[excessive quoting removed by server]

Dave Crozier

12:28 p.m.

Oh, and the hndWin parameter is numeric

Dave

-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Dave Crozier Sent: 11 April 2016 13:27 To: ProFox Email List profox@leafe.com Subject: RE: ShellExecute window size ignored

Paul, I don't use Adobe it is a pain but the equivalent runs with FoxitReader PDF reader. Set up cParams to be path to the PDF to open.

DECLARE INTEGER ShellExecute IN shell32.dll ; INTEGER hndWin, ; STRING cAction, ; STRING cFileName, ; STRING cParams, ; STRING cDir, ; INTEGER nShowWin

cParams="" cFileName = "C:\Program Files (x86)\Foxit Software\Foxit Reader\foxitreader.exe" cAction = "open"

*nMode = 1 && Standard Window nMode = 3 && Full screen ShellExecute(0,cAction,cFileName,cParams,"",nMode)

-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Paul Newton Sent: 11 April 2016 12:27 To: profox@leafe.com Subject: RE: ShellExecute window size ignored

Thanks but I tried that and it still didn't work - it was another developer who wrote the code and assigned a numeric value to lcCallingWindow instead of lnCallingWindow

Hi Paul:

lcCallingWindow should be numeric, and normally is 0.

Try if this makes any difference El 11/4/2016 11:49 a. m., "Paul Newton" Paul.Newton@pegasus.co.uk escribió:

...

Hi all

I am trying to view a PDF in a maximized window

ShellExecute(lcCallingWindow, "Open", lcFileName, "", "", 3)

The last parameter _should_ force the application window to be maximized but it doesn't :(

The default application for PDFs on my system is Adobe Reader XI V11.0.09 and I am running Windows 7. Has anybody else had a similar issue?

Thanks

Paul Newton

[excessive quoting removed by server]

_______________________________________________ Post Messages to: ProFox@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/CAGQ_Jums0WCMhyHONUQVBLA-qV4AaTCOq-yQ... ** 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. Report [OT] Abuse: http://leafe.com/reportAbuse/CAGQ_Jums0WCMhyHONUQVBLA-qV4AaTCOq-yQCD6DpYeXw9... _______________________________________________ Post Messages to: ProFox@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/9A8106AFB0EF9B44B69045C4448935A201410... ** 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. _______________________________________________ Post Messages to: ProFox@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/18725B8CD2D5D247873A2BAF401D4AB2852CF... ** 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.

Fernando D. Bozzo

12:35 p.m.

Hi Paul:

The problem is that Adobe Reader is not a normal application, and do not respect normal messages.

I've found an awful hack, but seem to work:

http://superuser.com/questions/640174/how-to-start-adobe-reader-with-window-...

2016-04-11 13:27 GMT+02:00 Paul Newton Paul.Newton@pegasus.co.uk:

...

Thanks but I tried that and it still didn't work - it was another developer who wrote the code and assigned a numeric value to lcCallingWindow instead of lnCallingWindow

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

Paul Newton

12:38 p.m.

Thank you Fernando

-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Fernando D. Bozzo Sent: 11 April 2016 13:35 To: profoxtech@leafe.com Subject: Re: ShellExecute window size ignored

Hi Paul:

The problem is that Adobe Reader is not a normal application, and do not respect normal messages.

I've found an awful hack, but seem to work:

http://superuser.com/questions/640174/how-to-start-adobe-reader-with-window-...

2016-04-11 13:27 GMT+02:00 Paul Newton Paul.Newton@pegasus.co.uk:

...

Thanks but I tried that and it still didn't work - it was another developer who wrote the code and assigned a numeric value to lcCallingWindow instead of lnCallingWindow

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

[excessive quoting removed by server]

Ted Roche

1:02 p.m.

Another point of view to consider here is that, in using ShellExecute, you're yielding to Windows to open the PDF in the registered application. It may be the default Reader in some OS. It may be FoxIt, as someone's already mentioned. It may be the full Adobe Suite, if someone has that installed. Or it may be CutePDF reader or PDFCreator. Or the VIP reader for the blind.

If you're dealing with an in-house app where you control the desktop, or if you ship a reader with your app, you may have more control to get the effect you want. But if you just want to launch "the reader" you might have to depend on the user to set things the way they would prefer.

On Mon, Apr 11, 2016 at 8:38 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote:

...

Thank you Fernando

-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Fernando D. Bozzo Sent: 11 April 2016 13:35 To: profoxtech@leafe.com Subject: Re: ShellExecute window size ignored

Hi Paul:

The problem is that Adobe Reader is not a normal application, and do not respect normal messages.

I've found an awful hack, but seem to work:

http://superuser.com/questions/640174/how-to-start-adobe-reader-with-window-...

2016-04-11 13:27 GMT+02:00 Paul Newton Paul.Newton@pegasus.co.uk:

...
Thanks but I tried that and it still didn't work - it was another developer who wrote the code and assigned a numeric value to lcCallingWindow instead of lnCallingWindow

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

[excessive quoting removed by server]

3601

Age (days ago)

3601

Last active (days ago)

profox@leafe.com

7 comments

4 participants

tags (0)

participants (4)

Dave Crozier
Fernando D. Bozzo
Paul Newton
Ted Roche