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" j
. 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 not seem to. Also, what I
> specific
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
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 ab
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
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 Dup
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)."
Does anyone else really really wish that resizeControl was set when the
control
I'm thinking this may be a documentation bug, but wanted to check before
submitting.
I know that resizeControl is sent to a group when the size is updated by
script (for other controls, the message is only generated when manually
resized by dragging handles). The documentation for the me
> On 17 Jul 2017, at 9:42 am, Sannyasin Brahmanathaswami via use-livecode
> wrote:
>
> I can't any use case where you would want any group to trap a mouse event
> outside its rect.
It sounds like you want sharedBehavior on and backgroundBehavior off
If it’s a background it behaves like it’s
in the
message path. You can put an empty resizecontrol handler in objects that
shouldn't respond, or check in the group script that the target is one of
the group members, as you did.
___
use-livecode mailing list
use-livec
I saw this recently. It isn't a bug, the navigation group is a background
group so it will catch any message that isn't blocked earlier in the
message path. You can put an empty resizecontrol handler in objects that
shouldn't respond, or check in the group script that the target
t;far away" from the rect of the bottom tool bar.
context:
1) paste a chevron widget… supposed serve as a go next button
2) switch to select tool, change the shape of the widget and the bottom bar's
icons change position
So I put this in the behavrio just to confirm
on resizeCon
I have a stack that relies on the resizeControl message. But it appears
that it's broken for images on all iterations of LC 6. Everything else
sends the message - buttons, fields, graphics. And it works in all the
5.x versions I tried.
I did file a bug report in January (11689) and
Thank you Richard !
I ignored this property...
Bon souvenir de Paris
René
Le 19 nov. 2011 à 18:05, Richard Gaskin a écrit :
> One thing I've found making custom controls from groups in LC is a bit
> non-obvious but makes sense one you use it:
>
> on resizeControl
> -- do
One thing I've found making custom controls from groups in LC is a bit
non-obvious but makes sense one you use it:
on resizeControl
-- do stuff
-- then:
set the boundingRect of me to the rect of me
end resizeControl
The boundingRect property determines the working space of the
Thank you Jacque, I think I will solve my problem with this remark!
Simple, but sometimes we dont see what we have in front of our nose...
Thank you again
:-)
René
Le 17 nov. 2011 à 21:15, J. Landman Gay a écrit :
> On 11/17/11 1:23 PM, René Micout wrote:
>> I think it is not possible...
>> I thi
On 11/17/11 1:23 PM, René Micout wrote:
I think it is not possible...
I think I do place other object in the group, place object at the edge of the
group and resize the button in relation with this new object (the left of the
button = the right of the new object)... Something like that...
It is
>
>> Hello,
>> I have a problem (simple but...) :
>> 2 buttons (button 1 and button 2), with these 2 buttons I made a group.
>> The script of the group is :
>> on resizeControl
>> set the width of btn "Button 1" to (the width of me)-30
>>
gt; Hello,
>> I have a problem (simple but...) :
>> 2 buttons (button 1 and button 2), with these 2 buttons I made a group.
>> The script of the group is :
>> on resizeControl
>> set the width of btn "Button 1" to (the width of me)-30
>> end resizeContr
of the group is :
> on resizeControl
>set the width of btn "Button 1" to (the width of me)-30
> end resizeControl
> When I resize the group it is OK but when I release the mouse the group and
> the button grows...
> What is wrong ?
> Thank you
> René
_
Hello,
I have a problem (simple but...) :
2 buttons (button 1 and button 2), with these 2 buttons I made a group.
The script of the group is :
on resizeControl
set the width of btn "Button 1" to (the width of me)-30
end resizeControl
When I resize the group it is OK but when I release
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 onl
onary.
I had noticed the selectGroupedControls property in the inspector
window but thanks for mentioning that too.
Pete Haworth
On Dec 31, 2010, at 2:19 PM, Richard Gaskin wrote:
Peter Haworth wrote:
Thanks Richard. I just submitted a note to the resizeControl
dictionary entry.
Thank
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 o
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 sub
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 R
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
I was just surprised when I found that groups behave
differently than other controls in this as far as resizeControl is
concerned. Maybe I should put a note in the dictionary entry.
Craig - I haven't tried putting the resizeControl at the card level,
it's in the script of the gro
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-liv
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
The dictionary claims that the resizeControl message is sent right
after a control has been resized. That appears to be true for all
controls except groups. For groups, the resize control message seems
to be sent continuously while the group is being resized, not after
the resizing is
34 matches
Mail list logo
