Dang! I thought I was learning a new word!
Bob S
On Nov 30, 2023, at 9:29 AM, ambassador--- via use-livecode
wrote:
it uses the power of the engine to its most efficient, preditable, and robust
advangage to put things exactly where you want them.
On 11/30/2023 2:20 PM, Brian Milby via use-livecode wrote:
Groups get the message when resize happens by script.
Other objects only receive the message when resized by hand.
Brian Milby
br...@milby7.com
Except, the "PowerButton" widget actually receives "resizeControl" just
as a group does w
Groups get the message when resize happens by script.
Other objects only receive the message when resized by hand.
Brian Milby
br...@milby7.com
> On Nov 30, 2023, at 1:51 PM, Paul Dupuis via use-livecode
> wrote:
>
> Thank you Richard.
>
> I see what the issue for me was. Groups do indeed re
Thank you Richard.
I see what the issue for me was. Groups do indeed receive a
resizeControl message automatically if the rect is changed by script.
However, the message (resizeControl) use seems inconsistent. For
example, while a group does received the resizeControl message, a field
does no
Craig Newman wrote:
> “reSizeControl” is a message. What I mean by that is if you are already
> running under script control, why do you need to send such a message at
> all? Can’t your handler do whatever you needed to if the user did the
> actual resize action?
He's asking about resizing that ta
On 30/11/2023 16:05, Paul Dupuis via use-livecode wrote:
resizeControl is sent "only sent when the user resizes a control by
dragging its handles. It is not sent if a handler changes the size of
a control by changing its properties (width, height, and so on)."
Basically, that dictionary entr
Paul.
“reSizeControl” is a message. What I mean by that is if you are already running
under script control, why do you need to send such a message at all? Can’t your
handler do whatever you needed to if the user did the actual resize action?
Craig
> On Nov 30, 2023, at 11:05 AM, Paul Dupuis vi
I think a property that controls this behavior would certainly have
been the best way to implement this. Any time software is changed to
behave in a way that is just about the opposite of how it used to
work, there needs to be a way for users to control that behavior. If
I'd known about y
--- On Fri, 12/31/10, Richard Gaskin wrote:
> DunbarX wrote:
>
> > Why the messages is not passed along to the card, or
> why they are sent
> > continuously, is a mystery.
>
> For most of LC/Rev/MC's life, the resizeControl message was
> consistently sent only after the user stopped performing a
Thanks Richard, I'll submit an additional note.
I agree that these are useful changes, in fact the reason I got into
the resizing issue is because of custom control I designed as a group
for my own app. It would just be so much better if changes like this
were documented in the dictionary.
Peter Haworth wrote:
Thanks Richard. I just submitted a note to the resizeControl
dictionary entry.
Thanks for adding that.
However, I didn't know until I read your email that
the resizeControl message is sent even when the resize happens by
script - that's the opposite of what the dictiona
Thanks Richard. I just submitted a note to the resizeControl
dictionary entry. However, I didn't know until I read your email that
the resizeControl message is sent even when the resize happens by
script - that's the opposite of what the dictionary says. I don't
mind submitting another d
DunbarX wrote:
Why the messages is not passed along to the card, or why they are sent
continuously, is a mystery.
For most of LC/Rev/MC's life, the resizeControl message was consistently
sent only after the user stopped performing a resize action with the
pointer tool.
But in v3.5 RunRev i
And to me. Someone probably knows the reason. As mentioned, it
didn't cause a problem for me, just didn't expect it since it's not
mentioned in the dictionary.
Pete Haworth
On Dec 31, 2010, at 1:09 PM, dunb...@aol.com wrote:
Pete.
Right you are. The message is sent continuously, like "m
Pete.
Right you are. The message is sent continuously, like "mouseMove" when the
message is trapped in the group script. As advertised in the card script.
The message watcher confirms this; continuous messages while changing, and, as
icing on the cake, one more when you are done.
Why the messa
Thanks Mark. I'm actually trying to achieve the opposite of that - I
want to resize the group and have the controls within it resize
appropriately. But all seems to be working OK, the code I've written
correctly resizes the the controls when I resize the group so no
worries. I was just s
I don't get this behavior. If I place a resizeControl handler in a card
script that beeps, and then resize simple objects or groups, I get beeps only
after I am done in all cases.
Craig Newman
___
use-livecode mailing list
use-livecode@lists.runrev.com
Pete-
Just a guess, but I think you're running into the fact that group will
adjust to the position of its controls. So if you're moving a control
around the group *is* getting resized along with it. You might try
setting the lockmessages to true while you're moving a control and
then back to fals
18 matches
Mail list logo
