[Bug 41354] New: PDF-XChange Editor

https://bugs.winehq.org/show_bug.cgi?id=41354

Bug ID: 41354
           Summary: PDF-XChange Editor
           Product: Wine
           Version: 1.9.19
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Hello, PDF XChange Editor has a bug in wine where it only accepts form input a
few times. When in a PDF document with several forms, it stops accepting form
input after editing several form elements. For example, try typing in one text
field, and then move into another text field. It will no longer accept input.

This is an important bug, because native PDF readers under Linux are pathetic,
and PDF XChange Editor works flawlessly otherwise under Wine.

Thanks!

[Bug 41354] PDF-XChange Editor

https://bugs.winehq.org/show_bug.cgi?id=41354

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from [e-mail] ---
Can you provide the console output while it hangs like this?

[Bug 41354] PDF-XChange Editor

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #2 from Rahim  ---
Created attachment 56090
  --> https://bugs.winehq.org/attachment.cgi?id=56090
debug output, stopped accepting form input after click back and forth between
two forms

Sure, here you go. Thanks!

[Bug 41354] PDF-XChange Editor

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #3 from Rahim  ---
Created attachment 56091
  --> https://bugs.winehq.org/attachment.cgi?id=56091
sample form I used, but **all** fillable PDFs behave the same

[Bug 41354] PDF-XChange Editor

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #4 from [e-mail] ---
What was the program version and could you include it in the title? Also if
this has a free trial that can reproduce the issue please link a download here.

[Bug 41354] PDF-XChange Editor

https://bugs.winehq.org/show_bug.cgi?id=41354

Matteo Guglielmi  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #5 from Matteo Guglielmi  ---
I'm experiencing the same bug when I use the "typewriter" tool.

I'm able to insert/remove text only the first time I use the tool.

After that, as soon as I try to edit the typewriter box again or create a new
one, the cursor inside the box no longer appears and no matter what key I press
on the keyboard, no character makes it to the form.

I'm using the latest version of wine-staging (2.1-1) and pdf-xchange
(6.0.320.1-1) on a Arch Linux box.

[Bug 41354] PDF-XChange Editor

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #6 from Rahim  ---
Unfortunately with PDF-Xchange Editor 6.0.320.1 and Wine 2.1 there is some kind
of major regression where it can't find the main .DLL and the program won't run
at all.

[Bug 41354] PDF-XChange Editor

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #7 from Matteo Guglielmi  ---
Little off topic here but, since I'm new to wine, do bugs like this get usually
fixed quickly or better I get myself a windows box while waiting for the patch?

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
            Summary|PDF-XChange Editor          |PDF-XChange Editor needs
                   |                            |UIAutomationCore.dll
           Keywords|                            |download
                URL|                            |https://www.tracker-softwar
                   |                            |e.com/product/pdf-xchange-e
                   |                            |ditor
     Ever confirmed|0                           |1

--- Comment #8 from Dmitry Timoshkov  ---
Current downloadable version of PDF-XChange Editor 6.0.320.1 depends on
UIAutomationCore.dll which is missing in Wine but is a part of Windows XP
and later. After copying UIAutomationCore.dll from XP installation the app
works without any visible problems. No other components or winetricks are
required for installation and running.

$> wine --version
wine-2.2-972-g5a09901a8d (Staging)

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #9 from Rahim  ---
Hi Dmitry, so the "UIAutomationCore.dll" fixes the original reported issue
about form input, or the recent major issue where it won't run at all?

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #10 from Dmitry Timoshkov  ---
(In reply to Rahim from comment #9)
> Hi Dmitry, so the "UIAutomationCore.dll" fixes the original reported issue
> about form input, or the recent major issue where it won't run at all?

Missing UIAutomationCore.dll prevents PDF XChange Editor from starting
at all. I just tested with a pdf document with multiple input fields and
can't reproduce the problem. Since there is no details about original
PDF XChange Editor version it's not clear whether the problem has been
fixed on application or Wine side.

Please retest with recently released wine-staging-2.2.

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #11 from Rahim  ---
Ok, I used Wine 2.2 to test this version:
http://downloads.pdf-xchange.com/PDFXEdit6_Portable.zip
The program does not run anymore out of the box, complaining: "Unable to load
the `PDFXEditCore.x86.dll` module."

I downloaded UIAutomationCore.dll from somewhere, and put it inside the
PDFXEdit directory and added it to the overridden Wine DLLs. Now the program
runs again, but still behaves as before. To reproduce,

1. Download https://bugs.winehq.org/attachment.cgi?id=56091
2. Type in a number into one of the forms
3. Click somewhere outside of the form, in the whitespace. The cursor turns
into a hand
4. Now try to click on another form, it won't work.

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #12 from Dmitry Timoshkov  ---
(In reply to Rahim from comment #11)
> Ok, I used Wine 2.2 to test this version:
> http://downloads.pdf-xchange.com/PDFXEdit6_Portable.zip
> The program does not run anymore out of the box, complaining: "Unable to
> load the `PDFXEditCore.x86.dll` module."
>
> I downloaded UIAutomationCore.dll from somewhere, and put it inside the
> PDFXEdit directory and added it to the overridden Wine DLLs. Now the program
> runs again, but still behaves as before. To reproduce,
> - Download https://bugs.winehq.org/attachment.cgi?id=56091
> - Type in a number into one of the forms
> - Click somewhere outside of the form, in the whitespace. The cursor turns
>
> into a hand
> 4. Now try to click on another form, it won't work.

Following the steps above I still can't reproduce the problem. I've used
32-bit msi installer (not portable) with clean wine prefix and only one
UIAutomationCore.dll added to c:\windows\system32. Same (correct) behaviour
with Windows XP and Windows 7 selected in winecfg.

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #13 from Rahim  ---
Thanks for the reply.

On my system, I had to drop UIAutomationCore.dll in
~/.wine/drive_c/windows/syswow64/ , not system32. This is after installing
from:
http://downloads.pdf-xchange.com/EditorV6.x86.msi

As for the original bug report here, it appears that the MSI installed version
is slightly less buggy in that respect. But I did find a way to reproduce it.
Place your mouse exactly in the spot where you see in the screenshot I'm
attaching. (The pointer should be an open hand icon, which the screenshot
utility didn't capture.)

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #14 from Rahim  ---
Created attachment 57385
  --> https://bugs.winehq.org/attachment.cgi?id=57385
Click right here (there might be other similar locations too)

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

Alistair Leslie-Hughes  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #15 from Alistair Leslie-Hughes  ---
Staging has patches for UIAutomationCore.dll
https://github.com/wine-compholio/wine-staging/tree/master/patches/api-ms-wi...

Do they help?

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #16 from Rahim  ---
Unfortunately I just use a pre-compiled binary Wine, so I can't test the
patches.

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #17 from Matteo Guglielmi  ---
I tried replacing wine-staging-2.2's uiautomationcore.dll with windows's
original one but the problem did not go away. The typewriter tool works fine
(text can be inserted into the corresponding box/input form) only the first
time is used.

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #18 from [e-mail] ---
Should be fixed by this commit:
http://source.winehq.org/git/wine.git/commit/aca0a27cedfde05414112a505f727df...

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #19 from Matteo Guglielmi  ---
(In reply to fjfrackiewicz from comment #18)
> Should be fixed by this commit:
> http://source.winehq.org/git/wine.git/commit/
> aca0a27cedfde05414112a505f727df2e36c95b6

Just installed wine-staging 2.3-1 on a arch linux box but the typewriter tool
problem is still there (works only once, then is dead). Do you know if your
patch made it to this release on arch? Any temporary workaround available?

Thanks.

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

Nikolay Sivov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |uiautomationcore

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #20 from Nikolay Sivov  ---
This commit made it to Wine 2.3, and that's what should be tested, not
wine-staging that has its own stub for this dll.

[Bug 41354] PDF-XChange Editor needs UIAutomationCore.dll

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #21 from Matteo Guglielmi  ---
(In reply to Nikolay Sivov from comment #20)
> This commit made it to Wine 2.3, and that's what should be tested, not
> wine-staging that has its own stub for this dll.

I've removed wine-staging and installed wine 2.3 on the arch linux box. I've
also erased the local folder .pdf-xchange/wine completely, rebooted the system
and started a fresh session of pdf-xchange which triggered wine to recreate
.pdf-xchange/wine and populate it with additional .NET stuff downloaded from
the web I guess.

Unfortunately the problem persists (typewriter tool works only once).

The bug is quite simple to reproduce:

1) open any pdf file with pdf-xchange and select the typewriter tool
2) click anywhere on the pdf and start typing something
3) click anywhere on the pdf and start typing something again (it will not
work)

Can you actually confirm/check if the bug was fixed in wine 2.3?

Thanks.

[Bug 41354] PDF-XChange Editor typewriter tool and form input stops working

https://bugs.winehq.org/show_bug.cgi?id=41354

Rahim  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|PDF-XChange Editor needs    |PDF-XChange Editor
                   |UIAutomationCore.dll        |typewriter tool and form
                   |                            |input stops working

[Bug 41354] PDF-XChange Editor typewriter tool and form input stops working

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #22 from Austin English  ---
(In reply to Matteo Guglielmi from comment #21)
> (In reply to Nikolay Sivov from comment #20)
> > This commit made it to Wine 2.3, and that's what should be tested, not
> > wine-staging that has its own stub for this dll.
>
> I've removed wine-staging and installed wine 2.3 on the arch linux box. I've
> also erased the local folder .pdf-xchange/wine completely, rebooted the
> system and started a fresh session of pdf-xchange which triggered wine to
> recreate .pdf-xchange/wine and populate it with additional .NET stuff
> downloaded from the web I guess.
>
> Unfortunately the problem persists (typewriter tool works only once).
>
> The bug is quite simple to reproduce:
> - open any pdf file with pdf-xchange and select the typewriter tool
> - click anywhere on the pdf and start typing something
> - click anywhere on the pdf and start typing something again (it will not
>
> work)
>
> Can you actually confirm/check if the bug was fixed in wine 2.3?

Can you please attach the new terminal output? It's likely a different issue
that still prevents the tool from working (but the crash itself should be
fixed, as there's now a stub).

[Bug 41354] PDF-XChange Editor typewriter tool and form input stops working

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #23 from Matteo Guglielmi  ---
(In reply to Austin English from comment #22)
> Can you please attach the new terminal output? It's likely a different issue
> that still prevents the tool from working (but the crash itself should be
> fixed, as there's now a stub).

This is the whole output of 'pdf-xchange' fired up in a terminal window with
all duplicated lines being removed (thousands of them actually).

Because the output was scrolling so fast, I cannot tell which lines correspond
to the opening and using of the typewriter tool... but the output is complete
from starting pdf-xchange, opening an empty pdf file, selecting the typewriter
tool and using it two times (first one was successful, second one failed) and
finally closing pdf-xchange.

fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:process:RegisterApplicationRestart (L"/Recover",0)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:imm:ImmGetOpenStatus (0x1c90250): semi-stub
fixme:imm:ImmReleaseContext (0x10076, 0x1c90250): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:ver:GetCurrentPackageId (0x346e570 (nil)): stub
err:ole:CoGetContextToken apartment not initialised
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:resource:GetGuiResources (0xffffffffffffffff,0): stub
fixme:heap:RtlCompactHeap (0x10000, 0x0) stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:win:RegisterTouchWindow (0x10096 00000000): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100b8 00000000): stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x10094 00000000): stub
fixme:msg:ChangeWindowMessageFilter 4a 00000001
fixme:msg:ChangeWindowMessageFilter c062 00000001
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x316e530, 0x316e3e4): semi-stub
fixme:ole:CoGetApartmentType (0x316e538, 0x316e3e4): semi-stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x804e530, 0x804e3e4): semi-stub
fixme:ole:CoGetApartmentType (0x804e538, 0x804e3e4): semi-stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x804e530, 0x804e3e4): semi-stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x20042 00000000): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100ba 00000000): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100bc 00000000): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100be 00000000): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100c0 00000000): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100c2 00000000): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100c4 00000000): stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100c6 00000000): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100ce 00000000): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100d0 00000000): stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:win:RegisterTouchWindow (0x100d2 00000000): stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x316e530, 0x316e3e4): semi-stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x804e530, 0x804e3e4): semi-stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x84ce530, 0x84ce3e4): semi-stub
fixme:ole:CoGetApartmentType (0x84ce538, 0x84ce3e4): semi-stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x84ce530, 0x84ce3e4): semi-stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:ver:GetCurrentPackageId (0xe6ce570 (nil)): stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:msxml:domdoc_setProperty Ignoring property L"NewParser", value 0x22dab0
{VT_BOOL: ffffffff}
fixme:msxml:domdoc_setProperty Unknown property L"NormalizeAttributeValues"
fixme:msxml:domdoc_get_parseError (0x7880e90)->(0x22db08): creating a dummy
parseError
fixme:msxml:domdoc_setProperty Ignoring property L"NewParser", value 0x22d980
{VT_BOOL: ffffffff}
fixme:msxml:domdoc_setProperty Unknown property L"NormalizeAttributeValues"
fixme:msxml:domdoc_get_parseError (0x7869160)->(0x22d9d8): creating a dummy
parseError
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x84ce530, 0x84ce3e4): semi-stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x84ce530, 0x84ce3e4): semi-stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x804e530, 0x804e3e4): semi-stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x804e530, 0x804e3e4): semi-stub
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:font:GetCharacterPlacementW flags 0x00000032 ignored
fixme:ole:CoGetApartmentType (0x804e570, 0x804e414): semi-stub
fixme:ole:CoGetApartmentType (0x316e570, 0x316e414): semi-stub
fixme:ole:CoGetApartmentType (0x83ce570, 0x83ce414): semi-stub
fixme:ole:CoGetApartmentType (0x86ce570, 0x86ce414): semi-stub
fixme:ole:CoGetApartmentType (0x82ce570, 0x82ce414): semi-stub
fixme:ole:CoGetApartmentType (0x87ce570, 0x87ce414): semi-stub
fixme:ole:CoGetApartmentType (0x85ce570, 0x85ce414): semi-stub
fixme:ole:CoGetApartmentType (0x84ce570, 0x84ce414): semi-stub
fixme:ole:CoGetApartmentType (0x346e570, 0x346e414): semi-stub
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:ver:GetCurrentPackageId (0x22fcd0 (nil)): stub

[Bug 41354] PDF-XChange Editor typewriter tool and form input stops working

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #24 from Austin English  ---
(In reply to Matteo Guglielmi from comment #23)
> (In reply to Austin English from comment #22)
> > Can you please attach the new terminal output? It's likely a different issue
> > that still prevents the tool from working (but the crash itself should be
> > fixed, as there's now a stub).
>
> This is the whole output of 'pdf-xchange' fired up in a terminal window with
> all duplicated lines being removed (thousands of them actually).

Please _attach_ (as a file) in the future, don't paste big logs inline.

[Bug 41354] PDF-XChange Editor typewriter tool and form input stops working

https://bugs.winehq.org/show_bug.cgi?id=41354

Gijs Vermeulen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #25 from Gijs Vermeulen  ---
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)

This also triggers bug https://bugs.winehq.org/show_bug.cgi?id=41670

[Bug 41354] PDF-XChange Editor typewriter tool and form input stops working

https://bugs.winehq.org/show_bug.cgi?id=41354

--- Comment #26 from Matteo Guglielmi  ---
Is there any progress/news about this bug affecting the typewriter tool, which
is still present in wine 2.7 (pdf-xchange 6.0, build 322.0).

[Bug 41354] PDF-XChange Editor typewriter tool and form input stops working

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=41354

mirh  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #27 from mirh  ---
(In reply to Rahim from comment #11)
> Ok, I used Wine 2.2 to test this version:
> http://downloads.pdf-xchange.com/PDFXEdit6_Portable.zip
> - Download https://bugs.winehq.org/attachment.cgi?id=56091
> - Type in a number into one of the forms
> - Click somewhere outside of the form, in the whitespace. The cursor turns
>
> into a hand
> 4. Now try to click on another form, it won't work.

I could confirm the issue was still present with 5.0.2. 
I went to check 5.15-staging.. and now I can't seem to reproduce this anymore
even with the original 5.0.2. 
I did try a clean prefix, and to delete the three preferences .dat files to no
avail.

p.s. if you are testing the installer version, native comctl32 makes it crash