You never need an excuse with me. On the contrary, having an adventurous
mind hardly needs an excuse at all.
In fact, where you're headed is a potentially exciting place.
I have a need for something tangentially related for a web production
tool, where I need to reproduce in an LC lib some of
Thank you for your feedback, Graham.
If it takes more than a quick skim to get to the "a ha!" of using groups
well to reduce scripting, I'll bet I can revise that to be clearer.
Help me understand something - anyone, please chime in:
Resizable windows have been around since the dawn of GUI OS
Richard,
it wasn't that you over-wrote it - the problem was I over-thought it.
My excuse is that I have been thinking quite a bit this last week about
whether there was a (simple enough) approach to layout that would allow
"rows & columns" semi-flow layout to be nearly automatic, and be
possi
Very good thoughts there, Alex.
The assumptions you list would be important to keep in mind if one were
aiming to generalize basic layout handling, with libraries that have
nicely-designed APIs, or even further with virtual props that would lend
themselves well to reducing things further to si
On the MobileDemo stack, there are a couple scripts that would be useful.
https://github.com/bwmilby/mobileDemo/tree/master/mobileDemo_Scripts
stack_MobileDemo_button_id_1024
stack_MobileDemo_card_id_1002
The button script is a behavior applied to 2 groups on the card. There are
6 buttons that wi
Richard, thanks for these valuable insights. I am doing my best to absorb them
as quick as I can, meanwhile making use of FullScreen mode just to get my app
running before it becomes redundant. You are right, it has been very difficult
to gather comprehensive info on the topic until now.
Graham
On 27/04/2020 21:29, Richard Gaskin via use-livecode wrote:
I've been itching to write a tutorial on using specific object
placement ("Responsive Design", as the kids call it) to compliment the
Lesson we've had for years on the other mobile layout option,
FullScreenMode.
I had a few minut
Graham (and Brahmanathaswami may enjoy this too):
I've been itching to write a tutorial on using specific object placement
("Responsive Design", as the kids call it) to compliment the Lesson
we've had for years on the other mobile layout option, FullScreenMode.
I had a few minutes over the we
I just pushed an update to my demo that adds a button to advance to the next
card to make it a little more obvious. The second card has some shapes to see
how they distort and a few text sizes. The third card is a demo of the
TreeView Widget. I may tweak that a bit though to demonstrate using
I hadn't thought about it that way. That's easier to remember.
On 4/10/20 1:20 PM, Brian Milby via use-livecode wrote:
showAll is the same as letterBox but the borders are the stack background
instead of black.
Thanks,
Brian
On Apr 10, 2020, 2:15 PM -0400, Richard Gaskin via use-livecode
, wr
That description doesn’t seem correct. It partly depends on the aspect ratio of
the card. With showAll you know that all of the card area will be visible. With
noBorder you know that there will not be any black borders to the left and
right, or top and bottom of the card area.
So, with showAll
It's similar to noBorder, but noBorder scales to the short side of the screenrect and showAll
scales to the long side (regardless of orientation.)
I think. I get those two mixed up.
On 4/10/20 1:14 PM, Richard Gaskin via use-livecode wrote:
Good catch. It would be great if the Lessons were in G
Brian this is terrific! Looking at it now.
thanks so much
Graham
> On 10 Apr 2020, at 15:18, Brian Milby via use-livecode
> wrote:
>
> Take a look at my mobileDemo repo:
> https://github.com/bwmilby/mobileDemo
>
> It lets you play around with showing how a stack developed at different
> size
showAll is the same as letterBox but the borders are the stack background
instead of black.
Thanks,
Brian
On Apr 10, 2020, 2:15 PM -0400, Richard Gaskin via use-livecode
, wrote:
> Good catch. It would be great if the Lessons were in Github so they
> could be enhanced by the community. I guess f
Good catch. It would be great if the Lessons were in Github so they
could be enhanced by the community. I guess for now a comment there is
the only mechanism for filing enhancement requests.
How does showAll differ from the options shown there?
--
Richard Gaskin
Fourth World Systems
J. Lan
I hadn't seen that lesson before. They didn't include showAll though.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On April 10, 2020 12:11:40 PM Richard Gaskin via use-livecode
wrote:
Brian Milby wrote:
> I also built a stack last
Graham Samuel wrote:
> Thanks Richard, for that typically useful reply! I have indeed written
> many a resize handler, but getting back into this stuff I was struck
> by how messy it can get. Right now I don’t even know if say a field
> with 12 point type in it has to be changed to a smaller or la
Brian Milby wrote:
> I also built a stack last year to show how much space is not used when
> using different modes. I'll see if I can locate that and make it
> available.
Useful I'm sure, but this lesson about using fullScreenMode as an option
for handling different screen sizes includes illu
Take a look at my mobileDemo repo:
https://github.com/bwmilby/mobileDemo
It lets you play around with showing how a stack developed at different
sizes looks when presented on a device using the different
FullScreenModes. I have not updated it for the new iPhoneX aspect ratios,
but probably should
Thanks Jacque - sounds very practical. fullScreenMode, here I come!
Cheers
Graham
> On 9 Apr 2020, at 20:09, J. Landman Gay via use-livecode
> wrote:
>
> On 4/9/20 11:47 AM, Richard Gaskin via use-livecode wrote:
>> Graham Samuel wrote:
>> > Folks, yet again I don’t know where to look for an
Thanks Richard, for that typically useful reply! I have indeed written many a
resize handler, but getting back into this stuff I was struck by how messy it
can get. Right now I don’t even know if say a field with 12 point type in it
has to be changed to a smaller or larger rectangle with smaller
On 4/9/20 11:47 AM, Richard Gaskin via use-livecode wrote:
Graham Samuel wrote:
> Folks, yet again I don’t know where to look for an answer in the LC
> documentation.
>
> The issue is the enormous variety of screen sizes on smart phones. For
> example the iPhone XS Max has 1242 pixels width
Graham Samuel wrote:
> Folks, yet again I don’t know where to look for an answer in the LC
> documentation.
>
> The issue is the enormous variety of screen sizes on smart phones. For
> example the iPhone XS Max has 1242 pixels width, the iPhone 5 has 640.
> And there are many many more before we
Folks, yet again I don’t know where to look for an answer in the LC
documentation.
The issue is the enormous variety of screen sizes on smart phones. For example
the iPhone XS Max has 1242 pixels width, the iPhone 5 has 640. And there are
many many more before we even get to tablets…
The quest
24 matches
Mail list logo
