LiveCode Forums

Rachel. I don't see the white line you speak of. Is it that the two controls do not overlie each other? That the borders are separated a bit? Try changing the value of the "step" in the repeat loop to a larger number. You will have to experiment to find the rate that looks good to you, based on how ...

Here is just about as simple a collapsible gadget as you can get, and could have been just as easily made in Hypercard in 1987. I only mention that to show how you might set started with a few tools. This uses no effects, just raw LiveCode 101. It isn't even pretty, though it can be made so. Anyway,...

Hi. There are many, many ways to do this sort of thing, and much depends on how much fun you want to have designing and using whatever gadgetry you finally settle on. Since LC gives complete control over the appearance, size and a thousand other properties, as well as offering dynamic special effect...

Hi.

I don't build widgets, but check out this:
http://lessons.livecode.com/m/4603/l/73 ... ng-widgets

They are more than just self-contained gadgets like clocks or spinners. They are keys to other worlds.

Craig

This thread is still running, eh? And now all about cute little animals. Hmmm.

Forget "Duck Soup". Move up to Groucho in "Night at the Opera"

https://www.youtube.com/watch?v=BjIZwv5aENQ

Craig

What Bogs said. It takes a little while to integrate the basics of LiveCode so that you can use basic tools to do some real work. What Bogs mentioned, and what he implied you need to learn, is that you can isolate virtually any part of a body of text. LiveCode calls that "chunking". A word is a chun...

Richard makes a point, in that the debugger coming to the front is a "change" in the environment, and the loss of focus in the field is a clear result of that.

Just the way things work.

Craig.

Bogs wrote; sticking a simple breakpoint into the field handler prevents *actual* typing from the keyboard from showing up Right. More is happening than simply "freezing" the process and restarting it. Something changes, which is counterintuitive. This seems sinister, and might throw a user, like me...

Also made one try canceling the pendingMessages, and still no luck.

These two still might do the trick, with a little more investigation.

Craig

Thunder.

Play around, but: Did not work.

Craig

Bogs.

Well, what do you know? I have never used an effect. Very cool.

Craig

Hi.

What Klaus said.

But do read the dictionary entry for "numberFormat". It is important to know that many formatting issues require that at least one mathematical operation be run before the format will be applied.

Craig Newman

Bogs. Throwing the breakpoint in doesn't change that your putting in code to pass the event (I think). But it does. No char is written into the field. Stopping the handler, and then continuing breaks the flow somehow. Hermann. This is interesting. The very first answer dialog should block all subseq...

Bogs.

Ah, now I see what you were talking about. I think, though, that it was the top border.

Your effects solution is cool, but would not work for, say, the right side, no? The kluge is at least adaptable to any one or more of the four borders.

Craig

Nothing happens. Apparently "keydown" has to originate from the field itself for a char to appear at the insertion point: on mouseUp --in the button send "keyDown C" to fld 1 end mouseUp on keyDown tKey --in the field pass keyDown end keyDown And as for poking around the edges, I like the solitude. ...