okular

3558 Commits

9 Branches

332 Tags

50 MiB

Tag: Branch: Tree: 1be1b40dd0

Commit Graph

Author	SHA1	Message	Date
Pino Toscano	964424d62f	stop gracefully the font extraction thread when closing a document or the properties dialog; make the thread deleting itself when finished svn path=/trunk/KDE/kdegraphics/okular/; revision=685437	19 years ago
Pino Toscano	e5037f45b1	Refator a bit the way Document and the generators use to read the font information from a document. Instead of having a synchronous function that extracts all the information at once, use a function to read the fonts of a single page. This way, we can get all the result step by step (aka page by page), and possibly in an asynchronous way. The resuls of the font "scanning" are sent via signals, as well the end of the work. So, instead of block waiting for the results of all the document at once, the Fonts tab in the properties dialog can have a progress bar with the progress, and the results (the fonts) that are added incrementally to the list. Only two minor things are left: - the process is always asynchronous at the moment, as the only generator that can provide this kind of information is the Poppler one (safe) - there is no check for duplicate fonts But they should be easy to solve. svn path=/trunk/KDE/kdegraphics/okular/; revision=685002	19 years ago
Pino Toscano	166ba5b87a	move the Generator::Private to a GeneratorPrivate, and move the implementations of the provate threads to a cpp svn path=/trunk/KDE/kdegraphics/okular/; revision=656221	19 years ago

Author

SHA1

Message

Date

Pino Toscano

964424d62f

stop gracefully the font extraction thread when closing a document or the properties dialog; make the thread deleting itself when finished

svn path=/trunk/KDE/kdegraphics/okular/; revision=685437

19 years ago

Pino Toscano

e5037f45b1

Refator a bit the way Document and the generators use to read the font information from a document.

Instead of having a synchronous function that extracts all the information at once, use a function to read the fonts of a single page.
This way, we can get all the result step by step (aka page by page), and possibly in an asynchronous way.
The resuls of the font "scanning" are sent via signals, as well the end of the work.
So, instead of block waiting for the results of all the document at once, the Fonts tab in the properties dialog can have a progress bar with the progress, and the results (the fonts) that are added incrementally to the list.

Only two minor things are left:
- the process is always asynchronous at the moment, as the only generator that can provide this kind of information is the Poppler one (safe)
- there is no check for duplicate fonts
But they should be easy to solve.

svn path=/trunk/KDE/kdegraphics/okular/; revision=685002

19 years ago

Pino Toscano

166ba5b87a

move the Generator::Private to a GeneratorPrivate, and move the implementations of the provate threads to a cpp

svn path=/trunk/KDE/kdegraphics/okular/; revision=656221

19 years ago

3 Commits (1be1b40dd08a66dd00a6d15f27a3dcfa65fadd30)