Very interesting...
Thanks for sharing this info.
On 09/03/2019, 17:38, "use-livecode on behalf of Richard Gaskin via
use-livecode" wrote:
David Bovill wrote:
> No one using docker?
https://hub.docker.com/r/techstrategies/livecode/
--
Richard Gaskin
David Bovill wrote:
> No one using docker?
https://hub.docker.com/r/techstrategies/livecode/
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
ambassa...@fourthwor
Well, i deleted the DG (saving the internal scripts first).
Then copied the working one and adjusted it. (it's in the same stack so
no copy issues)
Regards.
Op 8-3-2019 om 21:44 schreef JJS via use-livecode:
Hi,
on one DG i can't add a column behavior, the + button is not
responsive. (lc9
revUpdateGeometry needs to be called in the preOpenCard handler to take care of
GM updates.
Thanks,
Brian
On Mar 9, 2019, 8:37 AM -0500, Tore Nilsen via use-livecode
, wrote:
> Thank you for your suggestions. I did not have any resizeStack handlers, but
> relied on the geometry manager to posit
Thank you for your suggestions. I did not have any resizeStack handlers, but
relied on the geometry manager to position the few elements I needed to
reposition. I managed to have the changes implemented on both cards by using
send resizeStack to me in a preOpenCard handler on both cards.
Best
move the resizeStack handlers from each CARD to the STACK script and
combine them so they update both cards to the new stack size
On 3/9/2019 7:51 AM, Tore Nilsen via use-livecode wrote:
I have a stack with 2 cards. On these cards, some elements change size or
position when the stack is resiz
preOpenCard is what I’ve used. I know it includes “openCard”, but it is a
different handler.
Thanks,
Brian
On Mar 9, 2019, 7:52 AM -0500, Tore Nilsen via use-livecode
, wrote:
> I have a stack with 2 cards. On these cards, some elements change size or
> position when the stack is resized. As t
I have a stack with 2 cards. On these cards, some elements change size or
position when the stack is resized. As the resizeStack message is only sent to
the current card, any changes only happen on this card. If the user then
navigates to the other card, elements will be out of order on this car
