AnsweredAssumed Answered

Grouped Lines and Tab Panel Bug

Question asked by Pereljon on May 13, 2009
Latest reply on Jun 24, 2009 by TSGal

Summary

Grouped Lines and Tab Panel Bug

Description of the issue

   FileMaker Product(s) involved:FileMaker Pro 9 / FileMaker Pro Advanced 9 / FileMaker Pro Advanced 10 Operating System(s) involved:Mac OS X 10.4.11 / Mac OS X 10.5.6 Detailed description of the issue:Nudging grouped horizontal lines out of the left or top border of a tabbed panel causes problems with the grouped lines. Exact steps to reproduce the issue:  1. Create a new FileMaker file.2. Create a new tab panel with a single tab group.3. Create two lines inside of the tab panel.4. Group the two lines together.5a. Nudge the grouped lines across the left edge of the tab panel.5a1. If the lines are left-aligned (and both cross the left edge at the same time) they will become part of a larger group that is grouped with the tab panel. If you move the tab panel the grouped lines don't move, but if you move the grouped lines the panel does move.5a2. If the lines are NOT left-aligned then the grouping on the lines will be broken as soon as the left-most line crosses the left edge of the tab panel. 5b. Nudge the grouped lines across the top edge of the tab panel.  5b1. If the lines are top-aligned then (and both cross the top edge at the same time) they will become part of a larger group that is grouped with the tab panel. If you move the tab panel the grouped lines don't move, but if you move the grouped lines the panel does move.5a2. If the lines are NOT top-aligned then the grouping on the lines will be broken as soon as the top-most line crosses the top edge of the tab panel.  Expected ResultGrouped lines that are dragged out of a tab panel should not have their grouping affected in any way.Actual ResultGrouped lines that are dragged out of the left or top edge of a tab panel have their grouping affected.Exact text of any error message(s) that appeared: NONEAny additional configuration information/troubleshooting that is relevant to the issue: NONEAny workarounds that you have found: NONE  Please see below for an example of how to provide this information:   

Outcomes