Thanks Jacque,
> On Dec 14, 2014, at 12:47 PM, J. Landman Gay wrote:
>
> It seems like expected behavior. If the file path is wrong, nothing happens
> and the player retains whatever it was previously set to. If there was a
> filename set then it stays there. The engine doesn't remove the prev
On Sun, Dec 14, 2014 at 11:16 AM, Richmond
wrote:
> On 14/12/14 18:30, Dr. Hawkins wrote:
>
>>
>>
> If I do roll back, though, it's not going to be to wait for 7, but to get
>> by until I figure out how to transfer my effort to another platform
>> entirely.
>>
>
> "wait for 7" sounds odd as we,
Thanks for the ideas. The final text ends up in an XML export. We see Hindi in
the Excel spreadsheet that the translators are providing, but it ends up as
scrambled Roman characters in Filemaker. I think though that those characters
will end up looking right if I set the font to a Hindi one. One
Hi Colin
Are you trying to use Hindi for the FileMaker screen text, or in the fields
where the user adds data?
Option 1
I add a global field example _Text Header to the layout using a "Merge
Field", then I use a calculation to equal the value assigned and assign
that value from a field with the
Last post on this, things are working well enough that I'm happy. In case
anyone is interested, here is a link to a stack with 3 sliders, r, g, b
sliders so that the weight of each color can be adjusted during cycling.
All it does is change the background color of the card based on the sliders
and
Made a discovery. Copy and paste can work if you paste into the right program/
It seems that fonts that can show Roman, Chinese, Japanese, and Thai, cannot
show Hindi. The solution may be to change the font to a Hindi one just when
using Hindi, and leave it alone for all other languages.
Not sure if it would work, and I have no way to try it, but I think you
could set up the spreadsheet as an odbc datasource and pull from it using
lc database functionality. Pretty sure that part work, but whether the
hindi would arrive intact is another question.
On Sun, Dec 14, 2014 at 2:00 PM,
Nobody replied to this question, so here’s an easier one:
You’re looking at an Excel spreadsheet, and can clearly see Hindi text in the
cells. How do you get that text out of Excel? Copy and past doesn’t work, nor
does exporting Unicode text.
> On Dec 2, 2014, at 7:29 PM, Colin Holgate wrote:
On 12/13/2014, 8:37 PM, Timothy Miller wrote:
I’m in version 6.7.0 on Macintosh. I’m not very good at searching for
bugs, so it’s possible it’s a fixed bug.
If you set a player filename to an invalid filename, by hand or by
script, the player seems to play the last valid filename entered,
even t
On 14/12/14 18:30, Dr. Hawkins wrote:
On Sun, Dec 14, 2014 at 1:17 AM, Richmond
wrote:
Well, if you must work with a release candidate I honestly don't understand
why you are surprised there are problems.
Because "release candidate" means "more than beta; we think it's good to
go, but need t
On Sun, Dec 14, 2014 at 8:23 AM, tbodine
wrote:
> Two things I found helpful:
> * Isolate LC7.x and any plug-ins, tool stacks and codebase stacks it uses
> on
> a separate user account or machine from the same resources used for LC6.
>
> I'm absolutely free of plugins and external stacks :)
And
Richard,
Sorry for your woes. I'm finding LC7 RC3 quite stable so far.
Two things I found helpful:
* Isolate LC7.x and any plug-ins, tool stacks and codebase stacks it uses on
a separate user account or machine from the same resources used for LC6.
* Be mindful of stack format versions by check
On Sun, Dec 14, 2014 at 1:17 AM, Richmond
wrote:
> Well, if you must work with a release candidate I honestly don't understand
> why you are surprised there are problems.
>
Because "release candidate" means "more than beta; we think it's good to
go, but need to confirm"--whereas livecode "releas
You can also do a sneaky if you want to see the stackfileversion of one
stack from another.
you can: send "put the stackfileversion into "
to stack "stackname"
On Sun, Dec 14, 2014 at 9:17 AM, Klaus major-k wrote:
>
> Hi David,
>
> > Am 14.12.2014 um 17:02 schrieb David Epstein :
> >
> > Is ther
Hi David,
> Am 14.12.2014 um 17:02 schrieb David Epstein :
>
> Is there a way to determine by script which version of LC’s file format an
> existing stack uses?
> I see that I can set the file format version when saving a stack by setting
> the stackFileVersion,
> but I’d like to write a scri
Is there a way to determine by script which version of LC’s file format an
existing stack uses? I see that I can set the file format version when saving
a stack by setting the stackFileVersion, but I’d like to write a script that
saves a stack and leaves unchanged its prior version.
Many thank
Hello,
> Le 14 déc. 2014 à 02:44, Dr. Hawkins a écrit :
>
> Is anyone else seeing these? I haven't had this problem with any prior
> release.
Having the same problem.
Using unicode doesn’t allow me to work with a previous version of LC.
>
> The only vaguely repeatable related event I've seen
from liveCodes' mobile release notes...
When an application is installed on a phone (or in the simulator) a number of
initial folders are
created for use by the application. You can locate the paths to these folders
using the
specialFolderPath() function with the following selectors:
• home –
Richmond, if you want more than a nodding acquaintance with Unicode, I think
you have to shift to the various versions of LC7. I know SOMETHING could be
done in Unicode before this, but not the things I (and I suppose many others)
wanted to do, however modest.
FWIW, none of the LC7 release can
On 12/14/2014 02:44 AM, Dr. Hawkins wrote:
Is anyone else seeing these? I haven't had this problem with any prior
release.
The only vaguely repeatable related event I've seen is that if I have an
inspector open and change a custom property, it crashes if a piece of code
tries to access that pr
20 matches
Mail list logo
