Text Answer box is white in the stand alone.

[Hohan]

I succeeded. It is a large application with many stacks. Also, LC is new to me, but I'm really starting to understand it. Indeed,
I had to adjust the text color for a certain stack.(set textcolor of this stack to black) Very simple and a much better solution than I first thought of. Thanks for your help and Merry Christmas.

[dunbarx]

Hohan.

Whoa.

I had to adjust the text color for a certain stack

What is a "certain stack"? Whatever stack you are talking about would have no influence at all on the "answer dialog" stack. What did you do?

Craig

[jacque]

Actually, the answer and ask dialogs inherit colors from the current stack, so it would affect the dialog. I had to do the same thing once.

[dunbarx]

Jacque.

Why would not the field inherit its properties from the dialog stack itself, and only that stack, as opposed to any old topStack that called the dialog? That would not work with any other pair of stacks that were in play.

Craig

[Hohan]

I succeeded. It is a large application with many stacks, ritten by other programmers. Also, LC is new to me, but I'm really starting to understand it. Indeed, I had to adjust the text color for a certain stack. Very simple and a much better solution than I first thought of. Thanks for your help.

[jacque]

Why would not the field inherit its properties from the dialog stack itself, and only that stack, as opposed to any old topStack that called the dialog? That would not work with any other pair of stacks that were in play.

I haven't looked at the scripts but I assume they set the colors so the dialogs will match the mainstack. I don't think they use normal inheritance.

[dunbarx]

@Jacque.

Hmmm. OK.

@Hohan. You need to to a search for the word "textColor" in the entire stack file. Use the tool "edit/find and replace". See what turns up.

Craig

[stam]

@Hohan. You need to to a search for the word "textColor" in the entire stack file. Use the tool "edit/find and replace". See what turns up.

Craig

Craig, arguably Hohan does not need to do this as it’s done already and the problem is sorted
According to at least two posts above in any case lol
Merry Christmas

[dunbarx]

Stam.

Hohan seems to have solved his problem. That has nothing to do with (my) understanding how.

He had a nearly unreadable washed out text in an answer dialog. I duplicated at least one way to emulate that by globally setting the backColor of the answer dialog stack.

Hohan said:

...had to adjust the text color for a certain stack.(set textcolor of this stack to black)

Great news But "this stack"? And I still do not know what he did in the project browser.

So when, exactly, did we figure out what happened?

Craig

[jacque]

He mentioned there were many stacks, and I assumed only one put up a dialog. "This stack" is presumably that one.

[dunbarx]

@Jacque.

I made a new stack in a new session, and, just to make sure:

Code: Select all

set the textColor of this card to "yellow"
set the textColor of this stack to "yellow"

But when I invoke an ask dialog, it looks rather normal. Only when I explicitly set the textColor of the dialog stack itself, as I posted ages ago, does the dialog act as one might expect with such a hack. That is, all of the dialog text is colored yellow.

Those settings do not stick between sessions. The dialogs "reset" to the usual black textColor.

Craig

[jacque]

It only happens in standalones if I remember right.

[dunbarx]

It only happens in standalones if I remember right.

I am in the IDE.

Craig

[stam]

It only happens in standalones if I remember right.

I am in the IDE.

Craig

Well that makes sense.
The OP only saw this in standalone, not in IDE
You're not seeing it in IDE and you obviously haven't built a standalone to test.

I think it's safe to say this is a caveat to remember - if you change the text color of a stack that launches an asnwer/ask dialog it can affect it as standalone but not in the IDE.
There are a few things like this like arrow navigation - was false in IDE but true in standalone, so users could willy nilly just bypass all password controls and navigate the entire stack with arrow keys until I realised this (incidentally this *should* be fixed now).
It all goes to show that standalones should be beta tested extensively, just design in IDE is not sufficient.

Things like this happen. Mystery solved.
Arguably if anyone cares enough a bug report should be submitted but given the current priorities it's doubtful this will be addressed... not sure there is any mileage in discussing this further..........

[FourthWorld]

There's no place like Home.