I was thinking the same thing. Maybe theres a "put after" somewhere..
On Mon, May 11, 2015 at 4:14 PM, J. Landman Gay
wrote:
> On 5/11/2015 2:11 PM, David V Glasgow wrote:
>
>>
>> I got the field to report its layermode at various points, and it
>> seems to be static. I was really optimistic t
On 5/11/2015 2:11 PM, David V Glasgow wrote:
I got the field to report its layermode at various points, and it
seems to be static. I was really optimistic that that might be the
issue, but it seems not.
Are we at the bottom of the barrel yet?
The only other thing I can think of is that you h
> On 9 May 2015, at 4:18 pm, J. Landman Gay wrote:
>
> How about the layermode of the field? If it's not static it will be cached.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
>
I got the field to rep
On May 9, 2015 7:38:06 AM CDT, David V Glasgow wrote:
>
>It doesn’t seem to matter whether the same custom property has been
>displayed before. I can just move back and forth between two buttons
>and get a steady (albeit variable) increment, so I don’t think it is a
>caching thing. But why don’t
> On 8 May 2015, at 6:31 pm, J. Landman Gay wrote:
>
> Does it still happen if you remove the visual effect?
>
>
Thanks for the suggestion Jacqueline. Yes it does.
However, if I comment out the whole show line, the problem disappears. It
seems it is specifically related to that.
It d
Does it still happen if you remove the visual effect?
On 5/8/2015 9:35 AM, David V Glasgow wrote:
Hello folks,
I am hesitant to call this a memory leak problem, but it doesn’t seem far off.
I have a group consisting of an array of 18x 5 button radio buttons, each set
prepended by a field la
