Diese Seite mit anderen teilen ...

Informationen zum Thema:
Forum:
WinDev Forum
Beiträge im Thema:
27
Erster Beitrag:
vor 2 Wochen, 3 Tagen
Letzter Beitrag:
vor 3 Tagen, 20 Stunden
Beteiligte Autoren:
ThiloRieger, GuenterP, Al, Paulo Oliveira, Mr Black, Igor Pobi, Steven Sitas, Frans, Michael Drechsel, DerekT, Igy, Olivier P.

Print Preview Problem after Windows Creators Update

Startbeitrag von ThiloRieger am 13.04.2017 14:11

Hello,

after the Windows 10 Creators Update i have problems with the print preview. After opening the preview windows with pdf export oder opening twice, i have no further reaction for mouse cliks on menus or images. The only thing i can do after this is to exit the windows with keystrokes and restart the Program.

Anyone else with such an behavior?

Greetings
Thilo

Antworten:

Hello !

Same problem ! Tested with Windev 18, 19 and 21 !

von Igy - am 13.04.2017 21:40
Hi Thilo,

please send problem report to PC Soft's Free Technical Support!!!

Thank you!

von GuenterP - am 14.04.2017 04:56
Hello,

I have the same problem (WD21):
Have you got any feedback from the PCSoft Technical Support ?

von Olivier P. - am 18.04.2017 12:19
Same problem here.

The problem happens when we export the report to word, excel, html, pdf or xml in the preview window

If you try to print the report the same problem occurs.

von Paulo Oliveira - am 18.04.2017 14:39
Same problem here. But I seem to be able to get control back.

1. iPrintReport is called from a window which is not maximized.
2. Enter Preview --> Run Export --> Exit preview
3. Calling window is frozen. Controls on window do not function.
4. Grab title bar of calling window and reposition window.
5. Calling window is now unfrozen and controls function.

Can't explain it..

It would seem that even though the report has exited, the calling window still behaves as preview is still open, until the calling window is repositioned, then it understand that the report is closed. This is confirmed by placing a trace after iPrintReport. The trace doesn't execute until the window is repositioned.

von Mr Black - am 19.04.2017 02:41
You solution only works if the repositioning of the windows is the first thing you do after closing the preview.

If you try to click in one button before repositioning the window the problem remains.

tested in WD18.

Anyone have news from Montpellier regarding this isue?

von Paulo Oliveira - am 19.04.2017 09:06
I get something very similar to this when running in debug.
If I get an error I have 2 choices.
Click Cancel - Everything carries on as normal.
Click Debug - Code window opens but cannot be edited - well in fact it can but only a character at a time and I need to click on another area of the monitor to get it to display.
Only answer is to close and reopen WD - if I attempt to continue and run the app I get the exact 'dead screen' problem you describe.

von DerekT - am 19.04.2017 10:09
As soon as the preview window is closed, the applicate spikes in CPU. The CPU spike remains until the calling window is repositioned. It not a solution, just some weird behaviour of the problem.

von Mr Black - am 19.04.2017 12:54
I got quick answer from the support team, that they are looking for the problem.

1: "Thank you for the feedback. It seems that the "Creators Update" is not yet available for the french version and we were not aware of this problem.
The problem has been forwarded to our developers. Incident reference is #103 089/214663, please use it when you contact us on this subject. "

2: "The test we made was to export a PDF from the preview twice. Is there anything more to it ? We have not been able to replicate the problem here using version 1703 / build 15063 RTM version (Release to Manufacturing) of the "Creators Update". Please can you tell us what build you are using exactly ? Are you able to replicate the problem using one of the provided example ?"

I gave them the link of this forum and hopefully we can help them to solve the problem.

von ThiloRieger - am 19.04.2017 15:13
My windows version is 1703 / 15063.138

To reproduce the problem using one of the examples just use Examples\Training\WD Advanced Reports\Exe\WD Advanced Reports.exe
steps:
1. Various reports
2. a Euro converter
3. Print
4. Print preview
5. export in PDF
6. Don't open the document
7. Close the preview windows
8. Click Cancel button
And that's it, nathing happens.

test it in your environment and if you get the same result as i have please send it to PCS, you already have one Incident reference.

von Paulo Oliveira - am 19.04.2017 15:27
Solved! Thanks to PCsoft.

"The developers inform me that the problem cause has been found and fixed.
A fix is available for the incident #103089 regarding a freeze in the preview window after installation of the Creators Upgrade for Windows 10 (problem cause : the message loop is receiving an undocumented window message) .

Use this link to download the upgrade for WinDev 21 version "Update 2" (210067F):

http://stg.webdev.info/Telechargement_Support_WEB/US/telec_ST.awp?ID=2934&PDT=WinDev_21&REF=214663

This upgrade includes:

- \framework\linux4\wd210prn.so (1777,11 Ko)
- \framework\linux44_64\wd210prn64.so (1885,95 Ko)
- \framework\win32x86\wd210prn.dll (1932,00 Ko) - version : 21.0.71.19
- \framework\win64x86\wd210prn64.dll (2647,50 Ko) - version : 21.0.71.19

Make sure the upgrade file is unzipped keeping the folder tree (path) into the \Programs\ folder for WinDev 21 and if asked accept to replace any existing files. Then create a new EXE for your application in order to deploy it with the new framework update.

We do apologize for the inconvenience."

von ThiloRieger - am 19.04.2017 18:14
Hello

Now that the problem is fixed, it will be interesting to see how PCSoft handle it.

There is a known conflict between their current software and an operating system used by at least 25% of all PC's running Windows.

V21 English is still current so by their own rules they should release a patch for V20 English - I don't think they will

The altruistic thing would be for PCSoft to email all developers who own V21 and advise them of the problem and the solution. They are capable of doing this as evidenced by past sales emails I have received.

The smart thing would be for them to advise ALL developers of the issue and see it as a sales opportunity to get developers to upgrade to the latest version as software developed in prior versions now may not work in coming versions of Windows 10.

On past performance they be like the three wise monkeys and will do nothing - unless of course they read this message and take heed :)

Regards
Al

von Al - am 19.04.2017 18:41
Thanks Thilo for seeing this through.. I got the update installed and initial testing looks good, problem solved.

I must say that was pretty quick on PCSoft part for getting a fix out in a day or so, but I would have thought they would have been working with insider builds for a while so this wouldn't have been a surprise.. The next W10 build is expected Oct - Nov this year, so perhaps we'll find some time to do some testing once it getting close..

von Mr Black - am 20.04.2017 00:02

Print preview (solved; my own error)

Hello to you all,

Sorry,
Was a 'normal' printer error.

von Frans - am 20.04.2017 10:50
Hello Frans

The instructions that Thilo received from PCSoft and then published here are as follows:

Make sure the upgrade file is unzipped keeping the folder tree (path) into the \Programs\ folder for WinDev 21 and if asked accept to replace any existing files. Then create a new EXE for your application in order to deploy it with the new framework update.

According to your post, you did not follow those instructions. Could you try again as per the instructions and let us know how it went please.

Regards
Al

von Al - am 20.04.2017 10:58
Hi Frans, I hope, he did a restart of their PC before trying again ...

von GuenterP - am 20.04.2017 11:12

Sorry

Sorry,

for the inconvenience.
Was an IP problem after changing a modem. The cutomer did not inform me.
Thanks for the fast reply's.

von Frans - am 20.04.2017 11:20
Hi,
although its great that PCSoft fixed this for v21 - what happens with apps in v20 or v19 etc..?
Since the new Windows update is just around the corner and you CANNOT DISABLE IT, there will be lots of problems with developers who haven't upgraded to v21.

By the way, my antivirus (Norton Security), doesn't like the above patch/web site at all.
It reports various threats (like trojans viruses and remote control surveilance tools ...).
Anybody else seen this ?

Steven Sitas

von Steven Sitas - am 20.04.2017 12:22
Hi Steven,

please see http://stg.webdev.info/publicationSt_WEB/uk/miseajourst.awp?LANGUE=US for the updates from version 16 up to 21!

von GuenterP - am 22.04.2017 16:16
Hi Guenter,

thanks for the info - Great job from PCSoft

Steven Sitas

von Steven Sitas - am 23.04.2017 09:00
Does anyone have direct links to these bug fixes for Windev 18, 19 and 20?
PC SOFT support does not give feedback for two days (receipt of a received request came back to me).
Thank you in advance !

von Igor Pobi - am 25.04.2017 15:31
Two messages above.

von ThiloRieger - am 25.04.2017 20:10
Quote
ThiloRieger
Two messages above.


Where is link for download in this message ?
I see only "Ask for an upgrade", enter serial number and email but for now, support is not answer.

von Igor Pobi - am 25.04.2017 20:52
Hi Igor,

the link contains a reference to the serial number (only jesus knows why ....), so publishing here is not possible ...

von Michael Drechsel - am 26.04.2017 08:16

Do not install Windows Creators Update!

Hi,

Microsoft begs not to install the buggy Windows Creator update!

http://www.theregister.co.uk/2017/04/26/stop_downloading_win10_creators_update/

von GuenterP - am 27.04.2017 05:20

Re: Do not install Windows Creators Update!

Hello Guenter

Sound advice.

I have a Windows 10 machine for testing complied programs, but my development computer is Win7 Pro and will remain so for as long as possible. I have even gone to the extreme step of purchasing a reserve PC with a Broadwell i7 chip because any Intel chip past generation 5 will not support Win7 properly in the future.

http://www.theverge.com/2016/1/16/10780876/microsoft-windows-support-policy-new-processors-skylake

This should see me through until retirement or MS get it right - not sure what will come first :)

Regards
Al

von Al - am 27.04.2017 05:38
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.