Were you using the Project Browser? I thought I'd try it because the app
browser doesn't offer drag-relayering, but the same thing happened to me
when I dragged a control upwards. It popped into the group above it in
the list.
On 11/11/16 10:09 PM, Bob Sneidar wrote:
Nope it's false. Just che
Nope it's false. Just checked.
Bob S
> On Nov 11, 2016, at 18:39 , Phil Davis wrote:
>
> Sounds to me like 'relayerGroupedControls' may have been set to true?
> Otherwise I can't imagine it would be swallowed whole by the next lower-layer
> group.
>
> Phil Davis
>
>
>
> On 11/11/16 6:18
Sounds to me like 'relayerGroupedControls' may have been set to true?
Otherwise I can't imagine it would be swallowed whole by the next
lower-layer group.
Phil Davis
On 11/11/16 6:18 PM, Bob Sneidar wrote:
Not sure if this is a bug actually. I recently selected a data grid and moved it back
Not sure if this is a bug actually. I recently selected a data grid and moved
it back one level, and it disappeared! Select Grouped was off. I discovered my
errant datagrid had been added to the group one level back, and because the
boundaries of that group did not encompass the data grid, and t
On Thu, Nov 10, 2016 at 1:39 PM, J. Landman Gay
wrote:
> Interesting...I'm working with formattedheight today too. I have a field
> placed under an image where it can't be seen. It slides down sometimes and
> moves everything below it down to accomodate. When I get the
> formattedheight of the gr
I've confirmed the offset bug is resolved.
set the itemDelimiter to "|"
set wholematches to true
put "|123|456|" into tContactType
put itemOffset("456", tContactType)
will return 3. Prior to the fix it would return 0.
Bob S
___
use-livecode mailing
