[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim resolved JBIDE-7862. ------------------------------------- Resolution: Done layouting the combo's parent as soon as the cloud name gets edited -> combo resizes to the space needed to show the whole name committed to TRUNK (CR1) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-7862: ------------------------------------ Fix Version/s: 3.2.1 (was: 3.2.x) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-7862: ----------------------------------------- bug does not occur in trunk. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-7862 at 3/14/11 10:45 AM: ------------------------------------------------------------------- bug does only occur if you have at least 2 clouds. It does not happen if you have only 1 cloud. was (Author: adietish): bug does not occur in trunk. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-7862: ------------------------------------ Steps to Reproduce: 1) make sure you have at least 2 clouds available. You need a cloud with a long label and one with a short label (ex. "aaaaaaaaaaaaaaaaaaaaaaa" and "b") 2) go to cloud view, select the cloud with the short label and choose "Edit Connection" from the context menu 4) in the wizard: change the name of the cloud to a name that's much longer than the current one 5) hit finish 6) The combo in the image view was resized to the space that is needed to display the full label 7) now rename it back to a very short name 8) check the size of the combo in the image view Result: The combo did not shrink again, it still uses the full space that was used to display the long label Expected result: The combo resized to the space needed to show the whole name was: 1) make sure you have at least 2 clouds available 2) go to image view, select the could you will rename in the next step 3) go to cloud view, select your cloud and choose "Edit Connection" from the context menu 4) in the wizard: change the name of the cloud to a name that's much longer than the current one 5) hit finish 6) look at the combo in the image view Result: The combo did not resize, it does not show the whole name, the name gets cut Expected result: The combo resized to the space needed to show the whole name -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-7862: ----------------------------------------- committed to TRUNK, patch for maintenance attached so that it can be reviewed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-7862: ------------------------------------ Steps to Reproduce: 1) make sure you have at least 2 clouds available. You need a cloud with a long label and one with a short label (ex. "aaaaaaaaaaaaaaaaaaaaaaa" and "b") 2) go to cloud view, select the cloud with the short label and choose "Edit Connection" from the context menu 3) in the wizard: change the name of the cloud to a name that's much longer than name of the other cloud 4) hit finish 5) The combo in the image view was resized to the space that is needed to display the full label 6) now rename it back to a very short name (that is shorter than the other, very long cloud name) 7) check the size of the combo in the image view Result: The combo did not shrink again, it still uses the full space that was used to display the long label Expected result: The combo resized to the space needed to show the whole name was: 1) make sure you have at least 2 clouds available. You need a cloud with a long label and one with a short label (ex. "aaaaaaaaaaaaaaaaaaaaaaa" and "b") 2) go to cloud view, select the cloud with the short label and choose "Edit Connection" from the context menu 4) in the wizard: change the name of the cloud to a name that's much longer than name of the other cloud 5) hit finish 6) The combo in the image view was resized to the space that is needed to display the full label 7) now rename it back to a very short name 8) check the size of the combo in the image view Result: The combo did not shrink again, it still uses the full space that was used to display the long label Expected result: The combo resized to the space needed to show the whole name -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-7862: ----------------------------------------- The cause of JBIDE-8590 was not introduced with this bug here. I'll therefore commit this patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Libor Zoubek commented on JBIDE-7862: ------------------------------------- I was not able to rename Cloud Connection because of JBIDE-8847. But I created 2 connections, 'a' and 'aaaaaaaaaaaa'. Combos in Instance/Image views do not resize when I select the other cloud. (v0.0.1.v20110503-1752-H179-M1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-7862: --------------------------------------- Fix Version/s: 3.3.0.M2 (was: 3.3.0.M1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-7862: ------------------------------------ Component/s: (was: deltacloud) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-7862: ------------------------------------ Priority: Minor (was: Major) Labels: (was: triage_3.2.1) Affects Version/s: 3.3.0.M1 3.2.1.M1 Component/s: deltacloud -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-7862: ----------------------------------------- you are right in the sense that the issue unfortunately is still present -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7862?page=com.atlassian.jira.plugin... ] Andre Dietisheim resolved JBIDE-7862. ------------------------------------- Resolution: Out of Date we're not developing Deltacloud any longer. See JBIDE-12458 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira