Bug 486419 - File -> Print interface glitched, unnavigable
Summary: File -> Print interface glitched, unnavigable
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 10
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-23 13:05 EST by Josh Cicchini CLA
Modified: 2022-12-13 06:08 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Cicchini CLA 2016-01-23 13:05:56 EST
When I attempt to print code from the Eclipse environment, the File -> Print dialogue box that arises is too small to contain all of its options. It allows neither resizing nor scrolling along its axes. I must print my code in landscape mode for class, and of course would prefer for it to print double-sided and in black & white; none of these options are currently reachable from my version of Eclipse, and the default settings override any adjustments I attempt to make by right-clicking on my printer in the containing list.

-- Configuration Details --
Product: Eclipse 4.5.1.20150917-1200 (org.eclipse.epp.package.java.product)
Installed Features:
 org.eclipse.jdt 3.11.1.v20150904-0015
Comment 1 Eclipse Genie CLA 2020-10-02 19:42:00 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2022-12-13 06:08:54 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.