https://proj.goldencode.com/https://proj.goldencode.com/favicon.ico2015-11-16T19:00:03ZGolden Code RedmineUser Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=349592015-11-16T19:00:03ZGreg Shah
<ul></ul><p>Using <code>./menu/simple_sm.p</code> in the Swing client, Vadim reported:</p>
<p>1. After I press on some menu-item in the on of sub-menus of a menubar, root sub-menu in menubar stays "mouse-entered" after body is hidden.</p>
<p>2. The same scenario: sub-menu child is still displayed as focused after it's parent's body is hidden.</p>
<p>3. At the start of the test the warning "Run-time error ... (3269)" is shown and no menubar is displayed in PROGRESS until the user will press any key, but in P2J empty menubar rectangle is drawn.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=350322015-11-18T22:36:04ZVadim Gindinvig@goldencode.com
<ul><li><strong>File</strong> <i>fonts_compare.png</i> added</li><li><strong>File</strong> <i>hidden_menu_elems.png</i> added</li></ul>Here are the images
<ol>
<li>Fonts compare <img src="fonts_compare.png" alt="" /> of PROGRESS, P2J SWING, P2J WEB. There is an other font for WEB.</li>
<li>MENU bug of showing hidden menu items <img src="hidden_menu_elems.png" alt="" /></li>
</ol> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=350342015-11-18T22:41:33ZVadim Gindinvig@goldencode.com
<ul><li><strong>File</strong> deleted (<del><i>hidden_menu_elems.png</i></del>)</li></ul> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=350352015-11-18T22:41:38ZVadim Gindinvig@goldencode.com
<ul><li><strong>File</strong> deleted (<del><i>fonts_compare.png</i></del>)</li></ul> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=350362015-11-18T22:46:00ZVadim Gindinvig@goldencode.com
<ul></ul><p>Greg Shah wrote:</p>
<blockquote>
<p>3. At the start of the test the warning "Run-time error ... (3269)" is shown and no menubar is displayed in PROGRESS until the user will press any key, but in P2J empty menubar rectangle is drawn.</p>
</blockquote>
<p>The place where that background is drawn is the same as for <code>popup_ext.p</code>: <code>BorderedPanelGuiImpl.draw()</code>. I've checked that at the drawing time menubar is hidden and it does not post <code>PaintEvent's</code>. So there are some other widget posted clipping rectangle, that intersects menubar area.. Once again if the widget is responsible to draw it's background itself, why it is needed to draw some rectangles in <code>BorderedPanelGuiImpl.draw()</code>?</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=350502015-11-19T15:03:43ZVadim Gindinvig@goldencode.com
<ul><li><strong>File</strong> <a href="/attachments/download/4367/menubar_background.png">menubar_background.png</a> added</li></ul><p>I'm trying to understand how the "menubar's" rectangle get into screen clippings, that are drawn in <code>BorderedPanelGuiImpl.draw()</code>. I recall that at that moment MENUBAR itself is hidden and does not post PaintEvent, so there is some other widget, that posts a PaintEvent with similar rectangle. I.e. right after start, when the warning "Run-time error in WAIT-FOR at line ..." is shown an a messagebar menubar is still hidden but it's background rectangle is drawn:<br /><img src="https://proj.goldencode.com/attachments/download/4367/menubar_background.png" alt="" /><br />I've added logging of processed PaintEvent native rectangle and source to <code>TitledWindow.processEvent()</code> method (line 163). Here is what I've got (top, left, bottom, right):<br /><pre>
PE: [0, 0, 41, 2147483647], source=MessageAreaGuiImpl
PE: [0, 0, 29, 399], source=MessageAreaGuiImpl
PE: [0, 0, 41, 399], source=BorderedPanelGuiImpl
PE: [0, 0, 29, 399], source=BorderedPanelGuiImpl
PE: [0, 0, 2147483647, 2147483647], source=WindowTitleBar
PE: [0, 0, 2147483647, 399], source=WindowTitleBar
PE: [0, 0, 2147483645, 2147483645], source=WindowTitleBar$WindowIcon
PE: [1, 2, 2147483646, 2147483647], source=WindowTitleBar$WindowIcon
PE: [0, 0, 2147483647, 399], source=WindowTitleBar$WindowTitle
PE: [0, 0, 17, 399], source=WindowTitleBar$WindowTitle
PE: [0, 0, 18, 399], source=WindowTitleBar
PE: [0, 0, 13, 15], source=CaptionButton
PE: [2, 382, 15, 397], source=CaptionButton
PE: [0, 0, 13, 15], source=CaptionButton
PE: [2, 364, 15, 379], source=CaptionButton
PE: [0, 0, 13, 15], source=CaptionButton
PE: [2, 348, 15, 363], source=CaptionButton
PE: [1, 19, 18, 399], source=WindowTitleBar$WindowTitle
PE: [1, 19, 18, 345], source=WindowTitleBar$WindowTitle
PE: [0, 0, 541, 408], source=WindowGuiImpl
PE: [23, 4, 484, 403], source=WindowWorkSpace
PE: [23, 4, 484, 403], source=BorderedPanelGuiImpl
PE: [0, 0, 540, 407], source=BorderedPanelGuiImpl
PE: [4, 4, 22, 403], source=WindowTitleBar
PE: [485, 4, 514, 403], source=MessageAreaGuiImpl
PE: [515, 4, 536, 403], source=StatusLineGuiImpl
PE: [485, 4, 514, 403], source=MessageAreaGuiImpl
PE: [485, 4, 514, 403], source=BorderedPanelGuiImpl
PE: [4, 4, 22, 403], source=WindowTitleBar
PE: [5, 6, 20, 21], source=WindowTitleBar$WindowIcon
PE: [5, 23, 22, 349], source=WindowTitleBar$WindowTitle
PE: [6, 386, 19, 401], source=CaptionButton
PE: [6, 368, 19, 383], source=CaptionButton
PE: [6, 352, 19, 367], source=CaptionButton
PE: [23, 4, 484, 403], source=WindowWorkSpace
PE: [23, 4, 484, 403], source=BorderedPanelGuiImpl
PE: [0, 0, 541, 408], source=WindowGuiImpl
PE: [0, 0, 564, 408], source=WindowGuiImpl
PE: [0, 0, 540, 407], source=BorderedPanelGuiImpl
PE: [0, 0, 563, 407], source=BorderedPanelGuiImpl
PE: [508, 4, 537, 403], source=MessageAreaGuiImpl
PE: [538, 4, 559, 403], source=StatusLineGuiImpl
PE: [508, 4, 537, 403], source=MessageAreaGuiImpl
PE: [538, 4, 559, 403], source=StatusLineGuiImpl
PE: [4, 4, 22, 403], source=WindowTitleBar
PE: [0, 0, 564, 408], source=WindowGuiImpl
PE: [4, 4, 22, 403], source=WindowTitleBar
PE: [4, 4, 22, 403], source=WindowTitleBar
PE: [0, 0, 564, 408], source=WindowGuiImpl
PE: [4, 4, 22, 403], source=WindowTitleBar
PE: [4, 4, 22, 403], source=WindowTitleBar
</pre><br />Menubar rectangle starts at top=23px approximately, so I don't see here exact rectangle, but here are some intersecting rectangles and some rectangles seems strange:<br />PE: [0, 0, 41, 2147483647], source=MessageAreaGuiImpl<br />PE: [0, 0, 29, 399], source=MessageAreaGuiImpl<br />PE: [0, 0, 41, 399], source=BorderedPanelGuiImpl<br />PE: [0, 0, 29, 399], source=BorderedPanelGuiImpl</p>
<p>Message area resides in the bottom of the window. It looks that rectangles are incorrect. What do you think?</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=350962015-11-20T14:44:36ZConstantin Asofiei
<ul></ul><p>Vadim, in which branch are you working this?</p>
<p>Also, please remind me, have you managed to address the sub-menu body repaint I mentioned some time ago?</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=350992015-11-20T14:57:41ZConstantin Asofiei
<ul></ul><p>Vadim, I think I know why you are seeing the top light-gray space. Menu-bar gets attached to window (and window is relayout) BEFORE making it visible in GUI. At the time this code is called and warning is shown:<br /><pre>
if(!hasEnabledFrame())
{
warnNoEnabledFrames(wnd);
}
wnd.getMenubar().setVisible(true);
</pre><br />the window is already layout as if a menu-bar is added. Only later the menu-bar is being drawn (as it is being made visible).</p>
<p>Can you check what happens if the menubar gets set to not-visible via a trigger? Is the window workspace resized and the menubar hidden? If so, the window needs to layout and use the menubar only if the menubar is visible; and if the menubar's visibility gets changed, the window needs to be relayout.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=351242015-11-22T12:54:09ZVadim Gindinvig@goldencode.com
<ul></ul><p>Constantin Asofiei wrote:</p>
<blockquote>
<p>Vadim, in which branch are you working this?</p>
</blockquote>
<p>bracnh 2677a, revno 11067.</p>
<blockquote>
<p>Also, please remind me, have you managed to address the sub-menu body repaint I mentioned some time ago?</p>
</blockquote>
<p>You probably mean the note 22 in the task <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: fix GUI menu drawing problems in menu/simple_sm.p (Closed)" href="https://proj.goldencode.com/issues/2736">#2736</a>. Yes, I'd tried that, but unsuccessfully: sub-menu's aren't drawn. You can see details about it in that task <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: fix GUI menu drawing problems in menu/simple_sm.p (Closed)" href="https://proj.goldencode.com/issues/2736">#2736</a> the latest post (popup_ext.p). More over I think there is another reason in that task.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=351302015-11-23T08:09:33ZVadim Gindinvig@goldencode.com
<ul><li><strong>File</strong> <a href="/attachments/download/4382/1123.diff">1123.diff</a><a href="/attachments/4382/1123.diff"><img src="/images/magnifier.png" alt="Magnifier" /></a> added</li></ul><p>Constantin. You were absolutely right about the reason. I've added <code>isVisible</code> check for MENUBAR to <code>WindowLayout</code> and fixed dynamic attach/detach case for GUI and CHUI. By the way, MENUBAR can be shown only by assigning to <code>window:menubar</code> attribute. <code>visible</code> attribute is not setable for menu. I've added corresponding error. I've also fixed CHUI layout for dynamic case.</p>
<p>Attached diff contains my current changes.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=351842015-11-24T12:18:35ZGreg Shah
<ul></ul><p>Code Review 1123.diff</p>
<p>1. I don't think it is a good idea to require that the status line and message line implementations must calculate whether or not the menubar exists to determine their location. The containing window should have a method that reports the correct location for each one. Actually, I don't understand why the location changes when the menubar is present. The screen dimensions should not be different and the status/message lines are at the same location no matter if the menubar exists or not.</p>
<p>2. You have mixed in your other changes (right mouse issues and toggle-box issues). I don't think the right mouse changes are safe, so these cannot be included.</p>
<p>Constantin: please review.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=351852015-11-24T12:29:45ZConstantin Asofiei
<ul></ul>Beside what Greg noted:
<ul>
<li>in ChUI, message area, status area, frames (and menubar) are all attached to the same parent (in other terms, they are all siblings). So the change in <code>WindowChuiImpl</code> doesn't look correct, as the <code>contentPane</code> will contain everything, not just frames</li>
<li>in ChUI, we don't have (yet) a container separation between frames and message area/status area/menubar. This requires more testing, to determine if a frame can overlay the last 3 rows (message + status) in the screen. If it can not, then ChUI needs a "workspace" equivalent, as GUI has, to separate the frames.</li>
<li>as Greg mentioned, the location/height of the status/message area is constant. Only the height available for frame placement is reduced when the menubar is attached in ChUI.</li>
</ul> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=351932015-11-24T13:54:54ZVadim Gindinvig@goldencode.com
<ul></ul><p>So should I fix it now or postpone that?</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=351942015-11-24T13:58:55ZGreg Shah
<ul></ul><p>1. Separate out the changes for toggle-box/right mouse issues.</p>
<p>2. Fix the rest based on the code reviews.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=352342015-11-24T17:18:36ZVadim Gindinvig@goldencode.com
<ul><li><strong>File</strong> <a href="/attachments/download/4392/1124.diff">1124.diff</a><a href="/attachments/4392/1124.diff"><img src="/images/magnifier.png" alt="Magnifier" /></a> added</li></ul><p>All 3 points in this task are fixed. See attached diff. I've separated issues from other tasks.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=352432015-11-24T19:10:05ZGreg Shah
<ul><li><strong>Assignee</strong> set to <i>Vadim Gindin</i></li></ul><p>Code Review 1124.diff</p>
<p>My only question is regarding the addition of the <code>Window.currentFocus()</code> code. This seems wrong. If I am understanding it properly, as long as there is ever a popup menu in the widget list for a window, only that popup menu will ever be focusable.</p>
<p>Please explain.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=352482015-11-24T19:35:36ZVadim Gindinvig@goldencode.com
<ul></ul><p>Greg Shah wrote:</p>
<blockquote>
<p>Code Review 1124.diff</p>
<p>My only question is regarding the addition of the <code>Window.currentFocus()</code> code. This seems wrong. If I am understanding it properly, as long as there is ever a popup menu in the widget list for a window, only that popup menu will ever be focusable.</p>
<p>Please explain.</p>
</blockquote>
<p>It is just a such behaviour: while popup menu is opened, tab order isn't working and navigation is available only inside menu using arrows. It probably relates to <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: implement and/or fix the default popup menus for all widgets (Closed)" href="https://proj.goldencode.com/issues/2849">#2849</a> task for ignoring right mouse button: when we do not set a focus to the button, on which we clicked using right mouse button, we will not be able to find current focused item in menu.. I can also move it at this point from the current update to <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: implement and/or fix the default popup menus for all widgets (Closed)" href="https://proj.goldencode.com/issues/2849">#2849</a> changes set.</p>
<p>P.S.<br />Another bug for CHUI: Focused element of MENUBAR must be drawn as <code>Color.MESSAGES</code>, but it is drawn as <code>Color.NORMAL</code>. I recall that <code>Color.MESSAGES=Color.NORMAL.withReverse()</code>.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=352512015-11-24T19:42:36ZGreg Shah
<ul></ul><blockquote>
<p>It is just a such behaviour: while popup menu is opened, tab order isn't working and navigation is available only inside menu using arrows. It probably relates to <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: implement and/or fix the default popup menus for all widgets (Closed)" href="https://proj.goldencode.com/issues/2849">#2849</a> task for ignoring right mouse button: when we do not set a focus to the button, on which we clicked using right mouse button, we will not be able to find current focused item in menu.</p>
</blockquote>
<p>I have 2 concerns:</p>
<p>1. When the popup menu is not open, the <code>currentFocus()</code> will be broken.</p>
<p>2. I don't think that the popup menu should be treated as a widget contained by the window. It is more like the combo-box drop-down. It temporarily appears and when it is open it owns the interaction with the user.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=352572015-11-24T20:01:35ZVadim Gindinvig@goldencode.com
<ul></ul><p>Greg Shah wrote:</p>
<blockquote><blockquote>
<p>It is just a such behaviour: while popup menu is opened, tab order isn't working and navigation is available only inside menu using arrows. It probably relates to <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: implement and/or fix the default popup menus for all widgets (Closed)" href="https://proj.goldencode.com/issues/2849">#2849</a> task for ignoring right mouse button: when we do not set a focus to the button, on which we clicked using right mouse button, we will not be able to find current focused item in menu.</p>
</blockquote>
<p>I have 2 concerns:</p>
<p>1. When the popup menu is not open, the <code>currentFocus()</code> will be broken.</p>
</blockquote>
<p>In that case <code>w.isVisible()==false</code> and therefore super.currentFocus() will be called. Isn't it?</p>
<blockquote>
<p>2. I don't think that the popup menu should be treated as a widget contained by the window. It is more like the combo-box drop-down. It temporarily appears and when it is open it owns the interaction with the user.</p>
</blockquote>
<p>The difference is in the fact, than <code>Menu</code> holds it's own widgets tree of menu widgets, that are also focusable.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=352632015-11-24T21:40:23ZGreg Shah
<ul></ul><blockquote>
<p>In that case w.isVisible()==false and therefore super.currentFocus() will be called. Isn't it?</p>
</blockquote>
<p>Yes, you're probably right.</p>
<blockquote><blockquote>
<p>2. I don't think that the popup menu should be treated as a widget contained by the window. It is more like the combo-box drop-down. It temporarily appears and when it is open it owns the interaction with the user.</p>
</blockquote>
<p>The difference is in the fact, than Menu holds it's own widgets tree of menu widgets, that are also focusable.</p>
</blockquote>
<p>The key point here is that we don't want to spread widget-specific behavior (e.g. for menus) into other non-related classes (e.g. window). It makes it hard to understand how menus work. It makes it hard to find all the behavior related to menus. It makes those classes very dependent upon one another, which makes things fragile and more likely to break.</p>
<p>Constantin/Hynek: thoughts?</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=352732015-11-25T08:18:18ZHynek Cihlar
<ul></ul><p>Greg Shah wrote:</p>
<blockquote><blockquote>
<p>In that case w.isVisible()==false and therefore super.currentFocus() will be called. Isn't it?</p>
</blockquote>
<p>Yes, you're probably right.</p>
<blockquote><blockquote>
<p>2. I don't think that the popup menu should be treated as a widget contained by the window. It is more like the combo-box drop-down. It temporarily appears and when it is open it owns the interaction with the user.</p>
</blockquote>
<p>The difference is in the fact, than Menu holds it's own widgets tree of menu widgets, that are also focusable.</p>
</blockquote>
<p>The key point here is that we don't want to spread widget-specific behavior (e.g. for menus) into other non-related classes (e.g. window). It makes it hard to understand how menus work. It makes it hard to find all the behavior related to menus. It makes those classes very dependent upon one another, which makes things fragile and more likely to break.</p>
<p>Constantin/Hynek: thoughts?</p>
</blockquote>
<p>I think Greg is right. Menu should be rendered in its own top-level window, otherwise we will have the same issue as with combo drop-down - the menu won't be able to draw outside of its logical parent window.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=353152015-11-25T14:50:51ZVadim Gindinvig@goldencode.com
<ul></ul><p>OK, I understand.</p>
<p>I have collected changes for 2-3 tasks and I would want to commit some of them, that are approved. All issues in this task are approved. Can I commit them (the latest diff) excluding <code>Menu</code> change?</p>
<p>Talking about ability to draw menu with opened sub-menus exceeding window sizes, is there a separate task for this already? Is it solved for combo-box or other widget, that has the same issue?</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=353252015-11-25T15:23:56ZHynek Cihlar
<ul></ul><p>Vadim Gindin wrote:</p>
<blockquote>
<p>Talking about ability to draw menu with opened sub-menus exceeding window sizes, is there a separate task for this already? Is it solved for combo-box or other widget, that has the same issue?</p>
</blockquote>
<p>There is an issue for combo-box drop-down, see <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: GUI combo-box drop-down needs to be able to draw outside of it's containing top-level window (Closed)" href="https://proj.goldencode.com/issues/2837">#2837</a>.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=353382015-11-25T16:52:06ZVadim Gindinvig@goldencode.com
<ul><li><strong>File</strong> <a href="/attachments/download/4407/2850_2511.diff">2850_2511.diff</a><a href="/attachments/4407/2850_2511.diff"><img src="/images/magnifier.png" alt="Magnifier" /></a> added</li></ul><p>Here is the latest diff on merged branch.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=353862015-11-26T08:39:33ZVadim Gindinvig@goldencode.com
<ul></ul><p>Yesterday, I've fixed CHUI bug with menubar:</p>
<blockquote>
<p>Another bug for CHUI: Focused element of MENUBAR must be drawn as Color.MESSAGES, but it is drawn as Color.NORMAL. I recall that Color.MESSAGES=Color.NORMAL.withReverse().</p>
</blockquote>
<p>So once again can I commit the last change (diff in the note <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: implement preprocessor variations generation (New)" href="https://proj.goldencode.com/issues/24">#24</a>)?</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=354912015-11-27T17:04:36ZVadim Gindinvig@goldencode.com
<ul><li><strong>File</strong> <a href="/attachments/download/4422/2711_rev10976.diff">2711_rev10976.diff</a><a href="/attachments/4422/2711_rev10976.diff"><img src="/images/magnifier.png" alt="Magnifier" /></a> added</li></ul><p>Here is the current changes diff (base on revision 10976 of the branch 2677b). Changes solve 3 bugs, described in the note 1 of this task. Please review and approve commit.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=354932015-11-27T18:06:16ZGreg Shah
<ul></ul><p>Go ahead and check these into 2677b.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=354962015-11-27T18:29:04ZVadim Gindinvig@goldencode.com
<ul></ul><p>Committed with revno 10978.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=355032015-11-27T19:08:49ZGreg Shah
<ul></ul><p>Are there any issues mentioned in this task which are not yet fixed AND which are not part of some other open task?</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=355102015-11-27T19:24:13ZVadim Gindinvig@goldencode.com
<ul></ul>There are the following issues:
<ol>
<li>CHUI. Dynamic attach/detach menubar (MENUBAR layout problems). It correlates with the task <a class="issue tracker-1 status-1 priority-3 priority-lowest child" title="Bug: Fix MENUBAR layouting in a window (New)" href="https://proj.goldencode.com/issues/2557">#2557</a></li>
<li>CHUI. Fix pop-up menu layout (popup-ext.p).</li>
<li>GUI. The case when opened sub-menus can reside outside of the window. It correlates with the task <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: GUI combo-box drop-down needs to be able to draw outside of it's containing top-level window (Closed)" href="https://proj.goldencode.com/issues/2837">#2837</a>.</li>
</ol> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=358272015-12-12T11:15:21ZGreg Shah
<ul></ul><blockquote>
<p>CHUI. Dynamic attach/detach menubar (MENUBAR layout problems). It correlates with the task <a class="issue tracker-1 status-1 priority-3 priority-lowest child" title="Bug: Fix MENUBAR layouting in a window (New)" href="https://proj.goldencode.com/issues/2557">#2557</a></p>
</blockquote>
<p>It was my understanding that this was a GUI-only issue as noted in <a class="issue tracker-1 status-1 priority-3 priority-lowest child" title="Bug: Fix MENUBAR layouting in a window (New)" href="https://proj.goldencode.com/issues/2557">#2557</a>.</p>
<blockquote>
<p>CHUI. Fix pop-up menu layout (popup-ext.p).</p>
</blockquote>
<p>This is still broken? Is it already being worked in another task?</p>
<p>If it is broken and not being worked, please create a new task for this and post the task number here.</p>
<p>I plan to close this task once that task is created, unless you know of a reason I should not.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=358512015-12-14T07:22:56ZVadim Gindinvig@goldencode.com
<ul></ul><p>I've created the task <a class="issue tracker-1 status-1 priority-4 priority-default" title="Bug: Fix pop-up menu layout for CHUI (popup_ext.p) (New)" href="https://proj.goldencode.com/issues/2933">#2933</a> for CHUI layout errors.</p> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=358572015-12-14T13:47:33ZGreg Shah
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul> User Interface - Bug #2850: menu/simple_sm.p drawing issues in Swing clienthttps://proj.goldencode.com/issues/2850?journal_id=475012016-11-16T17:12:26ZGreg Shah
<ul><li><strong>Target version</strong> changed from <i>Milestone 12</i> to <i>GUI Support for a Complex ADM2 App</i></li></ul>