[okular] [Bug 486487] New: Open new files in tabs not working

2024-05-02 Thread Tim
https://bugs.kde.org/show_bug.cgi?id=486487

Bug ID: 486487
   Summary: Open new files in tabs not working
Classification: Applications
   Product: okular
   Version: 23.08.1
  Platform: Microsoft Windows
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-devel@kde.org
  Reporter: tgran...@outlook.com
  Target Milestone: ---

SUMMARY
On Windows 11 Pro using version 23.09 "Open new files in tabs" does not change
the behavior of opening new files in their own window. 

PDF Backend Version 0.6.5
A PDF file renderer, Using Poppler 23.09.0

STEPS TO REPRODUCE
1.  Install Okular from Microsoft store on Windows 11 pro
2.  Open Okular for the first time, go to Settings -> General -> Program
Features: and check "Open new files in tabs" and leave "Switch to existing tab
if file is already open" checked.
3.  Try to open two different PDF documents from file explorer

OBSERVED RESULT
Subsequent PDF documents open in their own application windows.

EXPECTED RESULT
Subsequent PDF documents should open in new tabs in the original application
window.

SOFTWARE/OS VERSIONS
Windows: 11 Pro
KDE Plasma Version: Not sure
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 468479] New: 0-length .part files cluttering ~/Downloads after viewing .pdf files

2023-04-13 Thread Tim Murphy
https://bugs.kde.org/show_bug.cgi?id=468479

Bug ID: 468479
   Summary: 0-length .part files cluttering ~/Downloads after
viewing .pdf files
Classification: Applications
   Product: okular
   Version: 22.12.3
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-devel@kde.org
  Reporter: timm...@gmail.com
  Target Milestone: ---

SUMMARY
The okular app is leaving a 0-length *.part file in ~/Downloads after viewing a
.pdf file. This clutters up the ~/Downloads folder.

STEPS TO REPRODUCE
1. with okular set as the preferred (1st) application for .pdf files in plasma
file associations, open a .pdf file when browsing file:///home/tim1/downloads/
within the Firefox browser
2. close pdf
3. ls -alt ~/Downloads

OBSERVED RESULT
 Observe a 0-length *.part file left behind by okular

EXPECTED RESULT
No files left behind in ~/Downloads after viewing a .pdf file

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.27.4
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

Re: Possible to change scroll refresh rate to match monitor

2023-01-07 Thread Tim Hanson
Interesting .. I suspected as much, but thank you for confirming.

I do have one monitor, but yes for whatever reason the display manager
starts up at 60, and the Xsession runs at 120 Hz.

Nonetheless, can confirm that kile scrolls a pdf smoothly at 120Hz in the
preview pane.
What you said makes sense regarding line scrolling in kate -- also smooth /
instantaneous.

Could it be a performance issue?  Seems unlikely as Okular is not
saturating the CPU (a Ryzen 9 5950x...), and scrolling should be pretty
straightforward (unsure how much rendering is batched internally, though).

Cheers,
Tim

Date: Sat, 07 Jan 2023 10:47:51 +0100
From: David Hurka 
To: okular-devel@kde.org
Subject: Re: Possible to change scroll refresh rate to match monitor
(e.g. 120Hz, 144Hz)
Message-ID: <2285352.ElGaqSPkdT@doro>
Content-Type: text/plain; charset="UTF-8"

> Is there some way to get okular to refresh the page faster?
> It seems fixed at 60hz.

Its not possible from within Okular.
According to QScroller documentation, there is a global animation timer
which
sets the update rate.
This timer should match the frame rate of the screen, but apparently that
doesn’t work.
(Maybe you have more than one monitor, or the monitor changes framerate
after
startup, or Qt fails to detect it correctly.)

> Of note other KDE / qt apps refresh at the monitor rate
> (konsole, kate, kile)

It surprises me, because they use either line-wise scrolling, which happens
instantly, or Okular.
If it works in the Kile document preview, that means Kile is better than
the
Okular shell in detecting the framerate.


Possible to change scroll refresh rate to match monitor (e.g. 120Hz, 144Hz)

2023-01-05 Thread Tim Hanson
Hello,

Is there some way to get okular to refresh the page faster?  It seems fixed
at 60hz.  I grepped through the source and only found one instance in
pageview.cpp:3696:
d->dragScrollTimer.start(1000 / 60); // 60 fps
But this does not affect drag to scroll or scrollbar scrolling.

Of note other KDE / qt apps refresh at the monitor rate (konsole, kate,
kile)

pointers appreciated!
thanks,
Tim


[okular] [Bug 420925] Add kinetic scrolling on Trackpad use too

2023-01-05 Thread tim
https://bugs.kde.org/show_bug.cgi?id=420925

tim  changed:

   What|Removed |Added

 CC||imagesfromobje...@gmail.com

--- Comment #8 from tim  ---
(In reply to Nate Graham from comment #1)
> I would like this too.

I just filed a wishlist item for this feature in Dolphin. Similarly, there is a
version of kinetic scrolling when using a mouse wheel, but using a touchpad is
kludgy.

-- 
You are receiving this mail because:
You are the assignee for the bug.

D16048: Resize the preferences dialogue to avoid horizontal scrolling

2018-10-08 Thread Tim __
kadabash added a comment.


  Screenshot before change:
  F6312493: okular_configure_pre_patch.png 

  
  Screenshot after change
  F6312494: okular_configure_post_patch.png 


REPOSITORY
  R223 Okular

REVISION DETAIL
  https://phabricator.kde.org/D16048

To: kadabash
Cc: okular-devel, ngraham, aacid


D16048: Resize the preferences dialogue to avoid horizontal scrolling

2018-10-08 Thread Tim __
kadabash created this revision.
Herald added a project: Okular.
Herald added a subscriber: okular-devel.
kadabash requested review of this revision.

REVISION SUMMARY
  Scrolling horizontally for a small bit of the page feels awkward.
  
BUG: 373957

REPOSITORY
  R223 Okular

BRANCH
  resize_config_window (branched from master)

REVISION DETAIL
  https://phabricator.kde.org/D16048

AFFECTED FILES
  conf/preferencesdialog.cpp

To: kadabash
Cc: okular-devel, ngraham, aacid


[okular] [Bug 334653] Margins are broken when printing a PDF with Cups 1.7.2

2018-01-24 Thread Tim Edwards
https://bugs.kde.org/show_bug.cgi?id=334653

Tim Edwards <tkedwa...@fastmail.com.au> changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|CONFIRMED   |RESOLVED

--- Comment #12 from Tim Edwards <tkedwa...@fastmail.com.au> ---
I did a couple of test prints of PDF documents. I don't see this problem
anymore, closing

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 334653] Margins are broken when printing a PDF with Cups 1.7.2

2018-01-18 Thread Tim Edwards
https://bugs.kde.org/show_bug.cgi?id=334653

--- Comment #10 from Tim Edwards <tkedwa...@fastmail.com.au> ---
Please leave this open for a while? I'll test again when I get new printer ink
cartridges

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Okular-devel] [okular] [Bug 334653] Margins are broken when printing a PDF with Cups 1.7.2

2016-02-09 Thread Tim Edwards via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=334653

--- Comment #8 from Tim Edwards <tkedwa...@fastmail.com.au> ---
If this bug can't be fixed would it be better instead to just have Okular use
the lpr command directly to print things? That works as a manual workaround for
me at the moment

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel


[Okular-devel] [okular] [Bug 359122] New: Okular always cuts off the top approx 1cm of each page when printing

2016-02-07 Thread Tim Edwards via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359122

Bug ID: 359122
   Summary: Okular always cuts off the top approx 1cm of each page
when printing
   Product: okular
   Version: 0.23.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: printing
  Assignee: okular-devel@kde.org
  Reporter: tkedwa...@fastmail.com.au

I'm using Okular 0.23.2 on Kubuntu 15.10. Whenever I print a PDF file from
Okular the top 1cm (approximately) is cut off. I'm using a HP Photosmart 6510
printer.

This is not a problem with my printer or my CUPS configuration since if I print
with lpr directly the problem doesn't occur. So effectively using lpr is a
workaround:
lpr -o fit-to-page document.pdf


Reproducible: Always

Steps to Reproduce:
1. Download a PDF document, I can always reproduce the problem with this form:
https://www.border.gov.au/Forms/Documents/888.pdf
2. Print it
3.

Actual Results:  
The top 1cm of each page is cut off

Expected Results:  
The page is correctly printed, as it is with this command: lpr -o fit-to-page
document.pdf

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel


[Okular-devel] [okular] [Bug 354970] New: Wishlist for new function

2015-11-06 Thread Tim via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354970

Bug ID: 354970
   Summary: Wishlist for new function
   Product: okular
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: PDF backend
  Assignee: okular-devel@kde.org
  Reporter: timgel...@gmail.com

When filling in the forms on a PDF, there's no way to clear the forms for a new
entry.

Reproducible: Always

Steps to Reproduce:
1.Open PDF
2.Enter Forms
3.Fill in entry on forms

Actual Results:  
1.Open PDF
2.Enter Forms
3.Fill in entry on forms

Expected Results:  
1.Open PDF
2.Enter Forms
3.Fill in entry on forms
4.Clear entry on forms for new entry

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel


[Okular-devel] [okular] [Bug 348172] Scaling options missing in print dialog

2015-10-02 Thread Tim Eberhardt
https://bugs.kde.org/show_bug.cgi?id=348172

Tim Eberhardt <tim.eberha...@tu-bs.de> changed:

   What|Removed |Added

 CC||tim.eberha...@tu-bs.de

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel


[Okular-devel] [okular] [Bug 111254] Desire on-screen ruler functionality

2014-10-22 Thread Tim Landscheidt
https://bugs.kde.org/show_bug.cgi?id=111254

Tim Landscheidt t...@tim-landscheidt.de changed:

   What|Removed |Added

 CC||t...@tim-landscheidt.de

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel


[Okular-devel] [okular] [Bug 324731] New: opening an pdf document, it crash

2013-09-09 Thread tim ling
https://bugs.kde.org/show_bug.cgi?id=324731

Bug ID: 324731
   Summary: opening an pdf document, it crash
Classification: Unclassified
   Product: okular
   Version: 0.16.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-devel@kde.org
  Reporter: haoling.gee...@gmail.com

Application: okular (0.16.5)
KDE Platform Version: 4.10.5
Qt Version: 4.8.5
Operating System: Linux 3.10.10-100.fc18.i686 i686
Distribution: Fedora release 18 (Spherical Cow)

-- Information about the crash:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library /lib/libthread_db.so.1.
[Current thread is 1 (Thread 0xb7703780 (LWP 20251))]

Thread 2 (Thread 0xb51f4b40 (LWP 20253)):
#0  0xb7740424 in __kernel_vsyscall ()
#1  0x4523ebdb in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0x454b132c in poll (__timeout=-1, __nfds=5, __fds=0xb4802330) at
/usr/include/bits/poll2.h:46
#3  g_poll (fds=0xb4802330, nfds=5, timeout=-1) at gpoll.c:132
#4  0x454a2480 in g_main_context_poll (priority=2147483647, n_fds=5,
fds=0xb4802330, timeout=optimized out, context=0x9655c60) at gmain.c:3584
#5  g_main_context_iterate (context=0x9655c60, block=block@entry=1,
dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3285
#6  0x454a2963 in g_main_loop_run (loop=0x9655c28) at gmain.c:3484
#7  0x45e58feb in gdbus_shared_thread_func (user_data=0x9655c48) at
gdbusprivate.c:277
#8  0x454c8644 in g_thread_proxy (data=0x96939b0) at gthread.c:797
#9  0x45354aff in start_thread (arg=0xb51f4b40) at pthread_create.c:308
#10 0x452490ee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:132

Thread 1 (Thread 0xb7703780 (LWP 20251)):
[KCrash Handler]
#7  0xb0563716 in Poppler::MediaRendition::isValid (this=this@entry=0x9b83330)
at poppler-media.cc:58
#8  0xb0563853 in Poppler::MediaRendition::isEmbedded (this=0x9b83330) at
poppler-media.cc:80
#9  0xb05b7685 in createMovieFromPopplerScreen (popplerScreen=0x9b82b68) at
/usr/src/debug/okular-4.10.5/generators/poppler/generator_pdf.cpp:198
#10 0xb05c3ff7 in createAnnotationFromPopplerAnnotation (ann=0x9b82ac8,
doDelete=0xbfee7b57) at
/usr/src/debug/okular-4.10.5/generators/poppler/annots.cpp:334
#11 0xb05bbe2d in PDFGenerator::addAnnotations (this=this@entry=0x9a37d08,
popplerPage=popplerPage@entry=0x9a72718, page=page@entry=0x9b82538) at
/usr/src/debug/okular-4.10.5/generators/poppler/generator_pdf.cpp:1462
#12 0xb05bc483 in PDFGenerator::loadPages (this=this@entry=0x9a37d08,
pagesVector=..., rotation=rotation@entry=0, clear=clear@entry=false) at
/usr/src/debug/okular-4.10.5/generators/poppler/generator_pdf.cpp:639
#13 0xb05bcd22 in PDFGenerator::init (this=this@entry=0x9a37d08,
pagesVector=..., walletKey=...) at
/usr/src/debug/okular-4.10.5/generators/poppler/generator_pdf.cpp:572
#14 0xb05bf13e in PDFGenerator::loadDocument (this=0x9a37d08, filePath=...,
pagesVector=...) at
/usr/src/debug/okular-4.10.5/generators/poppler/generator_pdf.cpp:466
#15 0xb290abe0 in Okular::DocumentPrivate::openDocumentInternal
(this=0x97c1dd8, offer=..., isstdin=false, docFile=..., filedata=...) at
/usr/src/debug/okular-4.10.5/core/document.cpp:819
#16 0xb2913a66 in Okular::Document::openDocument (this=0x97aa160, docFile=...,
url=..., _mime=...) at /usr/src/debug/okular-4.10.5/core/document.cpp:1907
#17 0xb29d724b in Okular::Part::openFile (this=0x97658e8) at
/usr/src/debug/okular-4.10.5/part.cpp:1214
#18 0x483c77a6 in KParts::ReadOnlyPartPrivate::openLocalFile
(this=this@entry=0x9765a98) at
/usr/src/debug/kdelibs-4.10.5/kparts/part.cpp:591
#19 0x483c7e97 in KParts::ReadOnlyPart::openUrl (this=0x97658e8, url=...) at
/usr/src/debug/kdelibs-4.10.5/kparts/part.cpp:555
#20 0xb29c8333 in openUrl (_url=..., this=0x97658e8) at
/usr/src/debug/okular-4.10.5/part.cpp:1359
#21 Okular::Part::openUrl (this=0x97658e8, _url=...) at
/usr/src/debug/okular-4.10.5/part.cpp:1330
#22 0x0805103c in Shell::openUrl (this=this@entry=0x9754310, url=...) at
/usr/src/debug/okular-4.10.5/shell/shell.cpp:179
#23 0x08051249 in Shell::delayedOpen (this=0x9754310) at
/usr/src/debug/okular-4.10.5/shell/shell.cpp:138
#24 0x4627c55b in QMetaCallEvent::placeMetaCall (this=0x9a08cb8,
object=0x9754310) at kernel/qobject.cpp:524
#25 0x46280bc3 in QObject::event (this=0x9754310, e=0x9a08cb8) at
kernel/qobject.cpp:1194
#26 0x46b97bba in QWidget::event (this=0x9754310, event=0x9a08cb8) at
kernel/qwidget.cpp:8846
#27 0x46fcbfac in QMainWindow::event (this=0x9754310, event=0x9a08cb8) at
widgets/qmainwindow.cpp:1478
#28 0x47ab0c7c in KMainWindow::event (this=0x9754310, ev=0x9a08cb8) at
/usr/src/debug/kdelibs-4.10.5/kdeui/widgets/kmainwindow.cpp:1084
#29 0x47af9173 in KXmlGuiWindow::event (this=0x9754310, ev=0x9a08cb8) at
/usr/src/debug/kdelibs-4.10.5/kdeui/xmlgui/kxmlguiwindow.cpp:126
#30 0x46b3e10c in 

[Okular-devel] [Bug 224424] New: Okular crashed when the file it was showing was removed

2010-01-27 Thread Tim McKenzie
https://bugs.kde.org/show_bug.cgi?id=224424

   Summary: Okular crashed when the file it was showing was
removed
   Product: okular
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: okular-devel@kde.org
ReportedBy: tjm1...@gmail.com


Application that crashed: okular
Version of the application: 0.9.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.31.12-174.2.3.fc12.x86_64 x86_64

What I was doing when the application crashed:
Okular was showing a pdf that was automatically generated.  Another process
changed this pdf, then moved it and removed the directory it was previously
living in.  Okular crashed.

 -- Backtrace:
Application: Okular (okular), signal: Segmentation fault
41  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
[KCrash Handler]
#4  findNode (akey=value optimized out, this=0x27643d0) at
/usr/include/QtCore/qmap.h:431
#5  constFind (akey=value optimized out, this=0x27643d0) at
/usr/include/QtCore/qmap.h:559
#6  Okular::Page::hasPixmap (akey=value optimized out, this=0x27643d0) at
/usr/src/debug/kdegraphics-4.3.4/okular/core/page.cpp:203
#7  0x7f52a0906c65 in Okular::DocumentPrivate::sendGeneratorRequest
(this=0x2474c80) at
/usr/src/debug/kdegraphics-4.3.4/okular/core/document.cpp:837
#8  0x7f52a090ca45 in Okular::Document::qt_metacall (this=0x246ba40,
_c=InvokeMetaMethod, _id=value optimized out, _a=0x7fff75d5cbe0)
at
/usr/src/debug/kdegraphics-4.3.4/x86_64-redhat-linux-gnu/okular/document.moc:145
#9  0x0033b5b5408c in QMetaObject::activate (sender=0x279a050,
from_signal_index=value optimized out, to_signal_index=value optimized out,
argv=0x0) at kernel/qobject.cpp:3112
#10 0x0033b5b5906f in QSingleShotTimer::timerEvent (this=0x279a050) at
kernel/qtimer.cpp:298
#11 0x0033b5b4e08e in QObject::event (this=0x279a050, e=0x7fff75d5d1f0) at
kernel/qobject.cpp:1074
#12 0x0033b7f8f65c in QApplicationPrivate::notify_helper (this=0x237aaa0,
receiver=0x279a050, e=0x7fff75d5d1f0) at kernel/qapplication.cpp:4065
#13 0x0033b7f968ce in QApplication::notify (this=value optimized out,
receiver=0x279a050, e=0x7fff75d5d1f0) at kernel/qapplication.cpp:4030
#14 0x0033ba011a66 in KApplication::notify (this=0x7fff75d5d540,
receiver=0x279a050, event=0x7fff75d5d1f0) at
/usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302
#15 0x0033b5b3ee6c in QCoreApplication::notifyInternal
(this=0x7fff75d5d540, receiver=0x279a050, event=0x7fff75d5d1f0) at
kernel/qcoreapplication.cpp:610
#16 0x0033b5b698d2 in sendEvent (event=value optimized out,
receiver=value optimized out) at kernel/qcoreapplication.h:213
#17 QTimerInfoList::activateTimers (event=value optimized out,
receiver=value optimized out) at kernel/qeventdispatcher_unix.cpp:580
#18 0x0033b5b6729d in timerSourceDispatch (source=value optimized out) at
kernel/qeventdispatcher_glib.cpp:165
#19 0x0033ad23922e in g_main_dispatch (context=value optimized out) at
gmain.c:1960
#20 IA__g_main_context_dispatch (context=value optimized out) at gmain.c:2513
#21 0x0033ad23cc18 in g_main_context_iterate (context=0x237d520,
block=value optimized out, dispatch=value optimized out, self=value
optimized out) at gmain.c:2591
#22 0x0033ad23cd3a in IA__g_main_context_iteration (context=0x237d520,
may_block=1) at gmain.c:2654
#23 0x0033b5b671e6 in QEventDispatcherGlib::processEvents (this=0x23617b0,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327
#24 0x0033b8021ffe in QGuiEventDispatcherGlib::processEvents (this=value
optimized out, flags=value optimized out) at
kernel/qguieventdispatcher_glib.cpp:202
#25 0x0033b5b3d772 in QEventLoop::processEvents (this=value optimized
out, flags=...) at kernel/qeventloop.cpp:149
#26 0x0033b5b3db44 in QEventLoop::exec (this=0x7fff75d5d490, flags=...) at
kernel/qeventloop.cpp:201
#27 0x0033b5b3fcd9 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#28 0x004080e9 in main (argc=value optimized out, argv=value
optimized out) at /usr/src/debug/kdegraphics-4.3.4/okular/shell/main.cpp:81

This bug may be a duplicate of or related to bug 223390

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel


[Okular-devel] [Bug 187174] Okular gives Attempt to use QAction bookmark_action_0 with KXMLGUIFactory! warning

2009-06-06 Thread Tim Landscheidt
https://bugs.kde.org/show_bug.cgi?id=187174





--- Comment #3 from Tim Landscheidt tim tim-landscheidt de  2009-06-06 
21:54:02 ---
Pino said it right: The warnings are unuseful. They hamper work: Whether you
start okular on the command line or (sorry, no vi here :-)) Emacs, they cluster
your screen. I often use okular *  on the shell, and then mv or rm the
shown files. With the unnecessary warnings, this requires periodic C-l to clear
the screen.

Besides that, they also overshadow any real issues that may be hidden beneath.
As a non-developer, I cannot judge whether the warnings indicate a problem, or
a problem soon to emerge, or if they are harmless. That's why I filed the two
bugs. Do I know whether the bookmark_action_0 warning reflects the missing
xmlns in Konqueror's bookmarks.xml? No, and I do not want to ask every time I
run okular.

IMVHO a program should never output warnings in normal operations, so that
the user does not become accustomed to them and misses a critical one. Or the
developer when testing the program.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel