Re: [OT] Conference ticket for sale

[Jim Lambert]

Jacque & Ralph,

So sorry you won’t be attending this year’s conference.
Best wishes for a speedy recovery to Margaret.

Jim Lambert
___
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: Go Card Error Handling

[J. Landman Gay]

In HyperCard 2.2: The Book, the example handler for a "go" to a 
non-existent card checks the result and gracefully handles any failure. 
Presumably it doesn't throw an error so the stack author can manage 
navigation without interrupting the user with a dialog.


The sample handler describes a "statistics" stack where each card has 
baseball stats for a particular year. Not all years are represented. The 
handler checks the result and if the card isn't found, the handler 
answers "Sorry, there are no stats for that year."


So apparently it was done that way on purpose and assumes the stack 
author will handle failed navigation gracefully. In the case of a stack 
that HC can't find, the "go" command puts up a standard file dialog so 
the user can locate it. In the case of a non-existent card in a stack 
that is not open, the result is set to "no such card" and the 
destination stack is brought to the front.


On 6/23/2016 12:33 PM, Mark Waddingham wrote:

Hi all,

Whilst investigating a bug this afternoon
(http://quality.livecode.com/show_bug.cgi?id=17873 - which has a moral
attached to it, I'll come back to that) I was reminded that 'go card'
seems to have somewhat inconsistent error handling compared to other
commands which reference objects.

In pretty much all cases I can think of if a chunk cannot be resolved
because one of its parts does not exist, then a runtime error is thrown.
e.g.

   put the name of button "ThisButtonDoesNotExist"
   -- throws error "Chunk: no such object"

   copy char 1 to 5 of field 1 of card "ThisCardDoesNotExist"
   -- throws error "Chunk: can't find card"

However, if I do this:

   go card "ThisCardDoesNotExist"
   -- no error thrown: the result is "no such card"

In situations such as this, usually there is an apparent reason for the
difference I can point to - however in this case I struggle to think of
one. 'Going' to a card requires resolving a chunk reference, and by the
rules which are followed everywhere (?) else, and so if that chunk
reference does not resolve an error should be thrown.

I was just wondering if anyone knew why the behavior of 'go card' is
different from, well, pretty much all other commands acting on chunks...
Is it a HyperCard compatibility thing? An oversight from long ago? Is
the difference actually useful and important in any way?

I filed an anomaly about it here -
http://quality.livecode.com/show_bug.cgi?id=17901 - as it seems truly
anomalous, however, like everything else, knowing the 'why it is the way
it is' would be helpful to decide whether something should be done about
it at some point, or whether it is something which should always be the
way it currently is.

Warmest Regards,

Mark.

P.S. In regards to the original report which prompted my pondering on
'go card', then its important to remember (when processing actual
formatted text) that just because something looks like a space, it
doesn't mean it is a space - spaces and non-breaking spaces are very
different things (from the point of view of comparing strings, at least!).




--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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: Go Card Error Handling

[Dar Scott]

In "HyperCard: Script Language Guide" the "go" error message result is 
described in the context of file I/O, that is, finding the stack when there is 
a "without dialog" clause.  

> On Jun 23, 2016, at 11:33 AM, Mark Waddingham  wrote:
> 
> Hi all,
> 
> Whilst investigating a bug this afternoon 
> (http://quality.livecode.com/show_bug.cgi?id=17873 - which has a moral 
> attached to it, I'll come back to that) I was reminded that 'go card' seems 
> to have somewhat inconsistent error handling compared to other commands which 
> reference objects.
> 
> In pretty much all cases I can think of if a chunk cannot be resolved because 
> one of its parts does not exist, then a runtime error is thrown. e.g.
> 
>   put the name of button "ThisButtonDoesNotExist"
>   -- throws error "Chunk: no such object"
> 
>   copy char 1 to 5 of field 1 of card "ThisCardDoesNotExist"
>   -- throws error "Chunk: can't find card"
> 
> However, if I do this:
> 
>   go card "ThisCardDoesNotExist"
>   -- no error thrown: the result is "no such card"
> 
> In situations such as this, usually there is an apparent reason for the 
> difference I can point to - however in this case I struggle to think of one. 
> 'Going' to a card requires resolving a chunk reference, and by the rules 
> which are followed everywhere (?) else, and so if that chunk reference does 
> not resolve an error should be thrown.
> 
> I was just wondering if anyone knew why the behavior of 'go card' is 
> different from, well, pretty much all other commands acting on chunks... Is 
> it a HyperCard compatibility thing? An oversight from long ago? Is the 
> difference actually useful and important in any way?
> 
> I filed an anomaly about it here - 
> http://quality.livecode.com/show_bug.cgi?id=17901 - as it seems truly 
> anomalous, however, like everything else, knowing the 'why it is the way it 
> is' would be helpful to decide whether something should be done about it at 
> some point, or whether it is something which should always be the way it 
> currently is.
> 
> Warmest Regards,
> 
> Mark.
> 
> P.S. In regards to the original report which prompted my pondering on 'go 
> card', then its important to remember (when processing actual formatted text) 
> that just because something looks like a space, it doesn't mean it is a space 
> - spaces and non-breaking spaces are very different things (from the point of 
> view of comparing strings, at least!).
> 
> -- 
> Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps
> 
> ___
> 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

Go Card Error Handling

[Mark Waddingham]

Hi all,

Whilst investigating a bug this afternoon 
(http://quality.livecode.com/show_bug.cgi?id=17873 - which has a moral 
attached to it, I'll come back to that) I was reminded that 'go card' 
seems to have somewhat inconsistent error handling compared to other 
commands which reference objects.


In pretty much all cases I can think of if a chunk cannot be resolved 
because one of its parts does not exist, then a runtime error is thrown. 
e.g.


   put the name of button "ThisButtonDoesNotExist"
   -- throws error "Chunk: no such object"

   copy char 1 to 5 of field 1 of card "ThisCardDoesNotExist"
   -- throws error "Chunk: can't find card"

However, if I do this:

   go card "ThisCardDoesNotExist"
   -- no error thrown: the result is "no such card"

In situations such as this, usually there is an apparent reason for the 
difference I can point to - however in this case I struggle to think of 
one. 'Going' to a card requires resolving a chunk reference, and by the 
rules which are followed everywhere (?) else, and so if that chunk 
reference does not resolve an error should be thrown.


I was just wondering if anyone knew why the behavior of 'go card' is 
different from, well, pretty much all other commands acting on chunks... 
Is it a HyperCard compatibility thing? An oversight from long ago? Is 
the difference actually useful and important in any way?


I filed an anomaly about it here - 
http://quality.livecode.com/show_bug.cgi?id=17901 - as it seems truly 
anomalous, however, like everything else, knowing the 'why it is the way 
it is' would be helpful to decide whether something should be done about 
it at some point, or whether it is something which should always be the 
way it currently is.


Warmest Regards,

Mark.

P.S. In regards to the original report which prompted my pondering on 
'go card', then its important to remember (when processing actual 
formatted text) that just because something looks like a space, it 
doesn't mean it is a space - spaces and non-breaking spaces are very 
different things (from the point of view of comparing strings, at 
least!).


--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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: Right-Clicks and Double-Clicks don't work in LC8

[Mark Waddingham]

On 2016-06-23 18:46, mac...@earthlink.net wrote:

Although I’m not sure,of the exact culprit, I solved the issue by
removing all plug-ins. I’ll have to find some time one day to go
through them all to determine the offender, but in the meantime I can
actually use LC8 now! Happy Days :)


Ah! Glad you found the cause.

It sounds like one of the plugins you have is not playing nicely with 
LC8 (or LC8 is not playing nicely with it!). If you have time to go 
through and find out which one is causing the problem at some point - 
that would be great - we can then determine if it is the plugin, or the 
IDE which is at fault!


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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: Right-Clicks and Double-Clicks don't work in LC8

[MacBox]

Although I’m not sure,of the exact culprit, I solved the issue by removing all 
plug-ins. I’ll have to find some time one day to go through them all to 
determine the offender, but in the meantime I can actually use LC8 now! Happy 
Days :)



> On Jun 23, 2016, at 12:01, mac...@earthlink.net wrote:
> 
> Apologies, Mark, I apparently managed to leave out a critical piece of info; 
> this is in Edit, not Run-mode.
> 
> To be clear, double-clicking a control in Edit-mode does not open the 
> Property Inspector, and Right-Clicking does not display the PopUp menu to 
> Edit Script, show the Property Inspector, etc.
> 
> Additionally holding option-command and double-clicking does not open the 
> script editor
> 
> All these do work in older versions, and in LC8 under another user account, 
> so it must be something in my account that’s causing the issue.
> 
> 
>> Apologies, Mark, I apparently managed to leave out a critical piece of info; 
>> this is in Edit, not Run-mode.
>> 
>> To be clear, double-clicking a control in Edit-mode does not open the 
>> Property Inspector, and Right-Clicking does not display the PopUp menu to 
>> Edit Script, show the Property Inspector, etc.
>> 
>> Additionally holding option-command and double-clicking does not open the 
>> script editor
>> 
>> All these do work in older versions, and in LC8 under another user account, 
>> so it must be something in my account that’s causing the issue.
>> 
>> 
>> On Jun 23, 2016, at 11:31, mac...@earthlink.net wrote:
>> 
>>> Double-clicking on a control, and Right-Clicking a control do nothing in 
>>> LiveCode 8 in my user account (this has been true since the first DP 
>>> release). Testing on another account does work, so I tried quitting, 
>>> deleting the Livecode7.rev preference file in my account, and relaunching, 
>>> but that did not solve the issue. What other file(s) do I need to delete?
>>> 
>>> I’m currently using LC 8.0.1 build 13020 under Mac OS 10.9.5
>>> 
>>> TIA!!
>>> I'm not sure that behavior would be affected by the preferences...
>>> 
>>> I just created a stack and a button, and set the button's script to 
>>> this:
>>> 
>>> on mouseDown
>>> put the millisecs && the params & return before msg
>>> end mouseDown
>>> 
>>> on mouseDoubleDown
>>> put the millisecs && the params & return before msg
>>> end mouseDoubleDown
>>> 
>>> on mouseUp
>>> put the millisecs && the params & return before msg
>>> end mouseUp
>>> 
>>> on mouseDoubleUp
>>> put the millisecs && the params & return before msg
>>> end mouseDoubleUp
>>> 
>>> Switched to browser mode and the output of the message box when clicking 
>>> or double-clicking either the left or right button seem fine.
>>> 
>>> The engine allows to configure the 'double click interval' (the maximum 
>>> time between two clicks for it to register as a double-click) and the 
>>> 'double click delta' (the maximum distance from the first click the 
>>> mouse can move for a double-click to still register). The double click 
>>> interval is controlled by 'the doubleClickInterval' global property, and 
>>> the double click delta is controlled by 'the doubleClickDelta' global 
>>> property. The doubleClickInterval is initialized from the system default 
>>> when the engine starts up; the doubleClickDelta is by default 4 pixels.
>>> 
>>> Try doing 'put the doubleClickDelta' and 'put the doubleClickInterval' 
>>> in the message box on the user account which is broken (in this regard) 
>>> and the one that is not.
>>> 
>>> Also, whether or not the mouse recognises clicking on the right side as 
>>> a right click, there is an option in Mouse System Preferences which 
>>> allows you to configure what the 'secondary' click is. If you turn off 
>>> 'secondary click', then you have to use Ctrl-Click to get a Right-Click 
>>> - this setting is per user account so it might be worth checking that 
>>> too.
>>> 
>>> Warmest Regards,
>>> 
>>> Mark.
>>> 
>>> -- 
>>> Mark Waddingham ~ mark at livecode.com ~ http://www.livecode.com/
>>> LiveCode: Everyone can create apps
>> 
> 
___
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: Right-Clicks and Double-Clicks don't work in LC8

[MacBox]

Apologies, Mark, I apparently managed to leave out a critical piece of info; 
this is in Edit, not Run-mode.

To be clear, double-clicking a control in Edit-mode does not open the Property 
Inspector, and Right-Clicking does not display the PopUp menu to Edit Script, 
show the Property Inspector, etc.

Additionally holding option-command and double-clicking does not open the 
script editor

All these do work in older versions, and in LC8 under another user account, so 
it must be something in my account that’s causing the issue.


On Jun 23, 2016, at 11:31, mac...@earthlink.net wrote:

> Double-clicking on a control, and Right-Clicking a control do nothing in 
> LiveCode 8 in my user account (this has been true since the first DP 
> release). Testing on another account does work, so I tried quitting, deleting 
> the Livecode7.rev preference file in my account, and relaunching, but that 
> did not solve the issue. What other file(s) do I need to delete?
> 
> I’m currently using LC 8.0.1 build 13020 under Mac OS 10.9.5
> 
> TIA!!
> I'm not sure that behavior would be affected by the preferences...
> 
> I just created a stack and a button, and set the button's script to 
> this:
> 
> on mouseDown
> put the millisecs && the params & return before msg
> end mouseDown
> 
> on mouseDoubleDown
> put the millisecs && the params & return before msg
> end mouseDoubleDown
> 
> on mouseUp
> put the millisecs && the params & return before msg
> end mouseUp
> 
> on mouseDoubleUp
> put the millisecs && the params & return before msg
> end mouseDoubleUp
> 
> Switched to browser mode and the output of the message box when clicking 
> or double-clicking either the left or right button seem fine.
> 
> The engine allows to configure the 'double click interval' (the maximum 
> time between two clicks for it to register as a double-click) and the 
> 'double click delta' (the maximum distance from the first click the 
> mouse can move for a double-click to still register). The double click 
> interval is controlled by 'the doubleClickInterval' global property, and 
> the double click delta is controlled by 'the doubleClickDelta' global 
> property. The doubleClickInterval is initialized from the system default 
> when the engine starts up; the doubleClickDelta is by default 4 pixels.
> 
> Try doing 'put the doubleClickDelta' and 'put the doubleClickInterval' 
> in the message box on the user account which is broken (in this regard) 
> and the one that is not.
> 
> Also, whether or not the mouse recognises clicking on the right side as 
> a right click, there is an option in Mouse System Preferences which 
> allows you to configure what the 'secondary' click is. If you turn off 
> 'secondary click', then you have to use Ctrl-Click to get a Right-Click 
> - this setting is per user account so it might be worth checking that 
> too.
> 
> Warmest Regards,
> 
> Mark.
> 
> -- 
> Mark Waddingham ~ mark at livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps

___
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: Right-Clicks and Double-Clicks don't work in LC8

[Mark Waddingham]

On 2016-06-23 17:31, mac...@earthlink.net wrote:

Double-clicking on a control, and Right-Clicking a control do nothing
in LiveCode 8 in my user account (this has been true since the first
DP release). Testing on another account does work, so I tried
quitting, deleting the Livecode7.rev preference file in my account,
and relaunching, but that did not solve the issue. What other file(s)
do I need to delete?


I'm not sure that behavior would be affected by the preferences...

I just created a stack and a button, and set the button's script to 
this:


on mouseDown
   put the millisecs && the params & return before msg
end mouseDown

on mouseDoubleDown
   put the millisecs && the params & return before msg
end mouseDoubleDown

on mouseUp
   put the millisecs && the params & return before msg
end mouseUp

on mouseDoubleUp
   put the millisecs && the params & return before msg
end mouseDoubleUp

Switched to browser mode and the output of the message box when clicking 
or double-clicking either the left or right button seem fine.


The engine allows to configure the 'double click interval' (the maximum 
time between two clicks for it to register as a double-click) and the 
'double click delta' (the maximum distance from the first click the 
mouse can move for a double-click to still register). The double click 
interval is controlled by 'the doubleClickInterval' global property, and 
the double click delta is controlled by 'the doubleClickDelta' global 
property. The doubleClickInterval is initialized from the system default 
when the engine starts up; the doubleClickDelta is by default 4 pixels.


Try doing 'put the doubleClickDelta' and 'put the doubleClickInterval' 
in the message box on the user account which is broken (in this regard) 
and the one that is not.


Also, whether or not the mouse recognises clicking on the right side as 
a right click, there is an option in Mouse System Preferences which 
allows you to configure what the 'secondary' click is. If you turn off 
'secondary click', then you have to use Ctrl-Click to get a Right-Click 
- this setting is per user account so it might be worth checking that 
too.


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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: multiple field selection bug?

[Devin Asay]

> On Jun 23, 2016, at 7:21 AM, andrew  wrote:
> 
> Trying to decide if this is a "bug" or "feature", but it keeps pissing me off 
> so
> I would like file it under the former.
> 
> If I have the Property Inspector open to the Text tab and select multiple 
> field
> objects, the textAlign of the last selected object gets applied to every 
> object
> selected. I call this a bug, because the similar behavior is not applied to
> other properties like textSize or textFont.
> 
> If the selected objects have different values, that value is blank in the
> Property Inspector and each object retains it's original property value. When 
> I
> manually change that value (like size or style), it is then applied to every
> selected object (as expected). Except with textAlign, which is automatically
> changed (but ONLY when the Text tab is active in Property Inspector, not when
> any other tab is active). Seems like textAlign should behave like the other
> properties.

Agreed. It’s a bug. What version are you using? Have you reported it?

I’m actually seeing something slightly different, in 8.1.0.

1. Create several field objects with text in them.

2. Set the alignment of the various fields to different values.

3. Ensure one of the fields is selected and the property inspector is open to 
the Text tab.

4. Shift click the other fields to select them.

5. All of the text alignments change to left aligned.

This only happens if the selected fields are not all set to the same alignment. 
If they are all set to the same alignment, regardless of what it is, they all 
retain their alignment when selected together. If just one of the selected 
fields has an alignment that differs from the already-selected ones, all of the 
selected fields change to left aligned.

Andrew, if you have reported it, I’ll add my observations. If you haven’t I’ll 
report it.

Regards,

Devin

Devin Asay
Office of Digital Humanities
Brigham Young University

___
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

Right-Clicks and Double-Clicks don't work in LC8

[MacBox]

Double-clicking on a control, and Right-Clicking a control do nothing in 
LiveCode 8 in my user account (this has been true since the first DP release). 
Testing on another account does work, so I tried quitting, deleting the 
Livecode7.rev preference file in my account, and relaunching, but that did not 
solve the issue. What other file(s) do I need to delete?

I’m currently using LC 8.0.1 build 13020 under Mac OS 10.9.5

TIA!!
___
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

multiple field selection bug?

[andrew]

Trying to decide if this is a "bug" or "feature", but it keeps pissing me off so
I would like file it under the former.
 
If I have the Property Inspector open to the Text tab and select multiple field
objects, the textAlign of the last selected object gets applied to every object
selected. I call this a bug, because the similar behavior is not applied to
other properties like textSize or textFont.
 
If the selected objects have different values, that value is blank in the
Property Inspector and each object retains it's original property value. When I
manually change that value (like size or style), it is then applied to every
selected object (as expected). Except with textAlign, which is automatically
changed (but ONLY when the Text tab is active in Property Inspector, not when
any other tab is active). Seems like textAlign should behave like the other
properties.
 
--Andrew Bell
___
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: [OT?] the "compass" course in LC's ABC

[Mike Bonner]

I like the fact that things that would probably be complicated with other
languages are simple with livecode.   Not everything by any means, the
number of libraries/extensions etc for other languages dwarf livecode so
far. But livecode builder is a huge step towards opening the 3rd party
door.  I"m seriously hoping for things like a simple webserver in a widget
(or library) hopefully in its own thread (but that can "message" lc,
praying for the promised box2d... In its current state, livecode has made
it possible for me to do pretty much everything I've set my mind to.  The
only real limits have been ME.  (lack of math, or lack of ability to
understand the problem to be solved, but livecode is helping me get better
at both of those things)

On Thu, Jun 23, 2016 at 12:26 AM, Richmond 
wrote:

>
>
> On 23.06.2016 08:50, Nicolas Cueto wrote:
>
>> Apologies should this come off as off-topic.
>>
>> It's about LC's App-Building Course.
>>
>> First, the OT but GREAT news. Using as-is the course's "directional
>> compass
>> + horizontal-level" stack, it was possible for even me to build, email and
>> install an Android apk to both a Nexus 5 and a Nexus 7. {That success
>> alone
>> is worth the price of the course. Well done LC!}
>>
>> Next, the NOT SO GREAT (hopefully on-topic) news. The app functioned very
>> sluggish. Enough so that the north-indicator was never correct, and a
>> "wait
>> or kill?" message window repeatedly appeared. Also, the swipe action to
>> switch between compass and level functions did not work at all.
>>
>> Anyway, as someone very new to using LC for building Android apps, I am
>> posting here (the course has a message area, but the message I entered
>> there did not appear) to get feedback from those of you with experience
>> building and specially selling LC-built Android (iOS?) apps for
>> non-private
>> use (i.e., for demanding customers)
>>
>> First, is LC limited to building "simple" apps?
>>
>
> No: most definitely not!
>
> Don't know exactly what
>> that would be text-only stuff? ... not stuff which uses device sensors
>> or processes complex mathematics?
>>
>
> I am quite sure that Livecode can be used for all the tasks one can
> use languages such as C++ and C# for.
>
> This is NOT off-topic; it is a question that seems to come up again and
> again,
> and Livecode should do a spot more in their publicity to show what very
> complicated
> stuff can be made.
>
>
>> Second, what could be slowing things down in this specific instance?
>>
>> And third, why might the swipe action not be working?
>>
>> I realize that without access to the stack itself, answering these might
>> be
>> difficult if not impossible. Nevertheless, here I am, hoping someone might
>> be able to provide advice in the right direction, even if it's not exactly
>> true North.
>>
>> Thank you.
>>
>> (And, once again, a hearty よくできました to LC for the ABC.)
>>
>> --
>> Nicolas Cueto
>> ___
>> 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
>>
> Richmond.
>
>
> ___
> 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: [OT?] the "compass" course in LC's ABC

[Richmond]

On 23.06.2016 08:50, Nicolas Cueto wrote:

Apologies should this come off as off-topic.

It's about LC's App-Building Course.

First, the OT but GREAT news. Using as-is the course's "directional compass
+ horizontal-level" stack, it was possible for even me to build, email and
install an Android apk to both a Nexus 5 and a Nexus 7. {That success alone
is worth the price of the course. Well done LC!}

Next, the NOT SO GREAT (hopefully on-topic) news. The app functioned very
sluggish. Enough so that the north-indicator was never correct, and a "wait
or kill?" message window repeatedly appeared. Also, the swipe action to
switch between compass and level functions did not work at all.

Anyway, as someone very new to using LC for building Android apps, I am
posting here (the course has a message area, but the message I entered
there did not appear) to get feedback from those of you with experience
building and specially selling LC-built Android (iOS?) apps for non-private
use (i.e., for demanding customers)

First, is LC limited to building "simple" apps?


No: most definitely not!


Don't know exactly what
that would be text-only stuff? ... not stuff which uses device sensors
or processes complex mathematics?


I am quite sure that Livecode can be used for all the tasks one can
use languages such as C++ and C# for.

This is NOT off-topic; it is a question that seems to come up again and 
again,
and Livecode should do a spot more in their publicity to show what very 
complicated

stuff can be made.



Second, what could be slowing things down in this specific instance?

And third, why might the swipe action not be working?

I realize that without access to the stack itself, answering these might be
difficult if not impossible. Nevertheless, here I am, hoping someone might
be able to provide advice in the right direction, even if it's not exactly
true North.

Thank you.

(And, once again, a hearty よくできました to LC for the ABC.)

--
Nicolas Cueto
___
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

Richmond.

___
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