Bug 49866 - Allow constraints to be edited when >1 component is selected
Summary: Allow constraints to be edited when >1 component is selected
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: VE (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: VE Bugzilla inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 49871 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-01-12 14:09 EST by Joe Winchester CLA
Modified: 2011-06-13 11:38 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Winchester CLA 2004-01-12 14:09:35 EST
Collete ( who is writing a JVE book asked for this ) and this is her note and 
my reply

>- When I select multiple buttons, constraints isn't one of the 
>properties that shows up in the Properties view.   I remember when I 
>was writing the draft for this chapter I was surprised by that and 
>probably should have reported it earlier.  In VAJ, constraints was 
>one of the properties that you could set for multi-selected elements.

We could include it but we'd have to only allow it to appear if the 
containers' layout managers of all of the components parents were of the same 
type.  For some layout managers such as BorderLayout there are more problems 
because for this we show a list the list of available regions + the region 
currently occupied by the component.  If the two components were in different 
containers that were both in BorderLayout creating the list would be hard to 
do.  Bottom line, we excluded it because it requires some tricky code to get 
right and we just ran out of runway.
Comment 1 Peter Walker CLA 2004-02-20 12:56:47 EST
*** Bug 49871 has been marked as a duplicate of this bug. ***
Comment 2 Peter Walker CLA 2004-02-23 17:21:34 EST
changed to "future"... not sure we'd have time for this in v1.0.0