Not sure if this would cause the problem, but once I had gotten myself into a
pretty ugly situation that was causing some very odd behaviors:
* I had a group (A) that happened to contain another group (B).
* While editing group A, I had accidentally clicked group B (with that
"selectGroupedCon
Hello Martin, I did check that, thanks. I'm suspicious that it may have
something to do with the selectGroupedControls property that Sarah mentioned.
Changing this setting for these groups has no effect at this point and they
behave as if the property is "stuck" as true.
-Scott
On Mar 8, 201
Could it be the autohilite property?
On 3/8/10, Scott Morrow wrote:
> Recently, in one of my projects, the Application Browser stopped showing
> fields that were in a group. Furthermore, the fields in this group no longer
> allow text to be hilited. (The text can still be edited, but not somethin
Thank you, Sarah. I didn't know that. Unfortunately in this case it didn't
solve the problem. Time to rebuild, I guess.
-Scott
On Mar 7, 2010, at 9:02 PM, Sarah Reichelt wrote:
> On Mon, Mar 8, 2010 at 2:49 PM, Scott Morrow
> wrote:
>> Recently, in one of my projects, the Application Browse
On Mon, Mar 8, 2010 at 2:49 PM, Scott Morrow
wrote:
> Recently, in one of my projects, the Application Browser stopped showing
> fields that were in a group. Furthermore, the fields in this group no longer
> allow text to be hilited. (The text can still be edited, but not something
> that is re
Recently, in one of my projects, the Application Browser stopped showing fields
that were in a group. Furthermore, the fields in this group no longer allow
text to be hilited. (The text can still be edited, but not something that is
really usable.) The fields are obviously still there and runnin