bugGNU Octave - Bugs: bug #52749, fltk to qt merge


bug #52749: fltk to qt merge

Submitter:  Michael Godfrey <godfrey>
Submitted:  Wed 27 Dec 2017 02:43:57 PM UTC
Category:  Plotting Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Incorrect Result
Status:  None Assigned to:  None
Originator Name:  Michael Godfrey Open/Closed:  * Open
Release:  * dev Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup

Wed 27 Dec 2017 02:43:57 PM UTC, original submission:  

It is planned to transition fltk to qt. A major problem in doing
this is that, for the same input, the resulting PDF bounding
boxes differ by a large enough amount that their use, for example,
in LaTeX \includegraphics() requires substantial recoding of the
parameters. It would be very useful if both plotting systems
produced the same plot, including Bounding Box values when
processing the same input. Here is an example of the surrent
state with and without -tight:

***********qt vs fltk Bounding Box results w/wo pdfcrop
                          qt                   fltk  
plot_diff.pdf            17 179 595 702     49 198 536 589
plot_diff-crop.pdf       0 0 578 523        0 0 487 391
plot_orig_norm.pdf       17 179 595 702     64 236 551 564
plot_orig_norm-crop.pdf  0 0 578 523        0 0 487 328

With -tight set:
plot_diff.pdf            17 179 595 702     52 200 551 600
plot_diff-crop.pdf       0 0 578 523        0 0 499 400

It would also be helpful to implement an option to run
pdfcrop before writing the output. -tight appears not to
do the same as pdfcrop. pdfcrop makes the plots easier to

Michael Godfrey <godfrey>
Group Member


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by godfrey (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.


    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-b921.
    Corresponding source code