Monte Goulding wrote:
> Google assumes we are all working in java where the density is
> abstracted into 4 common plus a couple of less common density groups.
> LiveCode doesn't do that abstraction for us so we get the actual
> pixels on screen.
>
> The DisplayMetrics class has a density property
Thanks Mark. I'm new to the server stuff so was not familiar with the
process. LC has a lesson where they suggest you can connect to MySQL
directly on their site (I think) but maybe I am misunderstanding them.
http://lessons.runrev.com/s/lessons/m/4071/l/7003-Connecting-to-a-MySQL-database
Thats
Mark Schonewille-3 wrote
> What made you think that you could use the RunRev server to test your own
> MySQL scripts? Have you got any documentation from RunRev about this?
Hi Mark, I think the part that confused me was the line "RunRev has set up a
sample database which these scripts will use". T
Thank you Mark, that fixed the problem.
However, I'm not sure I can use that solution. Won't lock messages apply to
the stack I'm opening as well as the stack which issues it? If so, that
could interfere with the opened stack's processing.
If nothing else though, it narrows down the problem to t
What I mean is to a java dev the screen is in an abstracted width, height and
density. We need to work in the actual width, height and density.
Regarding the bug report it might be good I we could add a recipe. Perhaps a
recipe for creating a ldpi and xhdpi emulator at the same screen size then
Peter-
Saturday, September 29, 2012, 11:36:34 AM, you wrote:
> However, I'm not sure I can use that solution. Won't lock messages apply to
> the stack I'm opening as well as the stack which issues it? If so, that
> could interfere with the opened stack's processing.
Well, yes, that's the whole
Monte Goulding wrote:
> Regarding the bug report it might be good I we could add a recipe.
> Perhaps a recipe for creating a ldpi and xhdpi emulator at the same
> screen size then a stack to run on them. Then a couple of screenshots
> to save them the time of actually doing it...
Are they now re
Perhaps this has been discussed before, but I guess I wasn't paying
attention. Here goes:
I like to take certain "clumps of code" or handy hints from the digest and
paste them into Scriptors Scrapbook. 'cause you never know when they will
come in handy.
I have found that the only way I can get th
On Sat, Sep 29, 2012 at 7:46 PM, Richard Gaskin
wrote:
> Monte Goulding wrote:
>
> > Regarding the bug report it might be good I we could add a recipe.
> > Perhaps a recipe for creating a ldpi and xhdpi emulator at the same
> > screen size then a stack to run on them. Then a couple of screenshots
I think in this case where it's easy to show that its virtually impossible to
design a satisfactory UI for both devices then it would be beneficial to have
at least some screenshots. Just two screenshots of the same stack in different
density screens of similar size should do the job. If I get a
This is lcStackBrowser, it has to open stacks and allow them to do whatever
they do. This happens with any stack that I open, it's not just
one particular stack. I even created a new main stack with no objects, no
scripts of any sort, then opened it and got the same problem.
And here's more weir
That prompted me to see what happened if I removed the answer file dialog
and just hardcoded a stackfile path. Guess what - everything works
perfectly.
So something about the answer file dialog is causing this problem to occur.
The command is:
*
*
*answer* file "Select stackfile to open" with *t
I've long thought that this is a design flaw in the QCC. There should be
two fields, one to specify whether the entry is a bug or an enhancement
request and a separate one to define the severity. That way, a request
such as this could go in as a critical enhancement whereas now there is no
way to
Same here. Paste from almost any clipboard source needs notepad an an
intermediary.
Ralph DiMola
MIS Director
Evergreen Information Services
rdim...@evergreeninfo.net
-Original message-
From: Cal Horner
To: use-livecode@lists.runrev.com
Sent: Sat, Sep 29, 2012 22:53:21 GMT+00:00
Su
On 9/29/12 9:15 PM, Peter Haworth wrote:
That prompted me to see what happened if I removed the answer file dialog
and just hardcoded a stackfile path. Guess what - everything works
perfectly.
So something about the answer file dialog is causing this problem to occur.
The command is:
*
*
*ans
Pete-
Saturday, September 29, 2012, 7:01:03 PM, you wrote:
> This is lcStackBrowser, it has to open stacks and allow them to do whatever
> they do. This happens with any stack that I open, it's not just
> one particular stack. I even created a new main stack with no objects, no
> scripts of any
16 matches
Mail list logo
