Issue 86396 - OOH680_m7 (2.4rc1): PDF Export does not export controls in Writer
Summary: OOH680_m7 (2.4rc1): PDF Export does not export controls in Writer
Status: CLOSED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 2.4 RC1
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: OOo 2.4
Assignee: h.ilter
QA Contact: issues@gsl
URL:
Keywords: regression
: 86274 (view as issue list)
Depends on:
Blocks: 84957
  Show dependency tree
 
Reported: 2008-02-23 20:21 UTC by Giuseppe Castagno (aka beppec56)
Modified: 2009-07-20 14:53 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Writer document used for test (8.29 KB, application/vnd.oasis.opendocument.text)
2008-02-23 20:22 UTC, Giuseppe Castagno (aka beppec56)
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Giuseppe Castagno (aka beppec56) 2008-02-23 20:21:28 UTC
To verify in 2.4rc1 use the attached Writer document.
In GNU/Linux, Debian, KDE.

1) open the document
2) export to PDF enabling the form exporting (select 'Create PDF form'
checkbox), FDF type
3) open the PDF with Acrobat reader
The controls are not exported (nowhere to be seen).

I checked backward tags and the first tag when the issue shows up seems OOH680_m4.
Using OOo 2.3.1 the controls are correctly exported as it does on tag OOH680_m3.

Unless there is a new configuration I wasn't able to find, the PDF form export
functionality seems broken.
Comment 1 Giuseppe Castagno (aka beppec56) 2008-02-23 20:22:33 UTC
Created attachment 51683 [details]
Writer document used for test
Comment 2 helenrussian 2008-02-24 09:59:19 UTC
Confirm with OOo 2.4 RC1 on WinXP, Win98 and OpenSUSE 10.3

I changed OS "Linux" to "All"
Comment 3 Giuseppe Castagno (aka beppec56) 2008-02-24 13:56:21 UTC
-> pl
I did a first rough investigation, using a simple Writer document with a
pushbutton only.
In a debug session limited to the modules I know, I observed:
- method PDFExtOutDevData::SetIsExportFormFields( const sal_Bool
bExportFomtFields ) sets the correct value of the form export flag, according to
the filter interface
- method PDFExtOutDevData::GetIsExportFormFields() never gets called while
exporting the document.
- finally, in method PDFWriterImpl::emitWidgetAnnotations() there is no widget
to export.
Just a wild guess: may be it's application related?
I didn't add the issue to the 2.4 showstopper bugs list because I don't know if
it's related to another one already being investigated.
Comment 4 philipp.lohmann 2008-02-24 14:36:50 UTC
actually I know of this as issue 86274, but up to now I thought this was
SRC680m245 and up only. I'm currently looking into it.
Comment 5 philipp.lohmann 2008-02-24 14:56:49 UTC
Even more curious, if I create a new document containing just a button, it
works, but not with the attached sample.
Comment 6 philipp.lohmann 2008-02-24 15:12:47 UTC
This is even more curious, if I copy the controls from the document to a new one
and export that, it works. If I save the document, close it and open it again,
export to PDF it still works. Just when I end the application, start it again
and export to PDF, it fails.

However the same thing fails the same way in Impress, so I guess this is not
application dependent.
Comment 7 philipp.lohmann 2008-02-24 15:19:01 UTC
However I think this is certainly a stopper issue
Comment 8 kpalagin 2008-02-24 15:24:22 UTC
Here is another example - http://community.i-rs.ru/index.php?
action=dlattach;topic=7701.0;attach=5524 .

Comment 9 kpalagin 2008-02-24 15:28:58 UTC
Philipp,
as mentioned in Russian-language discussion[*] controls are exported until you 
save and close file. Once you open existing file controls would not export.

*http://community.i-rs.ru/index.php/topic,7701.msg49009/topicseen.html#msg49009
Comment 10 philipp.lohmann 2008-02-24 15:48:42 UTC
Debugging I see that we never reach describePDFControl in
svx/source/form/formpdfexport.cxx in case the document was loaded (we come
though there if exporting a new document however).

Insetad I get asertions on the commandline (I compiled svx/source/form with
debug) saying

Error: File
/export/home/pl93762/vclshowstop14/svx/source/form/fmcontrolbordermanager.cxx,
Line 399: ControlBorderManager::validityChanged: invalid control/peer!
Backtrace: [0] /export/home/pl93762/vclshowsto

I'm a little out of my field of experience in svx and forms, could you please
have a look ?
Comment 11 philipp.lohmann 2008-02-24 15:58:54 UTC
just confirming what everybody expected: same behavior on Windows
Comment 12 Frank Schönheit 2008-02-24 20:50:25 UTC
fs->aw: just notifying you ATM. I need to investigate, but my gut feeling is
I'll return to you on the topic ...
Comment 13 Frank Schönheit 2008-02-25 09:08:54 UTC
note: this is a regression between OOH680m3 and OOH680m4.
Comment 14 Frank Schönheit 2008-02-25 09:28:13 UTC
namely a regression of issue 82791
Comment 15 Frank Schönheit 2008-02-25 09:52:02 UTC
Okay, the fix for issue 82791 (resp. issue 83611) triggered a long-standing bug
in our toolkit code - certain controls claimed to be invisible in certain
situations, even if they knew better. Since the drawing routines respect the
visibility of controls with the fix for the above-mentioned issues, and PDF
export unfortunately was such a "certain situation", no controls were exported
anymore.
Comment 16 kpalagin 2008-02-25 10:22:58 UTC
Thanks a lot.
If only all issues could be handled this fast ...
Comment 17 stefan.baltzer 2008-02-25 10:27:01 UTC
SBA: Set keyword "regression" (Broken since OOH_m4).
Comment 18 Frank Schönheit 2008-02-25 12:48:47 UTC
fs-> hi: please verify in CWS formpdfexportfix
Comment 19 h.ilter 2008-02-26 11:59:16 UTC
Verified in CWS formpdfexportfix = OK
Comment 20 philipp.lohmann 2008-03-03 16:26:37 UTC
*** Issue 86274 has been marked as a duplicate of this issue. ***
Comment 21 thorsten.ziehm 2009-07-20 14:53:52 UTC
This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
http://download.openoffice.org/index.html
If you want to know more about the handling of fixed/verified issues =>
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues