Re: serial speed

[Richmond via use-livecode]

Well, in spite of appearing to logroll hereabouts, my initial point 
should not be overlooked:


"As someone who is engaged on a long, drawn-out refactoring on my main 
codebase;
a process that involves uncovering old code (max 9 years) that ranges 
from 'slightly clunky'
to 'utter crap' I have NO sympathy with phrases such as "when the code 
was written" when

relating to something that is extremely antiquated. "

While embryos in the womb may have to rehearse their evolutionary path,
LiveCode should not have to, and it would be greatly improved were its
appendix and other evolutionary left-overs excised
or replaced by something up-to-date.

Richmond.

On 4.05.19 0:07, Mark Wieder via use-livecode wrote:

On 5/3/19 10:38 AM, Richmond via use-livecode wrote:

Err: slightly wooden after a long day at work . . .

Richmond.

On 3.05.19 20:26, Mark Wieder via use-livecode wrote:

On 5/3/19 10:06 AM, Richmond via use-livecode wrote:


As someone who is engaged on a log


!!!


Must have been lumbering along all day.
Now you're bored stiff.



___
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: How big is a nanosecond?

[Stephen Barncard via use-livecode]

I love this woman.
--
Stephen Barncard - Sebastopol Ca. USA -
mixstream.org


On Fri, May 3, 2019 at 6:47 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> https://www.youtube.com/watch?v=JEpsKnWZrJ8
>
> --
>   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
>
___
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

How big is a nanosecond?

[Mark Wieder via use-livecode]

https://www.youtube.com/watch?v=JEpsKnWZrJ8

--
 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: serial speed

[runrevlist--- via use-livecode]

Hi Mark,

Thanks for the quick reply. It kind of sounds promising. 

I am on Mac so apparently I got obstructed by some old ‘artificial’ limit of 
old days. 

Can this 'simple engine patch’ you mention be implemented and ….preferably 
soon. It would really give LC a world of possibilities, think Internet of 
Things. The young ones could be using the modern lego with LC for instance. 
That would be really great. Using modem speeds in this age of 5G is kind of 
ridiculous. 

I wil certainly try your suggestion with stty shell command. I have never 
dabbled with shell in the context with LC. If you have some more hints they 
would be very welcome indeed. 

Thanks,
   Claudi



> On 03 May 2019, at 17:36, Mark Waddingham via use-livecode 
>  wrote:
> 
> On 2019-05-03 17:01, runrevlist--- via use-livecode wrote:
>> LC is ver well suited for all kinds of programs communicating with
>> robots, 3D printers, milling machines etc. if only we could have a
>> decent speed. I am not even asking for the preferred speed of 22…..
>> The arduino IDE can easily communicate at that speed, why not LC?
> 
> Which platform are you using?
> 
> On Windows, any limit in baudrate is determined by Win32: the 
> serialControlString
> property is passed to the 'BuildCommDCBW' Win32 API function to parse (which 
> doesn't
> explicitly mention a baudrate limit).
> 
> On Mac/Linux, however, there is an 'artificial' limit - the engine parses the 
> control
> string itself in those cases and maps the integer baudrate value to a system 
> constant...
> 
> So the reason it is limited to 57600 baud will be because when that code was 
> written, the only constants which were defined by the system were those up to 
> 57600 baud (it would appear at least.
> 
> This would need a (simple) engine patch to enable speeds up to the ones which 
> are defined (on macOS there are constants up to 230400, Linux has a few 
> higher ones defined too) when using 'the serialControlString' property.
> 
>> Does any one have a solution or idea how to increase this silly speed
>> limit of LC?
> 
> Alternatively, you might be able to open the serial device from LC as you do 
> now and then use the 'stty' shell command to tweak the settings:
> 
>   stty -F /dev/tty... 
> 
> Here  is one which is known by the system. For Linux this appears 
> to be a reasonably normative list 
> 
>  (although a baudrate being there doesn't mean the device supports it).
> 
> 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


___
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: serial speed

[Mark Wieder via use-livecode]

On 5/3/19 10:38 AM, Richmond via use-livecode wrote:

Err: slightly wooden after a long day at work . . .

Richmond.

On 3.05.19 20:26, Mark Wieder via use-livecode wrote:

On 5/3/19 10:06 AM, Richmond via use-livecode wrote:


As someone who is engaged on a log


!!!


Must have been lumbering along all day.
Now you're bored stiff.

--
 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: Is Anyone using the XPDFViewer?

[Matthias Rebbe via use-livecode]

Thanks Paul,

for whatever reason it still does not work. I´ve found a sample stack 
XPDF.livecode in the Livecode bundle in 
LiveCode Business 9.0.4 (rc 2).app/Contents/Tools/Ext/XPDF-1.0.31

The sample stack works, so it´s my code and i might be missing something.
Unfortunately the script of the sample stack is very detailed, but anyway it´s 
working and i just have to dig through the sample script to see how it is 
correctly done.

Regards,

Matthias Rebbe

> Am 03.05.2019 um 19:50 schrieb Paul Dupuis via use-livecode 
> :
> 
> I looked at my working code.
> 
> Every where I set the rect, I do so by:
> 
>   XPDFViewer_Set "pdfViewer","RECT", rect of grc "pdfRect" of grp "pdfViewer" 
> of me
> 
> where the graphic "pdfRect is a rectangle that is used to to map the area the 
> pdf viewer appears in.
> 
> Try creating a graphic called whatever you want. Set the rect of it to 
> 100,100,500,500 and then
> 
> XPDFViewer_Set "pdfviewer", "rect", rect of graphic 
> 
> 
> 
> 
> On 5/3/2019 1:39 PM, Matthias Rebbe via use-livecode wrote:
>> Hi,
>> 
>> i am using the following script to open a selected PDF file in the xpdf 
>> viewer, but  i am not successful.
>> 
>> answer file "PDF..."
>> 
>> if it is empty then exit top
>> 
>> put it into tFilename
>> 
>> XPDFViewer_Open "pdfviewer", the windowID of this stack
>> 
>> XPDFViewer_Set "pdfviewer", "filename",tFilename
>> 
>> XPDFViewer_Set "pdfviewer", "rect", (100,100,500,500)
>> 
>> XPDFViewer_Set "pdfviewer", "visible", TRUE
>> 
>> put xpdfviewer_Get("pdfviewer","rect")
>> 
>> 
>> The PDF viewer does not show up and the function pxdfviewer_get gives 
>> 0,0,0,0 back for the rect.
>> 
>> Is there something wrong with my script?
>> Or does anyone have working sample stack?
>> 
>> Regards,
>> 
>> Matthias Rebbe
>> 
>> ___
>> 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: Android needs 64 bit builds

[Ralph DiMola via use-livecode]

You can have more than one apk in production as long as they target different 
devices. In LCs case that would be 4 apks one for each architecture. The apk 
for the user's device will be automatically selected when installing from 
PlayStore. The size decrease comes from building 4 apks. Each of the 4 apks 
supports 1 architecture instead of 1 huge apk with all 4 engines. If you build 
1 large apk then you can limit the devices your app is compatible with. I use 
the signing and does not create anymore work. It seems to be transparent.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of 
JJS via use-livecode
Sent: Friday, May 03, 2019 1:46 PM
To: Richmond via use-livecode
Cc: JJS
Subject: Re: Android needs 64 bit builds

@Monte. I only see Atom x64 ARM for Android 7.1.1 in the SDK list in Android 
Studio. For all the higher Android versions i only see x86 and no ARM. I don't 
know if there are phones sold which have Android 8.x.x based on ARMx64. Do you 
know any details?

@Ralph, i did not see that (the different builds) yet in the Play Developer 
Console. Or is it only available when you use the signing which is offered by 
Google? (upload and download there signature
etcetera) It is also where your APK can be decreased in size, but i don't think 
it is for builds outside Android Studio? Any experience with that?


Thanks,

Jerry


Op 3-5-2019 om 08:01 schreef Richmond via use-livecode:
> Time to dust off my Intel chip Android tablet
>
> Richmond.
>
> On 3.05.19 г. 1:38 ч., Monte Goulding via use-livecode wrote:
>>
>>> On 3 May 2019, at 4:07 am, J. Landman Gay via use-livecode 
>>>  wrote:
>>>
>>> Wow. X86 too! Now we can use the faster emulator. :)
>> Yes that was the main reason for us doing x86 and x86_64 although 
>> there are some devices available for those architectures they aren’t 
>> very common so you probably only want to build for arm7 and arm64 
>> when releasing to avoid bloating your app too much.
>>
>> To make things simpler the Test button for android will detect the 
>> architecture of the target device/emulator and build just for that 
>> even if you don’t currently have it selected in the standalone builder.
>>
>> Cheers
>>
>> Monte
>> ___
>> 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: Is Anyone using the XPDFViewer?

[Paul Dupuis via use-livecode]

I looked at my working code.

Every where I set the rect, I do so by:

  XPDFViewer_Set "pdfViewer","RECT", rect of grc "pdfRect" of grp 
"pdfViewer" of me


where the graphic "pdfRect is a rectangle that is used to to map the 
area the pdf viewer appears in.


Try creating a graphic called whatever you want. Set the rect of it to 
100,100,500,500 and then


XPDFViewer_Set "pdfviewer", "rect", rect of graphic 




On 5/3/2019 1:39 PM, Matthias Rebbe via use-livecode wrote:

Hi,

i am using the following script to open a selected PDF file in the xpdf viewer, 
but  i am not successful.

answer file "PDF..."

if it is empty then exit top

put it into tFilename

XPDFViewer_Open "pdfviewer", the windowID of this stack

XPDFViewer_Set "pdfviewer", "filename",tFilename

XPDFViewer_Set "pdfviewer", "rect", (100,100,500,500)

XPDFViewer_Set "pdfviewer", "visible", TRUE

put xpdfviewer_Get("pdfviewer","rect")


The PDF viewer does not show up and the function pxdfviewer_get gives 0,0,0,0 
back for the rect.

Is there something wrong with my script?
Or does anyone have working sample stack?

Regards,

Matthias Rebbe

___
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: Android needs 64 bit builds

[JJS via use-livecode]

@Monte. I only see Atom x64 ARM for Android 7.1.1 in the SDK list in 
Android Studio. For all the higher Android versions i only see x86 and 
no ARM. I don't know if there are phones sold which have Android 8.x.x 
based on ARMx64. Do you know any details?


@Ralph, i did not see that (the different builds) yet in the Play 
Developer Console. Or is it only available when you use the signing 
which is offered by Google? (upload and download there signature 
etcetera) It is also where your APK can be decreased in size, but i 
don't think it is for builds outside Android Studio? Any experience with 
that?



Thanks,

Jerry


Op 3-5-2019 om 08:01 schreef Richmond via use-livecode:

Time to dust off my Intel chip Android tablet

Richmond.

On 3.05.19 г. 1:38 ч., Monte Goulding via use-livecode wrote:


On 3 May 2019, at 4:07 am, J. Landman Gay via use-livecode 
 wrote:


Wow. X86 too! Now we can use the faster emulator. :)
Yes that was the main reason for us doing x86 and x86_64 although 
there are some devices available for those architectures they aren’t 
very common so you probably only want to build for arm7 and arm64 
when releasing to avoid bloating your app too much.


To make things simpler the Test button for android will detect the 
architecture of the target device/emulator and build just for that 
even if you don’t currently have it selected in the standalone builder.


Cheers

Monte
___
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

Is Anyone using the XPDFViewer?

[Matthias Rebbe via use-livecode]

Hi,

i am using the following script to open a selected PDF file in the xpdf viewer, 
but  i am not successful.

answer file "PDF..."

if it is empty then exit top

put it into tFilename

XPDFViewer_Open "pdfviewer", the windowID of this stack

XPDFViewer_Set "pdfviewer", "filename",tFilename

XPDFViewer_Set "pdfviewer", "rect", (100,100,500,500)

XPDFViewer_Set "pdfviewer", "visible", TRUE

put xpdfviewer_Get("pdfviewer","rect")


The PDF viewer does not show up and the function pxdfviewer_get gives 0,0,0,0 
back for the rect.

Is there something wrong with my script?
Or does anyone have working sample stack?

Regards,

Matthias Rebbe

___
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: serial speed

[Richmond via use-livecode]

Err: slightly wooden after a long day at work . . .

Richmond.

On 3.05.19 20:26, Mark Wieder via use-livecode wrote:

On 5/3/19 10:06 AM, Richmond via use-livecode wrote:


As someone who is engaged on a log


!!!




___
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: serial speed

[Mark Wieder via use-livecode]

On 5/3/19 10:06 AM, Richmond via use-livecode wrote:


As someone who is engaged on a log


!!!

--
 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: [ANN] Release 9.0.4 RC-3

[Sannyasin Brahmanathaswami via use-livecode]

I took the release notes at "face value" and they did not include iOS 12.2

But, I tried it. It works! 

(aside)... I been doing testing an Android and rarely plug in my iPhone, 
because of the long build time and also  due the debacle Apple created using a 
dongle to Mac Pro...my powered USB hub does not work either through the 
dongle...sheesh 
 
BR

Ralph DiMola 
Great! Glad you got that resolved.

___
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: serial speed

[Richmond via use-livecode]

"when that code was written"

As someone who is engaged on a log, drawn-out refactoring on my main 
codebase;
a process that involves uncovering old code (max 9 years) that ranges 
from 'slightly clunky'
to 'utter crap' I have NO sympathy with phrases such as "when the code 
was written" when

relating to something that is extremely antiquated.

I have a list as long as your arm of new features I'd like to implement in
my Devawriter Pro: but they will just have to wait until I have cleaned 
out the attic, the cellar,

and re-papered the walls and repainted the dadoes in the main rooms . . .

Richmond.

On 3.05.19 18:36, Mark Waddingham via use-livecode wrote:

On 2019-05-03 17:01, runrevlist--- via use-livecode wrote:

LC is ver well suited for all kinds of programs communicating with
robots, 3D printers, milling machines etc. if only we could have a
decent speed. I am not even asking for the preferred speed of 22…..
The arduino IDE can easily communicate at that speed, why not LC?


Which platform are you using?

On Windows, any limit in baudrate is determined by Win32: the 
serialControlString
property is passed to the 'BuildCommDCBW' Win32 API function to parse 
(which doesn't

explicitly mention a baudrate limit).

On Mac/Linux, however, there is an 'artificial' limit - the engine 
parses the control
string itself in those cases and maps the integer baudrate value to a 
system constant...


So the reason it is limited to 57600 baud will be because when that 
code was written, the only constants which were defined by the system 
were those up to 57600 baud (it would appear at least.


This would need a (simple) engine patch to enable speeds up to the 
ones which are defined (on macOS there are constants up to 230400, 
Linux has a few higher ones defined too) when using 'the 
serialControlString' property.



Does any one have a solution or idea how to increase this silly speed
limit of LC?


Alternatively, you might be able to open the serial device from LC as 
you do now and then use the 'stty' shell command to tweak the settings:


   stty -F /dev/tty... 

Here  is one which is known by the system. For Linux this 
appears to be a reasonably normative list 
 
(although a baudrate being there doesn't mean the device supports it).


Warmest Regards,

Mark.




___
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: serial speed

[Mark Waddingham via use-livecode]

On 2019-05-03 17:01, runrevlist--- via use-livecode wrote:

LC is ver well suited for all kinds of programs communicating with
robots, 3D printers, milling machines etc. if only we could have a
decent speed. I am not even asking for the preferred speed of 22…..
The arduino IDE can easily communicate at that speed, why not LC?


Which platform are you using?

On Windows, any limit in baudrate is determined by Win32: the 
serialControlString
property is passed to the 'BuildCommDCBW' Win32 API function to parse 
(which doesn't

explicitly mention a baudrate limit).

On Mac/Linux, however, there is an 'artificial' limit - the engine 
parses the control
string itself in those cases and maps the integer baudrate value to a 
system constant...


So the reason it is limited to 57600 baud will be because when that code 
was written, the only constants which were defined by the system were 
those up to 57600 baud (it would appear at least.


This would need a (simple) engine patch to enable speeds up to the ones 
which are defined (on macOS there are constants up to 230400, Linux has 
a few higher ones defined too) when using 'the serialControlString' 
property.



Does any one have a solution or idea how to increase this silly speed
limit of LC?


Alternatively, you might be able to open the serial device from LC as 
you do now and then use the 'stty' shell command to tweak the settings:


   stty -F /dev/tty... 

Here  is one which is known by the system. For Linux this 
appears to be a reasonably normative list 
 
(although a baudrate being there doesn't mean the device supports it).


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: mobilePickPhoto on Android

[Dan Friedman via use-livecode]

Panos,

Here’s an update…  I met in person with my client with his Samsung Galaxy S9+ 
running Android 9.  My standalone built with 9.0.4 rc3 is failing on his 
device.  I call mobilePickPhoto "camera", and the camera does come up.  I take 
the picture, the screen flashes, and then the camera is ready to take another 
photo.  The photos are being added to his photo library.  It doesn’t return to 
the app.  If I cancel the camera, it returns to the app and I get “cancel” as 
the result.  There must be something different about this particular device.  
Do you have any insight or things I might try?

Anyone out there with a Samsung Galaxy S9+ running Android 9 that can confirm 
mobilePickPhoto is or isn’t working?

-Dan


From: Dan Friedman 
Date: Tuesday, April 30, 2019 at 10:26 AM
To: panagiotis merakos , How to use LiveCode 

Subject: Re: mobilePickPhoto on Android

Panos,

Thank you for the reply.  This version fixed the issue on several of our 
devices.   However, my client is saying it’s failing on his Samsung Galaxy S9+ 
running Android 9.  I have verified that he has the updated build (made with LC 
9.0.4 rc 2) installed on his device.   He says he has made no software or 
hardware modifications to the device but is still having the same issue.  
Perhaps there is a different issue with camera access with this device?

-Dan



From: panagiotis merakos 
Date: Tuesday, April 30, 2019 at 4:04 AM
To: How to use LiveCode 
Cc: Dan Friedman 
Subject: Re: mobilePickPhoto on Android

Hello Dan,

This sounds like https://quality.livecode.com/show_bug.cgi?id=21826, affecting 
only specific Android devices, and has been fixed in LC 9.0.4 RC-1+

Kind regards,
Panos
--

On Sat, 27 Apr 2019 at 01:09, Dan Friedman via use-livecode 
mailto:use-livecode@lists.runrev.com>> wrote:
Greetings!I am calling mobilePickPhoto "camera" on a Android device.   If I 
am running Android version 7.0, everything works great.   If I am running 
Android 8.0, then I get an empty back where length(image 1) is 0.   Using 
LiveCode 9.0.3.   Anyone know of an issue with mobilePickPhoto on late versions 
of Android.   FWIW, mobilePickPhoto "library" works fine on all versions of 
Android.

Thanks in advance,
-Dan

___
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

serial speed

[runrevlist--- via use-livecode]

Quite a few years ago I got the connection between LC and arduino properly 
working. Unfortunately, then the highest speed LC was capable of was 57600 
Baud. 
Besides 3D printing, I developed quite a big delta printer, I am now also into 
laser engraving and of course I printed all the parts to create one myself. I 
have now written a LC program to generate g-Code from foto’s. That is all 
working quite well.
LC is such a wonderfull tool. Unfortunately, universal gCode sender, a open 
source tool written in java chokes on big images. So I want to write my own 
g-Code sender, which isn’t that hard to do, except for one absolutely  crucial 
detail. 
The serial speed. I had hoped that by now, about 10 years later LC would be 
able to use a serial speed of at least 115200 Baud. But allas. LC still can’t 
communicate at that speed, which is an absolute deal breaker. It is incredible 
that LC can’t communicate with the outside world with something resembling a 
reasonable speed. 

LC is ver well suited for all kinds of programs communicating with robots, 3D 
printers, milling machines etc. if only we could have a decent speed. I am not 
even asking for the preferred speed of 22….. The arduino IDE can easily 
communicate at that speed, why not LC?

Does any one have a solution or idea how to increase this silly speed limit of 
LC?
I really need this tool and LC id the perfect choice to write it in a very 
short time, but as it is now, it’s a no go.

Any advice is greatly appreciated.

Claudi Cornaz
___
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