LiveCode Forums

bogs wrote: ↑

Mon Mar 08, 2021 9:00 pm

Frightening, isn't it? If you keep having similar thought lines to mine, I may have to recommend institutionalization ! (Come on in, the straight jackets are fine! )

Well, if we get good enough at it, I may not have to post here at all.

I spent a good deal of time creating printing templates for a project about 10 years ago, which should fit into your setup pretty well. :) However, my app printed on Mac and Windows, and I have a vague recollection that printing is somewhat different on 'nix so it may very well be your hardware. If ...

It's normal behavior. A fixed height means that each row will be the same size. If there is more text than will fit in the height of the row, the extra will fall below the bottom border and you won't see it. You can fix the problem by ensuring the row height is set to accommodate the largest amount ...

When I want a window that sort of acts like a palette but doesn't sit on top of everything, I set the stack to modeless. You don't need to track any other stacks that way. However, it won't consistently appear above other stacks either unless you click on it.

The Android scroll/select behavior is normal. If you look at almost any other Android app you'll see the same thing. The initial touch selects the line but as scrolling begins the selection is removed. When scrolling stops another tap is required to make a selection.

It sounds like you want: print <card> from <topLeft> to <bottomRight> where the described rectangle surrounds the area of interest. Unlike printing a field, this gives you a bitmap which should capture colors and /or images. Printing can be as easy or complicated as you want. Using some of the other...

My guess: A breakpoint allows the engine to catch up because it breaks the flow of messages and effectively creates an idle period. Try adding a "wait 0 with messages" and see if that gives LC a chance to do its default behavior.

Would a custom sort function help? LC doesn't require scripts to use only the built-in options.

It works (almost) fine in LC 9.6.2 rc 2. The only issue is that the textstyle is not always reset after the handler sets the textstyle of a word. Without resetting, the textstyle remains for all subsequent characters until a different style is recognized and set. To fix that, the last case of the sw...

In your report, ask if the team has any suggestions. I can't think of a workaround for now.

I probably remembered wrong. Try keyDown instead. That should eliminate the double characters.

But the Android issue does sound like a bug (assuming keyDown still fails.)

In places (see arrows) the text styling runs not only over spaces, but in some cases halfway into other words. In other places, it does not. Goofy stuff. I haven't seen that behavior. We'd need to know how you set the text styling to see why it did that. Was it scripted? Manually selected? If scrip...

The next question would be why do I have to use a native field instead of a "regular" one to receive the scanner input. I don't know the answer but the fact is the scanner works OK with a native field and just the first digit is captured when a "regular" field is used...but this should be the subje...

I won't comment on your character, Bogs. :) Text characters though...Yes, spaces, tabs, carriage returns, and anything else that isn't visible to the eye is called "white space" when we're talking about text. It isn't clear to me what issues you had with setting textstyles, but it kind of sounds lik...

I don't think it's a bug. PreOpenCard doesn't continue the handler until each command completes.