LiveCode Forums.

Hello,
if I want to build a mobile App, I've to set up multiple cards for the different screen-resolution and different looks for multiple plattforms.

But the most things are the same on every card. For example such us "Name".

Can I access "Name" on every card at the same time or does I've to access every variable on every card, if there's something to change at runtime?

Hi,

I've to set up multiple cards for the different screen-resolution and different looks for multiple plattforms.

Not clear on your full question but for the above, no.
Here:
http://lessons.runrev.com/m/4069/l/1564 ... ll-devices

Simon

Hi Simon,
no the auto-scale feature of LiveCode is useless, because of geometric deformation and/or borders and/or missing content for business-apps.

So I've to work with the much better solution altMobileResizer or set up multiple cards (one per screen-resolution, to use the available space of the different resolutions instead of just filling it ^^)


Back to my question:

What I mean is, if you've got two cards, which should show one same label "lastname" (such as), is there a way to update the content of label "lastname" on multiple cards with one line of code or do I have to address every label "lastname" on the multiple cards manually?

Hi DevBoyLars,

no the auto-scale feature of LiveCode is useless, because of geometric deformation..

You are the second person this week to say that? Can you show me an example?
I already know about altMobileResizer.

Thanks,
Simon

Oh wait... no you, are the same person to say that
Still... very interested in your example.

Back to your question, how about grouping your field "lastname" and setting it to "behave like background"?

Simon

If you are seeing deformation then you are probably using the wrong type of scaling. Some of the fullscreen options follow the original ratios so that they keep the correct propotions, others distort the proportions to force the stack to fit the current screenrect.

I helped Chipp write his resizer handlers and they always force the original ratio. But even Chipp has abandoned his resizing methods in favor of the new built-in methods because altResizer doesn't consider screen densities, which matter for some Android devices, and because using fullscreen replaces many lines of code with a single command.

Experiment with all the fullscreen modes until you find which one works best for your app. They are really quite good.

It is very simple:

If you build a card for an iPhone 4 it would never work without geometric deformation if you use build-in auto-scale. So you've to work with external tools like AltMobileResizer.

But this wasn't my question at all -.-

jacque wrote:If you are seeing deformation then you are probably using the wrong type of scaling. Some of the fullscreen options follow the original ratios so that they keep the correct propotions, others distort the proportions to force the stack to fit the current screenrect.

I helped Chipp write his resizer handlers and they always force the original ratio. But even Chipp has abandoned his resizing methods in favor of the new built-in methods because altResizer doesn't consider screen densities, which matter for some Android devices, and because using fullscreen replaces many lines of code with a single command.

Experiment with all the fullscreen modes until you find which one works best for your app. They are really quite good.

No they are truly not good.

Example 1 like above: Build a card for an iPhone 4 and auto-scale it to iPhone 5. Tada... geometric-deformation
Example 2: Build a card for an iPhone 4 and auto-scale it to an iPad... tada... geometric-deformation
Example 3: ....

It is a never-ending list. As long as LiveCode would has options like altMobileResizer to scale single opjects proportionally it is absolutely useless to build business-apps with one card for multiple screen-resolutions.

Please correct me, if I'm wrong with this

I'm guessing you don't like the loss of screen real estate when using "letterBox"?
No graphic distortion with it.

Simon

Simon wrote:I'm guessing you don't like the loss of screen real estate when using "letterBox"?
No graphic distortion with it.

Simon

Never!!

This looks damn unprofessional for a real business-app!

Ok, no one can help me with my real problem?

If you need to change the layout dynamically for different devices then you may need to write resizing code. If you want to keep the same layout for all devices, then you can probably use one of the built-in fullscreen options. Which fullscreen option you choose would depend on the layout of your stack.

In one of my stacks I use the "noBorder" option and include an area around the edges of the card that contain no controls. This resizes correctly for all the devices I support. The difference is only that users see varying amounts of border around the edges. In another app I use the "empty" option, which works well for iOS devices. For that one, I let iOS do the scaling, which works because the images are all high density.

If you can show us a screenshot of your app we may be able to suggest the correct fullscreen option to use. If you do need to change the layout, then you should stay with your current method. But remember that if fullscreen isn't appropriate for your app, it may work fine for other apps.

DevBoyLars wrote:Ok, no one can help me with my real problem?

I'm not sure I understand your question. You can get "the cardnames of this stack" if you want a list. But explain more about what you want to do with the list.

Simon wrote: ...
Back to your question, how about grouping your field "lastname" and setting it to "behave like background"?

Simon

Not doing it for you?

Simon

No, because of the fixed position :-p

As you see in my first post, I want to build multiple cards in different resolutions. So this can't works.

Is there no other way?