The case for not trying to be so English-like

2018-04-14 Thread Mark Wieder via use-livecode

Hah! or, why hangover is one word...

https://lithub.com/attention-grammar-pedants-the-english-language-isnt-logical/

--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Player Controls in Mobile

2018-04-14 Thread Sannyasin Brahmanathaswami via use-livecode
Well in case it useful anyone I went ahead and compiled from dictionary… keep 
this for reference. iOS command deliberately not include.

Did I miss anything?

MobileControlDo idOrName, propertyName  # command

e.g.

mobileControlCreate "player", "myFirstPlayer"   


==
MobileControlDo idOrName, propertyName   # command

mobileControlDo "myFirstPlayer", "play"
mobileControlDo "myFirstPlayer", "pause"
mobileControlDo "myFirstPlayer", "stop"

==
MobileControlSet  idOrName, propertyName, value # command

Global Properties
- "rect": the bounds of the control, relative to the top-left of the 
card. For example "0,0,100,100".
- "visible": set to true or false to determine whether the control 
should be displayed.
- "alpha": set to an integer value between 0 and 255 to blend the 
control with and controls underneath it.
- "backgroundColor": Set to either a standard color name, or a string 
of the form red,green,blue or red,green,blue,alpha. Where the components are 
integers in the range 0 to 255.

Player Specific

- "filename": The filename of URL of the media to play. Setting the 
filename of the player automatically 'prepares' the movie for playback.
- "showController": Determines whether the controller is displayed over 
the content. This is a boolean value.
- "currentTime": The current position of the playhead, measured in 
milliseconds (maps to the native currentPlaybackTime property). This is an 
integer value.
- "looping": Determines whether the playback of the movie should loop 
indefinitely. This is a boolean value.

==

mobileControlGet ( idOrName, propertyName ) # function - include parenthesis

local tVisibility
put mobileControlGet("myControlName", "visible") into tVisibility
if tVisibility is true then
  ...
end if


- "id": Returns the id of the control where the name is passed.
- "name": Returns the name of the control where the id is passed.
- "rect": Returns the bounds of the control, relative to the top-left 
of the card. For example "0,0,100,100".
-"visible": Returns true if the control is visible.
- "alpha": Returns the blendlevel of the control as an integer between 
0 and 255.
- "backgroundColor": Returns the background color of the control as an 
integer between 0 to 255.
- "filename": returns the filename or URL of the media set on the 
player, if any.
- "showController": returns true if the controller is displayed over 
the content.
- "currentTime": returns the current position of the playhead, measured 
in milliseconds (maps to the native currentPlaybackTime property). This is an 
integer value.
- "looping": returns true if the playback of the movie loops 
indefinitely.
- "duration": returns the duration of a movie, measured in milliseconds 
(maps to the native duration property on iOS). This is an integer value.
- "playableDuration": returns the amount of currently playable content, 
measured in milliseconds (maps to the native playableDuration property on iOS). 
This is an integer value.
- "playable": enough data is available to start playing, but it may run 
out before playback finishes.
- "playthrough": enough data has been buffered for playback to continue 
uninterrupted.
- "stalled": buffer of data has stalled and playback may pause 
automatically if the player runs out of data
- "playing": playback is current underway.
- "paused": playback is paused and resumes from the point it was paused.
- "interrupted": playback is temporarily interrupted, perhaps because 
the buffer ran out of content.
- "seeking forward": the player is currently seeking towards the end of 
the movie.
- "seeking backward": the player is currently seeking towards the 
beginning of the movie.





On 4/14/18, 12:47 PM, "use-livecode on behalf of Sannyasin Brahmanathaswami via 
use-livecode"  wrote:

I am using a default player in mobile.
Works fine in iOS.
But in Android is look pretty retrograde.

In particular,  it opens with a 150 px high (or something like that)  
object with the player control at the bottom.

So, I am trying to sort out mobileControlDo, to create have a native player 
and the dictionary has options of mobile control all jumbled together… That 
entry may needs some work. But one another plane with it would nice to have a 
lesson an each of the mobile controls. I looked on the web, there is old one 
multi channel sound for iOS .  that all, Perhaps I missed it?

I think I need  compile a separate document with an mobile player props. 
They are spread over MobileControlCreate, MobileControlSet, and mobileControlDo.

BR



___
use-livecode mailing list
use-live

Player Controls in Mobile

2018-04-14 Thread Sannyasin Brahmanathaswami via use-livecode
I am using a default player in mobile.
Works fine in iOS.
But in Android is look pretty retrograde.

In particular,  it opens with a 150 px high (or something like that)  object 
with the player control at the bottom.

So, I am trying to sort out mobileControlDo, to create have a native player and 
the dictionary has options of mobile control all jumbled together… That entry 
may needs some work. But one another plane with it would nice to have a lesson 
an each of the mobile controls. I looked on the web, there is old one multi 
channel sound for iOS .  that all, Perhaps I missed it?

I think I need  compile a separate document with an mobile player props. They 
are spread over MobileControlCreate, MobileControlSet, and mobileControlDo.

BR



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: On Boot - Run Time Tool vs Pointer Tool

2018-04-14 Thread Tom Glod via use-livecode
the beauty of livecode is that you can script anything the IDE is built
with Livecode, so you can change any aspect of it or script any action that
you want.

On Sat, Apr 14, 2018 at 12:33 PM, Tom Glod  wrote:

> on opencard
>
> *choose* browse tool
> end opencard
>
> On Sat, Apr 14, 2018 at 10:37 AM, Sannyasin Brahmanathaswami via
> use-livecode  wrote:
>
>> When we boot LC, I typically need to navigate, but the tool end up
>> Pointer tool.
>>
>> I am the only one who needs to change this ever time he boots?
>>
>> Can/Should be a global preference?
>>
>> BR
>>
>>
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: On Boot - Run Time Tool vs Pointer Tool

2018-04-14 Thread Tom Glod via use-livecode
on opencard

*choose* browse tool
end opencard

On Sat, Apr 14, 2018 at 10:37 AM, Sannyasin Brahmanathaswami via
use-livecode  wrote:

> When we boot LC, I typically need to navigate, but the tool end up Pointer
> tool.
>
> I am the only one who needs to change this ever time he boots?
>
> Can/Should be a global preference?
>
> BR
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


On Boot - Run Time Tool vs Pointer Tool

2018-04-14 Thread Sannyasin Brahmanathaswami via use-livecode
When we boot LC, I typically need to navigate, but the tool end up Pointer tool.

I am the only one who needs to change this ever time he boots?

Can/Should be a global preference?

BR


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Getting Orientation Enforced on Phone

2018-04-14 Thread Sannyasin Brahmanathaswami via use-livecode
BR: just completed test.

I tried "go letting"  to stack

   mobileSetAllowedOrientations "portrait,portrait upside down,landscape 
left,landscape right"
 
just before closing in and opening the next stack.  

No go an Android.

Next I wondered by the portrait turn up portrait in iOS?  Well I look like it 
did in openStack

on preOpenStack
   wait 100 milliseconds with messages
end preOpenStack
on openStack
   set the fullscreenmode of this stack to "showAll" -- better for wider screens
   mobile_SetAllowedOrientation "portrait"
   set the acceleratedRendering of this stack to true
end openStack

---

So I went to landscape then, which had it preopenstack handler, and I change it 
to openstack handler

results

iOS : It complied, go orientation landscape back to portrait BUT
complete, going to portrait to land scape. The was enforced (to landscape)
but location the background image was off !
and I have set in to image

   set the loc of img "bgImage" to the loc of this cd

Android: Did not compiled until we manually rotated and the bkground image was 
off is the name offsets and iOS.

GIT stash!  back to where I was before.

   9.0.1  

I can live with that.. hopefully sooner than later. If you don’t there soon 
I will be forced to a horrible notice 

"Please turn phone"  and end of change of stacks.



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: DataGrid Column Labels

2018-04-14 Thread Terence Heaford via use-livecode
More investigation.

Instead of using DGH to change the header label I did it manually by editing 
the groups.

This worked until a reload of the project at which point the header label had 
disappeared again.

Upon working through the header by editing the groups you eventually come to 
the text field that contains the header text.

This was empty.

Clearly something in the script of the DataGrid is emptying that field.

At this point I am giving up although if you create the headers on opening the 
project with the likes of:

set the dgProp[ "columns" ] of group  “myTable" of cd  “myCard" of stack  
“myStack" to "test"

set the dgProp[ "column labels" ] of group "myTable" of cd "myCard" of stack 
"myStack" to "TEST"


Then they do seem to stick for the duration of the project being open. I have 
placed these in open stack


All the best

Terry

> On 14 Apr 2018, at 09:03, Terence Heaford via use-livecode 
>  wrote:
> 
> When I look at the Data Grid Templates in the project browser I see 2 tables 
> that refer to DG2.
> 
> I suspect these are the culprits because these are associated with the two 
> new tables I have added to the project.
> 
> Where there problems are, I don’t know.
> 
> 
> Thanks
> 
> Terry
> 
> 
>> On 14 Apr 2018, at 08:17, Terence Heaford via use-livecode 
>>  wrote:
>> 
>> Thanks
>> 
>> Will have a look at that although the column does not have a column 
>> behaviour.
>> 
>> I have changed the properties of the header with DGH but the props listed in 
>> the Property Inspector do seem correct.
>> 
>> If I go back into DGH and click on the green tick to accept a change of 
>> margins for the header, the label again shows until the next time I restart 
>> the Stack in LiveCode
>> at which point it disappears again.
>> 
>> I can’t see what I have done to cause this errant behaviour.
>> 
>> There must be a bug somewhere but where…?
>> 
>> 
>> All the best
>> 
>> Terry
>> 
>> 
>> 
>>> On 13 Apr 2018, at 22:00, Bob Sneidar via use-livecode 
>>>  wrote:
>>> 
>>> I had a similar issue. Labels would not appear. I got the dgprop ["column 
>>> labels"] of the datagrid and they were all correct! That made me think 
>>> there is something wrong with the behavior, but other datagrids were 
>>> working fine! What I did to fix it is I got the behavior of another 
>>> datagrid that DID work, and set the behavior of the errant datagrid to the 
>>> long id of that. 
>>> 
>>> Bob S
>>> 
>>> 
 On Apr 13, 2018, at 11:52 , Terence Heaford via use-livecode 
  wrote:
 
 I have just started having an issue with the Column Labels on some newly 
 created tables.
 
 Basically they do not show unless I press “Refresh Data Grid" in the 
 Property Inspector.
 
 If I then shut down LiveCode and relaunch it they have gone missing again.
 
 I am using the community edition of LC9 in OSX 10.13.4.
 
 It is only affecting newly created DataGrids.
 
 DataGrids that have been created in previous versions seem OK.
 
 My only solution has been to overlay the DataGrid with a label.
 
 
 Is this an issue anyone else has been having or is it just me?
 
 I have been using the DGH 2.0.0 plugin if that makes a difference.
 
 
 Thanks for any pointers.
 
 
 All the best
 
 Terry
>>> 
>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: DataGrid Column Labels

2018-04-14 Thread Terence Heaford via use-livecode
When I look at the Data Grid Templates in the project browser I see 2 tables 
that refer to DG2.

I suspect these are the culprits because these are associated with the two new 
tables I have added to the project.

Where there problems are, I don’t know.


Thanks

Terry


> On 14 Apr 2018, at 08:17, Terence Heaford via use-livecode 
>  wrote:
> 
> Thanks
> 
> Will have a look at that although the column does not have a column behaviour.
> 
> I have changed the properties of the header with DGH but the props listed in 
> the Property Inspector do seem correct.
> 
> If I go back into DGH and click on the green tick to accept a change of 
> margins for the header, the label again shows until the next time I restart 
> the Stack in LiveCode
> at which point it disappears again.
> 
> I can’t see what I have done to cause this errant behaviour.
> 
> There must be a bug somewhere but where…?
> 
> 
> All the best
> 
> Terry
> 
> 
> 
>> On 13 Apr 2018, at 22:00, Bob Sneidar via use-livecode 
>>  wrote:
>> 
>> I had a similar issue. Labels would not appear. I got the dgprop ["column 
>> labels"] of the datagrid and they were all correct! That made me think there 
>> is something wrong with the behavior, but other datagrids were working fine! 
>> What I did to fix it is I got the behavior of another datagrid that DID 
>> work, and set the behavior of the errant datagrid to the long id of that. 
>> 
>> Bob S
>> 
>> 
>>> On Apr 13, 2018, at 11:52 , Terence Heaford via use-livecode 
>>>  wrote:
>>> 
>>> I have just started having an issue with the Column Labels on some newly 
>>> created tables.
>>> 
>>> Basically they do not show unless I press “Refresh Data Grid" in the 
>>> Property Inspector.
>>> 
>>> If I then shut down LiveCode and relaunch it they have gone missing again.
>>> 
>>> I am using the community edition of LC9 in OSX 10.13.4.
>>> 
>>> It is only affecting newly created DataGrids.
>>> 
>>> DataGrids that have been created in previous versions seem OK.
>>> 
>>> My only solution has been to overlay the DataGrid with a label.
>>> 
>>> 
>>> Is this an issue anyone else has been having or is it just me?
>>> 
>>> I have been using the DGH 2.0.0 plugin if that makes a difference.
>>> 
>>> 
>>> Thanks for any pointers.
>>> 
>>> 
>>> All the best
>>> 
>>> Terry
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: DataGrid Column Labels

2018-04-14 Thread Terence Heaford via use-livecode
Thanks

Will have a look at that although the column does not have a column behaviour.

I have changed the properties of the header with DGH but the props listed in 
the Property Inspector do seem correct.

If I go back into DGH and click on the green tick to accept a change of margins 
for the header, the label again shows until the next time I restart the Stack 
in LiveCode
at which point it disappears again.

I can’t see what I have done to cause this errant behaviour.

There must be a bug somewhere but where…?


All the best

Terry



> On 13 Apr 2018, at 22:00, Bob Sneidar via use-livecode 
>  wrote:
> 
> I had a similar issue. Labels would not appear. I got the dgprop ["column 
> labels"] of the datagrid and they were all correct! That made me think there 
> is something wrong with the behavior, but other datagrids were working fine! 
> What I did to fix it is I got the behavior of another datagrid that DID work, 
> and set the behavior of the errant datagrid to the long id of that. 
> 
> Bob S
> 
> 
>> On Apr 13, 2018, at 11:52 , Terence Heaford via use-livecode 
>>  wrote:
>> 
>> I have just started having an issue with the Column Labels on some newly 
>> created tables.
>> 
>> Basically they do not show unless I press “Refresh Data Grid" in the 
>> Property Inspector.
>> 
>> If I then shut down LiveCode and relaunch it they have gone missing again.
>> 
>> I am using the community edition of LC9 in OSX 10.13.4.
>> 
>> It is only affecting newly created DataGrids.
>> 
>> DataGrids that have been created in previous versions seem OK.
>> 
>> My only solution has been to overlay the DataGrid with a label.
>> 
>> 
>> Is this an issue anyone else has been having or is it just me?
>> 
>> I have been using the DGH 2.0.0 plugin if that makes a difference.
>> 
>> 
>> Thanks for any pointers.
>> 
>> 
>> All the best
>> 
>> Terry
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode