[
https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19453:
-------------------------------------
Unfortunately we don't control the minimum width of the column. Theoretically we
could make it wider by simply adding a very large widget and forcing it wider, but, then
it'd become inconvenient for the user to properly fit both columns on the screen
wtihout a scrollbar, so that's not really a good solution.
I've made a commit that lowers the minimum size of the server-home text field from 200
down to 150, and i've put the minimum width of the base-dir field down to 100. The
fields will still expand to fill whatever space is left after the browse button and label
are placed, if there is any extra... but it basically means that those text fields are
'able' to be squished, so long as they don't shrink below 150 and 100 pixels
respectively.
So if for some reason your font size throughout your entire workspace is huge, and the
labels on the left side take up the entire widget, then you'll still be
shit-out-of-luck and be unable to see the browse button. Unfortunately, this is more a
problem with the scrollbars than anything.
See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=464223 for more information.
Remote host information does not fit in the server editor
---------------------------------------------------------
Key: JBIDE-19453
URL:
https://issues.jboss.org/browse/JBIDE-19453
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.3.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.3.0.Beta1
Attachments: remote-runtime-does-not-fit.png, server-editor-2.png,
server-editor-linux.png
Today I noticed this. When I set up a remote server and then open it in the Server
editor, the part under Server Behavior where it shows the remote host configuration (e.g.
Remote Server Home) does not fix - it needs more space to the right, but it's hidden
and there is no way to scroll to view it.
!remote-runtime-does-not-fit.png!
The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want
to clone this for 4.3.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)