On September 12, 2016 9:57:40 PM Sannyasin Brahmanathaswami
wrote:
But both the Project Browser and RevApplicationbrowser do not reflect the
change. Once in a while they do… but 80% of the time, change of layers are
not reflected/updated.
Is there a way force refresh
> On 13 Sep 2016, at 12:56 PM, Sannyasin Brahmanathaswami
> wrote:
>
> also… if we change the layer of a group from the property inspector, eg. the
> card has 32 layers of objects and you want to move a group on layer 19 to the
> top.
>
> You can set the layer of group 19
also… if we change the layer of a group from the property inspector, eg. the
card has 32 layers of objects and you want to move a group on layer 19 to the
top.
You can set the layer of group 19 to 35 (in the property inspector) and it
actually moves to the top (you can see it on the card) and
I think you should be able to both relayer within the group and drag an object
out of a group into its parent group or card so it sounds like there’s an issue
there.
> On 13 Sep 2016, at 12:08 PM, Sannyasin Brahmanathaswami
> wrote:
>
> the Project Browser is much improved
the Project Browser is much improved an very stable now… Thanks for whoever did
the hard work there.
Today, with relayerGroupedControls set to default/false.. I inadvertently
dragged a group into another group in the Project Browser.
Now any attempt to change the layer of the group B that
OK… so long as we are using bracket form…
someArray [
]
then we will get numeric, sortable keys… so than just go ahead and use standard
JSON notation inside the array..
got it. tks
On 9/12/16, 11:31 AM, "use-livecode on behalf of Monte Goulding"
On 9/12/16 6:38 PM, J. Landman Gay wrote:
So I tried on a Samsung S4. On that device, the "installing" dialog
appears and nothing else happens. I waited two or three minutes, then
had to force-quit LC because there is no way to cancel the dialog.
And on restarting, it did install. No idea what
On 9/12/16 5:17 PM, panagiotis merakos wrote:
If the device name is shown but it is dimmed, could it be the case that you
have not selected to build for Android?
Yes, sorry, that was it. We're sharing the stack back and forth and I
should have realized the setting had been changed.
But now
Sannyasin Brahmanathaswami wrote
> but the example was
>
> Parent X (a behavior for)
> Child Y and Child X,
> where Child X was also a behavior for
> Child A
Hopefully that's a typo and not a circular reference.
So
A
|
BC
|
D
Is perfectly reasonable. B
> On 13 Sep 2016, at 8:17 AM, panagiotis merakos wrote:
>
> If the device name is shown but it is dimmed, could it be the case that you
> have not selected to build for Android?
The other option would be if the mode of your stack is not 1 or it’s not the
topStack.
Cheers
On Mon, Sep 12, 2016 at 9:58 AM, J. Landman Gay
wrote:
> I've been seeing it too, though not much more often than in LC 7. I still
> haven't figured out what triggers it and I never use an external editor.
I usually see it when I've opened scripts in an editor, and
If the device name is shown but it is dimmed, could it be the case that you
have not selected to build for Android?
On 12 Sep 2016 22:15, "J. Landman Gay" wrote:
> Was there a change in RC2 in recognizing Android test devices? I've tried
> three different ones and LC
Folks:
The beginners’ guide, which is access through LC 8.01 (rc2) seems to be out of
date. I was sending a link to a guy I’m trying to get interested and I see, on
the first page, stuff like:
Under iOS:
LiveCode recommends the following set up:
Platform Xcode SDK Simulators Included
Snow
Thanks
> On 13 Sep 2016, at 7:40 AM, J. Landman Gay wrote:
>
> On 9/12/16 4:17 PM, Monte Goulding wrote:
>> Everything needs a report so it can be tracked for testing.
>
> http://quality.livecode.com/show_bug.cgi?id=18375
>
> --
> Jacqueline Landman Gay |
Panos,
Thanks for the info. I kept meaning to thank you and just got diverted. I
was just looking for a complete list. I'll dig into the release notes next
time.
Thanks to you and JLG for your fast answers!
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
> On 13 Sep 2016, at 1:11 AM, Matthias Rebbe
> wrote:
>
> Is this a known behaviour or should i file a bug?
I’m not aware of it as a known issue
Cheers
Monte
___
use-livecode mailing list
On 9/12/16 4:17 PM, Monte Goulding wrote:
Everything needs a report so it can be tracked for testing.
http://quality.livecode.com/show_bug.cgi?id=18375
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
I’m happy to report that callbacks seem to be working with DirectShow in
Windows in LC 8.1 RC2.
Basic:
Callbacks are a property of a player. They are basically are a list of numbers,
each line followed by a message name. The number corresponds to a time in a
movie/audio file loaded into a
> On 13 Sep 2016, at 7:23 AM, Sannyasin Brahmanathaswami
> wrote:
>
> this seems "hacky" but can now order the keys because they default to numeric
> index
It is not hacky. It is the way you represent sequences in JSON. The hacky part
is the pipe delimiter. Try:
If you import JSON like this:
{
"colormeds": {
"progress": {
"level": "1",
"cycle": "1"
},
"colorwheel": {
"Red": "255,0,0",
Everything needs a report so it can be tracked for testing.
Sent from my iPhone
> On 13 Sep 2016, at 7:07 AM, J. Landman Gay wrote:
>
> I didn't open a report, I thought the behavior was either intentional or
> unavoidable. If you're submitting a fix anyway, probably
Was there a change in RC2 in recognizing Android test devices? I've
tried three different ones and LC won't allow any of them. Terminal
("adb devices") sees them, and they are in the LC Test Target menu, but
the device name is dimmed and can't be selected.
I've relaunched LC several times,
On 9/12/16 3:43 PM, Monte Goulding wrote:
I was pretty certain we had identified and sorted that out but I can
see we haven’t. Have you opened a report? It’s a fairly easy fix
which I’ll submit today for 8.1.1 RC 1.
I didn't open a report, I thought the behavior was either intentional or
> On 13 Sep 2016, at 6:29 AM, J. Landman Gay wrote:
>
>> Actually this should be resolved in RC 2. I presume you are still seeing it
>> there?
>
> Yup.
Sorry Jacque
I was pretty certain we had identified and sorted that out but I can see we
haven’t. Have you
http://www.easyrgb.com/index.php?X=MATH=02#text2
followed by
http://www.easyrgb.com/index.php?X=MATH=16#text16
?
On 12/09/2016 20:49, Sannyasin Brahmanathaswami wrote:
@ Scott:
changing constants to
constant color1 = "255,0,0" -- red - primary
constant color2 = "255,64,0" -- red-orange -
On 9/12/16 3:20 PM, Monte Goulding wrote:
Actually this should be resolved in RC 2. I presume you are still seeing it
there?
Yup.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Actually this should be resolved in RC 2. I presume you are still seeing it
there?
Sent from my iPhone
> On 13 Sep 2016, at 6:01 AM, J. Landman Gay wrote:
>
> Or I could just live with it.
___
use-livecode mailing list
I'm undecided about how to classify this behavior. I have LC prefs set
to always save stacks in their original stackfile format. That mostly
works transparently except in the case of script-only stacks.
LC stores the original stackfile version as a custom property in the
stack, and since
Mark Weider wrote:
That is indeed classical inheritance.
Multiple inheritance is properly not allowed in LiveCode and would look like
this
Behavior_button A
Behavior Button B
Behavior Button C
# has both button A and button B assigned as behaviors
@ Scott:
changing constants to
constant color1 = "255,0,0" -- red - primary
constant color2 = "255,64,0" -- red-orange - tertiary
constant color3 = "255,127,0" -- orange - secondary
constant color4 = "255,191,0" -- orange-yellow - tertiary
constant color5 = "255,255,0" -- yellow - primary
Sannyasin Brahmanathaswami wrote
> Theoretically I could have (I will declare these as objects, but of course
> now we can also use livecodescript text only stacks)
>
> Behavior_button A
>
> Behavior Buttons B and C
> # both have behavior A assigned
>
> Button D
># with button C
On 9/12/16 1:54 PM, J. Landman Gay wrote:
I'm seeing similar things, and wondering if a few crashes and lockups
I've had are related. There seems to be a problem with window
identification in general but I can't pin it down.
I'm wondering if it's related to script-only stacks. If anyone has
On 9/12/16 10:29 AM, Sannyasin Brahmanathaswami wrote:
OK, this seems to be another case of the mysterious LC 8.* IDE
issues.
e.g. after rebooting and making a big button with opaque false and
small label.. it works… a few moments ago I could not invoke the
property inspector for any object. I
On 9/11/16 11:47 PM, Roger Guay wrote:
How does one include the required icons in standalones using v8?
Where is this “icon library” you speak of?
I misspoke, I meant the Image Library which is no longer available in
the menus. We can still import images manually as before.
--
Jacqueline
Thanks Scott.. this gets me very close and I can see the pattern.
I can tweak this to get to the "official" formal color wheel which has the
three primaries, three secondaries and six tertiaries in proper order
see: e.g.
Hi.
Not sure what you are asking, but do you know about the "colorNames" property"?
Craig Newman
-Original Message-
From: Sannyasin Brahmanathaswami
To: How LiveCode
Sent: Mon, Sep 12, 2016 10:56 am
Subject: Algoritm for RGB Values
I posted a stack that creates a color wheel in a graphic using a conical
fill gradient. You may want to adjust the colors if you need different
values.
In your message box:
go url "http://tactilemedia.com/download/colorwheel.livecode;
Regards,
Scott Rossi
Creative Director
Tactile Media,
One instance in which I have seen this message is if I decide to name/rename a
stack after I have added script to it. Going to the script editor window after
renaming and saving triggers this message.
Tore
> 12. sep. 2016 kl. 18.58 skrev J. Landman Gay :
>
> I've
I've been seeing it too, though not much more often than in LC 7. I still
haven't figured out what triggers it and I never use an external editor. If
someone could tell us what the algorithm is for determining the warning I
could note what I've done right before it happens the next time I see
I think when I looked into this
I found there wasn’t any predicable
logic to this. You just have to look
up the values for the colors you want.
I suppose you could create a table
for just the colors you need and then
make your selection based on your table.
I found this on Wikipedia:
The
OK, this seems to be another case of the mysterious LC 8.* IDE issues.
e.g. after rebooting and making a big button with opaque false and small
label.. it works… a few moments ago I could not invoke the property inspector
for any object. I had to reboot LC
then I copied a button from one
Mark Wieder" wrote:
Well, most of the article rants about multiple inheritance, which is
indeed a bad idea. But of course you know that's different from chained
behaviors, so no worries there.
BR: actually I don't know how that is different, probably I just don't
understand it
Hi again,
i found out, what was causing the problem.
I´ve pasted an utf encoded script into the script editor. With that script i
can reproduce the behaviour.
If i paste the same script iso or mac roman encoded into the script editor the
problem is solved.
Is this a known behaviour or should
before I go after this myself I wonder if anyone has already coded runtime
display of the 12 segment color wheel as RGB values
red (primary)
red-orange (tertiary)
orange (secondary
etc… through to
red-purple (tertiary)
BR
___
use-livecode mailing
Thanks to Mike Bonner for his helpful suggestions. Stack A and Stack B are both
mainStacks. Further tests seem to confirm this rule:
A setProp or getProp handler in the script of stack A cannot be invoked for a
target in Stack B UNLESS we have "started using" stack A (even if Stack A is
Also, you need to do that with groups, as groups are not clickable areas.
Are you sure your button is at the top of the pile and not partially behind
something else?
On Mon, Sep 12, 2016 at 1:57 AM, Scott Rossi wrote:
> The "hack" mentioned by Brahmanatha is a technique
Sorry! .livecodescript is the suffix
I'm don't know where script-only stacks are documented, other than in
conversations, here, but there are plenty of them in the LC bundle. For
example, look in Contents->Tools->Toolset->Libraries, or
Contents->Tools->Toolset->Palettes->Script
Hi Mike, thanks for responding.
> Funny you should bring this up, as I spent most of yesterday in the script
> editor, which is a bunch of script-only stacks (text files with LC script
> in them with the ".livecode" suffix).
Do you (does anyone) know where script-only stacks are actually
Hey, Ben,
Funny you should bring this up, as I spent most of yesterday in the script
editor, which is a bunch of script-only stacks (text files with LC script
in them with the ".livecode" suffix).
a) What are you adding, and would this be something that my long-standing
goal of hoarde-sourcing the
FWIW I've not noticed this at all (LC 8.1.0 rc2 on Mac OS X 10.11.6). I
switch apps a lot (but don't do anything editing scripts externally).
Ben
On 12/09/2016 11:04, Matthias Rebbe wrote:
Hi,
am i the only one who is noticing the “Scripts externally modified” popup very
very often in LC
Since time immemorial, I've had a plugin which attempts/pretends to add
additional buttons to the standard toolbar.
Actually what it used to do is locate the last button on the toolbar, tell the
toolbar to adjust its width to just beyond this, resize itself to be the same
height and fit the
If you have a reliable recipe then please open a report.
Thanks
Monte
Sent from my iPhone
> On 12 Sep 2016, at 8:04 PM, Matthias Rebbe
> wrote:
>
> This is driving me crazy. So is anyone else noticing this and i should submit
> it as a bug or is there
Hi,
am i the only one who is noticing the “Scripts externally modified” popup very
very often in LC 8.1RC2 here on Mac OS X 10.11.6?
With the script editor opened switching from LC to an other program and back to
LC opens the popup.
Or within LC switching from the script editor to another
Hi LiveCoders
Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!
Read issue #50 here: http://goo.gl/kXAaNW
This is a weekly newsletter about LiveCode, focussing on what's been going on
in and
The "hack" mentioned by Brahmanatha is a technique to make
clickable/draggable transparent images, it doesn't have to do with buttons
at all:
http://runtime-revolution.278305.n4.nabble.com/Grabbing-Image-with-Transpar
ent-Mask-td4699808.html#a4699809
I agree with Jacque's findings. AFAIK,
55 matches
Mail list logo