September 2019 - jbosstools-issues

[JBoss JIRA] (ERT-756) ToolItem traversal does not fire deactivate event. [EBZ#341117]

by Friendly Jira Robot (Jira)

[ https://issues.jboss.org/browse/ERT-756?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-756. ------------------------------------- Resolution: Done > ToolItem traversal does not fire deactivate event. [EBZ#341117] > --------------------------------------------------------------- > > Key: ERT-756 > URL: https://issues.jboss.org/browse/ERT-756 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Priority: Major > Labels: 4.14_M1, SWT, bzira > > Build Identifier: M20100909-0800 > When using tab to traverse, a ToolItem in a ToolBar does not send deactivate event to existing active control when it receives focus. > This is for Linux, on Windows a deactivate event is fired. > Reproducible: Always > Steps to Reproduce: > 1.Run the attached snippet in Linux (gtk). > 2.Tab through the the two Text controls and the ToolItem button > 3.Note that Text 2 does not receive a deactivate event until Text 1 is activated > 4. On Windows Text 2 gets a deactivate event when the toolbar button receives focus. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-755) Device#getDPI method can return incorrect values [EBZ#545953]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-755?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-755: --------------------------------- Sprint: devex #172 Sep 2019 Assignee: Eric Williams > Device#getDPI method can return incorrect values [EBZ#545953] > ------------------------------------------------------------- > > Key: ERT-755 > URL: https://issues.jboss.org/browse/ERT-755 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: 4.14_M1, SWT, bzira > > Since the fix for Bug 535064 there is an issue with Device#getDPI method that can under some unclear conditions return an incorrect DPI. Since my comment in the original bug went unnoticed I'm creating a new bug to raise this issue. > Here's my comment in the original bug: > I'm noticing a strange behavior of Device#getScreenDPI on my system (Ubuntu 18.04 with latest updates, and GTK version 3.22.30). The returned DPI value is {102, 102} instead of {96,96} as it should be. I've tried to debug the issue and here are the values used for DPI calculation: > widthMM=480,scaleFactor=1,monitorGeometry={0, 0, 1920, 1080} > This gives 254*1920/(480*10.0) = 101.6, value then rounded to 102. > I've tried to reproduce this issue with VirtualBox with a clean 18.04 install but couldn't. Although it's the same system, returned widthMM is different: > widthMM=503,scaleFactor=1,monitorGeometry={0, 0, 1920, 988} > Which gives 254*1920/(503*10.0) = 96.0, which is correct. > Is this a bug? Running $ xrandr --query gives > Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 > VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm > So the 480mm value is there, but I am not sure what this means. The result is that Eclipse 4.9 and onward return and incorrect DPI value on my system. > "xrdb -query | grep dpi" gives the correct DPI as follows: > Xft.dpi: 96 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-26817 at 9/11/19 11:34 AM: -------------------------------------------------------------------- removed the 3rd link: !image-2019-09-11-17-34-37-623.png! was (Author: adietish): removed the 3rd link: !screenshot-1.png|thumbnail! > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26817: ------------------------------------- Attachment: (was: screenshot-1.png) > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-26817 at 9/11/19 11:33 AM: -------------------------------------------------------------------- removed the 3rd link: !screenshot-1.png|thumbnail! was (Author: adietish): removed the 3rd link: !screenshot-1.png! > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, screenshot-1.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26817: ------------------------------------- Attachment: screenshot-1.png > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, screenshot-1.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26817: ------------------------------------------ removed the 3rd link: !screenshot-1.png! > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, screenshot-1.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] André Dietisheim reassigned JBIDE-26817: ---------------------------------------- Assignee: André Dietisheim > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-755) Device#getDPI method can return incorrect values [EBZ#545953]

by Friendly Jira Robot (Jira)

Friendly Jira Robot created ERT-755: --------------------------------------- Summary: Device#getDPI method can return incorrect values [EBZ#545953] Key: ERT-755 URL: https://issues.jboss.org/browse/ERT-755 Project: Eclipse Release Train Issue Type: Task Components: Platform Reporter: Friendly Jira Robot Since the fix for Bug 535064 there is an issue with Device#getDPI method that can under some unclear conditions return an incorrect DPI. Since my comment in the original bug went unnoticed I'm creating a new bug to raise this issue. Here's my comment in the original bug: I'm noticing a strange behavior of Device#getScreenDPI on my system (Ubuntu 18.04 with latest updates, and GTK version 3.22.30). The returned DPI value is {102, 102} instead of {96,96} as it should be. I've tried to debug the issue and here are the values used for DPI calculation: widthMM=480,scaleFactor=1,monitorGeometry={0, 0, 1920, 1080} This gives 254*1920/(480*10.0) = 101.6, value then rounded to 102. I've tried to reproduce this issue with VirtualBox with a clean 18.04 install but couldn't. Although it's the same system, returned widthMM is different: widthMM=503,scaleFactor=1,monitorGeometry={0, 0, 1920, 988} Which gives 254*1920/(503*10.0) = 96.0, which is correct. Is this a bug? Running $ xrandr --query gives Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm So the 480mm value is there, but I am not sure what this means. The result is that Eclipse 4.9 and onward return and incorrect DPI value on my system. "xrdb -query | grep dpi" gives the correct DPI as follows: Xft.dpi: 96 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-755) Device#getDPI method can return incorrect values [EBZ#545953]

by Friendly Jira Robot (Jira)

[ https://issues.jboss.org/browse/ERT-755?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-755. ------------------------------------- Resolution: Done > Device#getDPI method can return incorrect values [EBZ#545953] > ------------------------------------------------------------- > > Key: ERT-755 > URL: https://issues.jboss.org/browse/ERT-755 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Priority: Major > Labels: 4.14_M1, SWT, bzira > > Since the fix for Bug 535064 there is an issue with Device#getDPI method that can under some unclear conditions return an incorrect DPI. Since my comment in the original bug went unnoticed I'm creating a new bug to raise this issue. > Here's my comment in the original bug: > I'm noticing a strange behavior of Device#getScreenDPI on my system (Ubuntu 18.04 with latest updates, and GTK version 3.22.30). The returned DPI value is {102, 102} instead of {96,96} as it should be. I've tried to debug the issue and here are the values used for DPI calculation: > widthMM=480,scaleFactor=1,monitorGeometry={0, 0, 1920, 1080} > This gives 254*1920/(480*10.0) = 101.6, value then rounded to 102. > I've tried to reproduce this issue with VirtualBox with a clean 18.04 install but couldn't. Although it's the same system, returned widthMM is different: > widthMM=503,scaleFactor=1,monitorGeometry={0, 0, 1920, 988} > Which gives 254*1920/(503*10.0) = 96.0, which is correct. > Is this a bug? Running $ xrandr --query gives > Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 > VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm > So the 480mm value is there, but I am not sure what this means. The result is that Eclipse 4.9 and onward return and incorrect DPI value on my system. > "xrdb -query | grep dpi" gives the correct DPI as follows: > Xft.dpi: 96 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2019