Re: Need help in getting started with writing the integration test

Thank you. I have created a single test case for the typewriter toolbutton and have pushed it to the gsoc2018_typewriter branch. I have defined 3 test cases as follows: 1. Check if the toolbar buttons contain the "Typewriter" button - Done 2. Click the typewriter button, start PickPointEngine

[okular] [Bug 395150] New: Okular print dialog always resets to duplex: none

https://bugs.kde.org/show_bug.cgi?id=395150 Bug ID: 395150 Summary: Okular print dialog always resets to duplex: none Product: okular Version: 1.3.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED

Re: Need help in getting started with writing the integration test

Hello Tobias, I have succeeded in getting the QInputDialog to write a new note: QMetaObject::invokeMethod(part.m_pageView, "slotToggleAnnotator", Q_ARG( bool, true )); // displayes the annotation toolbar QList toolbuttonList = part.m_pageView->findChildren(); // Get the list of all 10

[okular] [Bug 395132] New: Okular doesn't display some non-ascii characters in main view only. Print preview and text select work fine.

https://bugs.kde.org/show_bug.cgi?id=395132 Bug ID: 395132 Summary: Okular doesn't display some non-ascii characters in main view only. Print preview and text select work fine. Product: okular Version: 1.3.3

[okular] [Bug 395132] Okular doesn't display some non-ascii characters in main view only. Print preview and text select work fine.

https://bugs.kde.org/show_bug.cgi?id=395132 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it --- Comment #1 from

D13203: Add Typewriter annotation tool in Okular

dileepsankhla added inline comments. INLINE COMMENTS > tobiasdeiminger wrote in editannottooldialog.cpp:128 > So from now on ALL annotations (even ink, highlight, inline note etc) that > are created by a user-defined tool will store color as #AARRGGBB in *.okular > document archive, right?

[okular] [Bug 395150] Okular print dialog always resets to duplex: none

https://bugs.kde.org/show_bug.cgi?id=395150 --- Comment #4 from Albert Astals Cid --- Note how he says "the duplex option is preset to none for all printers, even those where long edge duplex is the default at the system level." That is "Qt print dialog doesn't read default options" it's not

[okular] [Bug 395150] Okular print dialog always resets to duplex: none

https://bugs.kde.org/show_bug.cgi?id=395150 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|UNCONFIRMED

[okular] [Bug 395150] Okular print dialog always resets to duplex: none

https://bugs.kde.org/show_bug.cgi?id=395150 --- Comment #3 from Nate Graham --- (In reply to Albert Astals Cid from comment #2) > Nate that bug you pointed has nothing to do with what Sergio is describing. I found https://bugreports.qt.io/browse/QTBUG-5196, which seems to describe Sergio's

Re: Need help in getting started with writing the integration test

Am 08.06.2018 18:57 schrieb Dileep Sankhla: Hello Tobias, I have succeeded in getting the QInputDialog to write a new note: QMetaObject::invokeMethod(part.m_pageView, "slotToggleAnnotator", Q_ARG( bool, true )); // displayes the annotation toolbar QList toolbuttonList =

[okular] [Bug 395150] Okular print dialog always resets to duplex: none

https://bugs.kde.org/show_bug.cgi?id=395150 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #2 from Albert

[okular] [Bug 395150] Okular print dialog always resets to duplex: none

https://bugs.kde.org/show_bug.cgi?id=395150 --- Comment #5 from Nate Graham --- Ah, thanks Albert. My mistake. -- You are receiving this mail because: You are the assignee for the bug.

[okular] [Bug 395158] Okular crashed after closing a troublesome PDF document

https://bugs.kde.org/show_bug.cgi?id=395158 --- Comment #1 from yst...@posteo.net --- Created attachment 113156 --> https://bugs.kde.org/attachment.cgi?id=113156=edit Troublesome PDF file -- You are receiving this mail because: You are the assignee for the bug.