Announcement: SVG Icon Tool

[Brian Milby via use-livecode]

I've posted an updated version of my SVG Icon Tool to my server with a
large number of icons included (everything from
https://leungwensen.github.io/svg-icon except the flags which needed
color).  I've also included the feather icons that were mentioned.

Direct link to the download:
https://milby.us/lc/SvgIconTool.180113-2301.zip

Latest forum post on the tool:
http://forums.livecode.com/viewtopic.php?f=10&t=30411&p=162655#p162655

Once the SVG Icon Library is updated to allow loading other icon families,
this tool can be used to help manage icon sets for applications.  There
should be no reason the LCB file in my PR couldn't be compiled in LC8, but
I've been working on it in LC9DP11 & develop.
It exports encoded LC arrays that are in the format needed for the library.

Thanks,
Brian
___
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 build executable on test device fails

[Nicolas Cueto via use-livecode]

And now a new problem. The SDK and JDK paths have disappeared.

Just now installed 8.0.2, pointed it to the SDK root path that worked with
8.1.8, but got the error "chosen folder not a valid Android SDK".

And, opening 8.1.8 to confirm the SDK rooth path, the SDK field there has
become blank and the JDK path has returned to "(none)".

Why?!?  Argh!!!

--
Nicolas Cueto


On 14 January 2018 at 09:43, MWCM via use-livecode <
use-livecode@lists.runrev.com> wrote:

>
> > Date: Sun, 14 Jan 2018 09:15:48 +0900
> > From: Nicolas Cueto 
> > To: How to use LiveCode 
> > Subject: Re: Android build executable on test device fails
> > Message-ID:
> >
> > Content-Type: text/plain; charset="UTF-8"
> >
> > The problem is on 8.1.8.
> >
> > Any idea what the subject of that thread was?
> >
>
> I was hoping I would be able to get something useful as I had a similar
> problem but the user found the problem object on their own.
>
> http://lists.runrev.com/pipermail/use-livecode/2018-January/244253.html
>
> --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
>
___
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 build executable on test device fails

[MWCM via use-livecode]

> Date: Sun, 14 Jan 2018 09:15:48 +0900
> From: Nicolas Cueto 
> To: How to use LiveCode 
> Subject: Re: Android build executable on test device fails
> Message-ID:
>
> Content-Type: text/plain; charset="UTF-8"
> 
> The problem is on 8.1.8.
> 
> Any idea what the subject of that thread was?
> 

I was hoping I would be able to get something useful as I had a similar problem 
but the user found the problem object on their own. 

http://lists.runrev.com/pipermail/use-livecode/2018-January/244253.html

--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: Android build executable on test device fails

[Nicolas Cueto via use-livecode]

Found the thread ("Error while saving standalone 8 & 9"), and, yes, widget
problem. But my stack is simply a field and two buttons. No widgets.

So, still stuck.

--
Nicolas Cueto

On 14 January 2018 at 09:15, Nicolas Cueto  wrote:

> The problem is on 8.1.8.
>
> Any idea what the subject of that thread was?
>
> --
> Nicolas Cueto
>
> On 13 January 2018 at 20:15, MWCM via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>>
>> > Testing on an Android device, the "Standalone builder progress" window
>> > shows first "Building classes" and then for a brief moment "Building
>> > executable", after which an error window reads "Unable to build app for
>> > testing: could not open module file".
>> >
>> > Searched the forums but no mention at all of this problem.
>> >
>> > --
>> > Nicolas Cueto
>> >
>>
>> Someone else on the list had this problem within the week, but had a
>> different subject for the thread. I believe their issue was some code or
>> widget lurking around without proper inclusions.
>>
>> What version of Livecode are you compiling with? I’ve had the same
>> problem recently with a stack that I’ve tried to compiler in 8.1.8. I fear
>> I opened this in 9dp11 to see the new dataGrid2 in action and saved the
>> stack without backwards compatibility. This isn’t strictly Android as I was
>> building for iOS when the error manifested.
>>
>> —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
>
>
>
___
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 build executable on test device fails

[Nicolas Cueto via use-livecode]

The problem is on 8.1.8.

Any idea what the subject of that thread was?

--
Nicolas Cueto

On 13 January 2018 at 20:15, MWCM via use-livecode <
use-livecode@lists.runrev.com> wrote:

>
> > Testing on an Android device, the "Standalone builder progress" window
> > shows first "Building classes" and then for a brief moment "Building
> > executable", after which an error window reads "Unable to build app for
> > testing: could not open module file".
> >
> > Searched the forums but no mention at all of this problem.
> >
> > --
> > Nicolas Cueto
> >
>
> Someone else on the list had this problem within the week, but had a
> different subject for the thread. I believe their issue was some code or
> widget lurking around without proper inclusions.
>
> What version of Livecode are you compiling with? I’ve had the same problem
> recently with a stack that I’ve tried to compiler in 8.1.8. I fear I opened
> this in 9dp11 to see the new dataGrid2 in action and saved the stack
> without backwards compatibility. This isn’t strictly Android as I was
> building for iOS when the error manifested.
>
> —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
___
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

OT: Developer Week SF Bay Area

[Mark Wieder via use-livecode]

If anyone is planning on coming to Developer Week 2018 in the Bay Area 
(3-7 February), more free OPEN passes have opened up. It's moving to 
Oakland from San Francisco this year, no doubt because nobody can afford 
San Francisco any more.


You must register by 11:59 pm on January 26 (or before we run out) to 
get your free OPEN Pass or SAVE $300 on your PRO Pass.


To register, go to 
https://www.eventbrite.com/e/developerweek-2018-tickets-36162005532?discount=MU2098&utm_campaign=MU2098


Promotional code MU2098, with a $300 discount, will automatically be 
applied to your order making your OPEN Pass completely free -- or use 
the discount towards an all-access PRO Pass.


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

Streaming video..

[Mike Bonner via use-livecode]

Quick question.. I'm attempting to write a program to work with my
hdhomerun (networked tv streamer) and think i'm on track.. However, i'm not
sure if its possible to tell the player to open a udp connection on port
5000 and wait for the stream to come in. (apparently, I need to have it
ready to receive before I send the command to the hdhr)  Will the player do
this?  If not I'll probably end up using vnc as my player, but it would
sure be nice to have an all LC solution.  (maybe I can use the browser
widget.. hmmm.  )
___
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: Anyone else got two-monitor issues with LC9 on Mac?

[Brian Milby via use-livecode]

@Graham, to determine if the 2 are related to the same underlying issue,
you should adjust your monitor layout so that the tops align. If the
problem goes away, then they are related (even if not identical). If the
problem doesn’t go away, then it is a new issue. That will be something
that is good to know when working on this issue.
On Sat, Jan 13, 2018 at 11:24 AM Graham Samuel via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Yes, of course it’s an OS thing really. I think it’s reasonable to want
> the Mac control panel configuration to mimic the physical arrangement I
> actually have. If I don’t do this, I’m always trying to make the mouse go
> somewhere which the Mac doesn’t see as part of the screen real estate.
> Since my physical arrangement is that the monitor is higher and to the side
> of the MacBook, that’s what I’ve set up in the control panel. The fact that
> this gives problems has clearly got to be a bug.
>
> After looking carefully at the bugs Martin has listed (one of which was
> raised by me, centuries ago!), I decided to submit a new report: it’s
> 20867. The mother ship may find that they can combine it with 19302, but I
> will leave that to them.
>
> Graham
>
> > On 13 Jan 2018, at 16:55, J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > It isn't the physical position of the monitors, it's how you arrange
> them in the Mac control panel. This allows you to set the virtual position
> of the two displays relative to each other. If I remember right, problems
> are avoided if you drag the two monitor images so that the tops are
> horizontally aligned.
> >
> > --
> > Jacqueline Landman Gay | jac...@hyperactivesw.com
> > HyperActive Software   | http://www.hyperactivesw.com
> >
> >
> >
> > On January 13, 2018 8:51:59 AM Graham Samuel via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> >> Thanks Martin - yes I do have a Mac Book Pro Retina, and since it’s
> normally on my desk with the monitor on a stand, the monitor is above the
> MacBook as you say. My search for bugs related to this didn’t turn up
> anything relevant: maybe I don’t understand how to do searches for
> unresolved bugs in particular areas. Anyway I missed the bugs you mention.
> Obviously I will now look at them and see what I can contribute.
> >>
> >> Thanks again
> >>
> >> Graham
> >>
> >>> On 13 Jan 2018, at 14:34, Martin Koob via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>>
> >>> I have experienced problems with dual monitors attached to my Mac Book
> Pro
> >>> Retina with LC 8 and posted bugs.
> >>>
> >>> http://quality.livecode.com/show_bug.cgi?id=19300
> >>> http://quality.livecode.com/show_bug.cgi?id=19302
> >>>
> >>> There are links on 19302  to other bugs I thought might be related.
> >>> http://quality.livecode.com/show_bug.cgi?id=15366
> >>> http://quality.livecode.com/show_bug.cgi?id=18363
> >>>
> >>> It seems the issue occurs only when the arrangement is that  secondary
> >>> external monitor is above the Mac Book Pro's monitor.  If in the
> Display
> >>> Preferences > arrangement I drag the secondary monitor to the side of
> the
> >>> primary monitor the issues I experienced were resolved.   It may also
> be an
> >>> issue with my retina display.  Do you have a Mac Book Pro Retina as
> well?
> >>>
> >>> You should post what you are seeing as a bug and reference these other
> ones.
> >>>
> >>> Martin Koob
> >>>
> >>>
> >>>
> >>> --
> >>> Sent from:
> http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html
> >>>
> >>> ___
> >>> 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
___
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: Problem pasting from Livecode to Mac Mail

[Brian Milby via use-livecode]

PR submitted against develop-8.2:
https://github.com/livecode/livecode/pull/6276

Updated MCClipboard::AddText such that is will clear the clipboard and only
place the plain text representations on the clipboard. The clipboard needed
to be cleared to avoid the HTML/RTF from a previous copy being left on the
clipboard which would cause issues when attempting to paste.

This will fix bugs 19206 and 20336.

Bug 18699 is actually due to the inclusion of HTML on the clipboard from my
testing (Mac/Windows).  TextEdit on the Mac places RTF and plain text on
the clipboard and does not suffer from the same issue when pasting into
Excel (which is why people were able to paste there and recopy to get
around the issue).

Have a good weekend everyone!

On Sat, Jan 13, 2018 at 11:27 AM, Brian Milby  wrote:

> PR just about done actually. It sets the plain text but leaves previous
> HTML right now. Should have it done this weekend.
>
> On Sat, Jan 13, 2018 at 10:50 AM Mark Waddingham via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> The behaviour should be that if you put plaintext then only plaintext
>> should be on the clipboard...
>>
>> If you put styled text then plain and rtf should be on the clipboard...
>> HTML maybe - but if that's the format causing the problem (and not rtf -
>> which I think is the main Cocoa style interchange format) then that needs
>> some thought.
>>
>> A line in a field is a paragraph - you can put vertical tabs in a line to
>> give you hard line breaks (i.e. BR in html). If other apps are interpreting
>> this differently then that causes a 'roundtrip' issue for LiveCode.
>>
>> Anyway, this is a result of the reworking of the clipboard we did early
>> on in 8 (maybe late 7) - if you have the time to poke around and propose a
>> patch on more than happy to help - it's been on my list to dig into for
>> ages, but hasn't reached the top yet!
>>
>> Warmest Regards,
>>
>> Mark.
>>
>> Sent from my iPhone
>>
>> > On 13 Jan 2018, at 15:16, Brian Milby via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> >
>> > The text on the clipboard is fine. The problem is that too much is put
>> on
>> > the clipboard. Plain text converted to HTML is likely the real problem.
>> > That is why a trip through a plain text editor fixes the issue. It takes
>> > the plain text from the clipboard and only puts plain text on the
>> > clipboard. There are 2 bug reports on this issue. I’m planning on
>> > submitting a PR but was waiting for any reasoning behind the current
>> method
>> > that I may have overlooked.
>> > On Sat, Jan 13, 2018 at 9:11 AM Richard Burkett via use-livecode <
>> > use-livecode@lists.runrev.com> wrote:
>> >
>> >> Actually, the reason why we’re having this conversation is that I
>> needed
>> >> to load the clipboard with in what SHOULD be plain text format data via
>> >> script, data that included plain returns, and it appeared as double
>> spaced
>> >> when pasted into Mac Mail. There was another user-driven in terms of
>> >> selecting text. This should probably be a bug in LiveCode (the same
>> thing
>> >> happens when I copy a script from the editor in LiveCode).
>> >>
>> >> In any case, I found a script solution which I sent to the list
>> >> (use-livecode Digest, Vol 172, Issue 24, item 5) and it works fine now.
>> >> Perhaps LiveCode should have a clipBoard key “plainTextREALLY” that
>> uses
>> >> that script.
>> >>
>> >> Thanks again for your help with this, Paul Hibbert.
>> >>
>> >> Richard
>> >>
>> >> Richard Burkett
>> >> richard.burk...@sbcglobal.net
>> >>
>> >>
>> >>> On Fri, Jan 12, 2018 Brian Milby wrote:
>> >>>
>> >>> That is precisely why we are having this conversation.  An assumption
>> was
>> >>> made that creating an HTML version of plain text was needed for the
>> >>> clipboard.
>> >>>
>> >>> On Fri, Jan 12, 2018 at 4:51 PM Bob Sneidar via use-livecode <
>> >>> use-livecode@lists.runrev.com >
>> >> wrote:
>> >>>
>>  Non- starter. Can't make assumptions about the end user's intent.
>> What
>> >> if
>>  what he was copying was SUPPOSED to have double line breaks or
>> carriage
>>  returns? The complaint would be that LC was taking liberties with
>> user's
>>  data!
>> 
>>  Bob S
>> 
>> 
>> > On Jan 12, 2018, at 09:42 , Brian Milby via use-livecode <
>>  use-livecode@lists.runrev.com > >>
>> >> wrote:
>> >
>> > If it was changed to use  for single line breaks and only
>> assuming
>> >> a
>> > paragraph when there are 2
>> 
>> 
>>  ___
>>  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 <
>> >> http://lists.runrev.com/mailman/listinfo/use-livecode>
>> >

Re: Problem pasting from Livecode to Mac Mail

[Brian Milby via use-livecode]

PR just about done actually. It sets the plain text but leaves previous
HTML right now. Should have it done this weekend.
On Sat, Jan 13, 2018 at 10:50 AM Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> wrote:

> The behaviour should be that if you put plaintext then only plaintext
> should be on the clipboard...
>
> If you put styled text then plain and rtf should be on the clipboard...
> HTML maybe - but if that's the format causing the problem (and not rtf -
> which I think is the main Cocoa style interchange format) then that needs
> some thought.
>
> A line in a field is a paragraph - you can put vertical tabs in a line to
> give you hard line breaks (i.e. BR in html). If other apps are interpreting
> this differently then that causes a 'roundtrip' issue for LiveCode.
>
> Anyway, this is a result of the reworking of the clipboard we did early on
> in 8 (maybe late 7) - if you have the time to poke around and propose a
> patch on more than happy to help - it's been on my list to dig into for
> ages, but hasn't reached the top yet!
>
> Warmest Regards,
>
> Mark.
>
> Sent from my iPhone
>
> > On 13 Jan 2018, at 15:16, Brian Milby via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > The text on the clipboard is fine. The problem is that too much is put on
> > the clipboard. Plain text converted to HTML is likely the real problem.
> > That is why a trip through a plain text editor fixes the issue. It takes
> > the plain text from the clipboard and only puts plain text on the
> > clipboard. There are 2 bug reports on this issue. I’m planning on
> > submitting a PR but was waiting for any reasoning behind the current
> method
> > that I may have overlooked.
> > On Sat, Jan 13, 2018 at 9:11 AM Richard Burkett via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> Actually, the reason why we’re having this conversation is that I needed
> >> to load the clipboard with in what SHOULD be plain text format data via
> >> script, data that included plain returns, and it appeared as double
> spaced
> >> when pasted into Mac Mail. There was another user-driven in terms of
> >> selecting text. This should probably be a bug in LiveCode (the same
> thing
> >> happens when I copy a script from the editor in LiveCode).
> >>
> >> In any case, I found a script solution which I sent to the list
> >> (use-livecode Digest, Vol 172, Issue 24, item 5) and it works fine now.
> >> Perhaps LiveCode should have a clipBoard key “plainTextREALLY” that uses
> >> that script.
> >>
> >> Thanks again for your help with this, Paul Hibbert.
> >>
> >> Richard
> >>
> >> Richard Burkett
> >> richard.burk...@sbcglobal.net
> >>
> >>
> >>> On Fri, Jan 12, 2018 Brian Milby wrote:
> >>>
> >>> That is precisely why we are having this conversation.  An assumption
> was
> >>> made that creating an HTML version of plain text was needed for the
> >>> clipboard.
> >>>
> >>> On Fri, Jan 12, 2018 at 4:51 PM Bob Sneidar via use-livecode <
> >>> use-livecode@lists.runrev.com >
> >> wrote:
> >>>
>  Non- starter. Can't make assumptions about the end user's intent. What
> >> if
>  what he was copying was SUPPOSED to have double line breaks or
> carriage
>  returns? The complaint would be that LC was taking liberties with
> user's
>  data!
> 
>  Bob S
> 
> 
> > On Jan 12, 2018, at 09:42 , Brian Milby via use-livecode <
>  use-livecode@lists.runrev.com >
> >> wrote:
> >
> > If it was changed to use  for single line breaks and only
> assuming
> >> a
> > paragraph when there are 2
> 
> 
>  ___
>  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 <
> >> 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
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this 

Re: Anyone else got two-monitor issues with LC9 on Mac?

[Graham Samuel via use-livecode]

Yes, of course it’s an OS thing really. I think it’s reasonable to want the Mac 
control panel configuration to mimic the physical arrangement I actually have. 
If I don’t do this, I’m always trying to make the mouse go somewhere which the 
Mac doesn’t see as part of the screen real estate. Since my physical 
arrangement is that the monitor is higher and to the side of the MacBook, 
that’s what I’ve set up in the control panel. The fact that this gives problems 
has clearly got to be a bug.

After looking carefully at the bugs Martin has listed (one of which was raised 
by me, centuries ago!), I decided to submit a new report: it’s 20867. The 
mother ship may find that they can combine it with 19302, but I will leave that 
to them.

Graham

> On 13 Jan 2018, at 16:55, J. Landman Gay via use-livecode 
>  wrote:
> 
> It isn't the physical position of the monitors, it's how you arrange them in 
> the Mac control panel. This allows you to set the virtual position of the two 
> displays relative to each other. If I remember right, problems are avoided if 
> you drag the two monitor images so that the tops are horizontally aligned.
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.com
> 
> 
> 
> On January 13, 2018 8:51:59 AM Graham Samuel via use-livecode 
>  wrote:
> 
>> Thanks Martin - yes I do have a Mac Book Pro Retina, and since it’s normally 
>> on my desk with the monitor on a stand, the monitor is above the MacBook as 
>> you say. My search for bugs related to this didn’t turn up anything 
>> relevant: maybe I don’t understand how to do searches for unresolved bugs in 
>> particular areas. Anyway I missed the bugs you mention. Obviously I will now 
>> look at them and see what I can contribute.
>> 
>> Thanks again
>> 
>> Graham
>> 
>>> On 13 Jan 2018, at 14:34, Martin Koob via use-livecode 
>>>  wrote:
>>> 
>>> I have experienced problems with dual monitors attached to my Mac Book Pro
>>> Retina with LC 8 and posted bugs.
>>> 
>>> http://quality.livecode.com/show_bug.cgi?id=19300
>>> http://quality.livecode.com/show_bug.cgi?id=19302
>>> 
>>> There are links on 19302  to other bugs I thought might be related.
>>> http://quality.livecode.com/show_bug.cgi?id=15366
>>> http://quality.livecode.com/show_bug.cgi?id=18363
>>> 
>>> It seems the issue occurs only when the arrangement is that  secondary
>>> external monitor is above the Mac Book Pro's monitor.  If in the Display
>>> Preferences > arrangement I drag the secondary monitor to the side of the
>>> primary monitor the issues I experienced were resolved.   It may also be an
>>> issue with my retina display.  Do you have a Mac Book Pro Retina as well?
>>> 
>>> You should post what you are seeing as a bug and reference these other ones.
>>> 
>>> Martin Koob
>>> 
>>> 
>>> 
>>> --
>>> Sent from: 
>>> http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html
>>> 
>>> ___
>>> 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: Anyone else got two-monitor issues with LC9 on Mac?

[J. Landman Gay via use-livecode]

It isn't the physical position of the monitors, it's how you arrange them 
in the Mac control panel. This allows you to set the virtual position of 
the two displays relative to each other. If I remember right, problems are 
avoided if you drag the two monitor images so that the tops are 
horizontally aligned.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com



On January 13, 2018 8:51:59 AM Graham Samuel via use-livecode 
 wrote:


Thanks Martin - yes I do have a Mac Book Pro Retina, and since it’s 
normally on my desk with the monitor on a stand, the monitor is above the 
MacBook as you say. My search for bugs related to this didn’t turn up 
anything relevant: maybe I don’t understand how to do searches for 
unresolved bugs in particular areas. Anyway I missed the bugs you mention. 
Obviously I will now look at them and see what I can contribute.


Thanks again

Graham

On 13 Jan 2018, at 14:34, Martin Koob via use-livecode 
 wrote:


I have experienced problems with dual monitors attached to my Mac Book Pro
Retina with LC 8 and posted bugs.

http://quality.livecode.com/show_bug.cgi?id=19300
http://quality.livecode.com/show_bug.cgi?id=19302

There are links on 19302  to other bugs I thought might be related.
http://quality.livecode.com/show_bug.cgi?id=15366
http://quality.livecode.com/show_bug.cgi?id=18363

It seems the issue occurs only when the arrangement is that  secondary
external monitor is above the Mac Book Pro's monitor.  If in the Display
Preferences > arrangement I drag the secondary monitor to the side of the
primary monitor the issues I experienced were resolved.   It may also be an
issue with my retina display.  Do you have a Mac Book Pro Retina as well?

You should post what you are seeing as a bug and reference these other ones.

Martin Koob



--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html


___
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: Problem pasting from Livecode to Mac Mail

[Mark Waddingham via use-livecode]

The behaviour should be that if you put plaintext then only plaintext should be 
on the clipboard...

If you put styled text then plain and rtf should be on the clipboard... HTML 
maybe - but if that's the format causing the problem (and not rtf - which I 
think is the main Cocoa style interchange format) then that needs some thought.

A line in a field is a paragraph - you can put vertical tabs in a line to give 
you hard line breaks (i.e. BR in html). If other apps are interpreting this 
differently then that causes a 'roundtrip' issue for LiveCode.

Anyway, this is a result of the reworking of the clipboard we did early on in 8 
(maybe late 7) - if you have the time to poke around and propose a patch on 
more than happy to help - it's been on my list to dig into for ages, but hasn't 
reached the top yet!

Warmest Regards,

Mark.

Sent from my iPhone

> On 13 Jan 2018, at 15:16, Brian Milby via use-livecode 
>  wrote:
> 
> The text on the clipboard is fine. The problem is that too much is put on
> the clipboard. Plain text converted to HTML is likely the real problem.
> That is why a trip through a plain text editor fixes the issue. It takes
> the plain text from the clipboard and only puts plain text on the
> clipboard. There are 2 bug reports on this issue. I’m planning on
> submitting a PR but was waiting for any reasoning behind the current method
> that I may have overlooked.
> On Sat, Jan 13, 2018 at 9:11 AM Richard Burkett via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> Actually, the reason why we’re having this conversation is that I needed
>> to load the clipboard with in what SHOULD be plain text format data via
>> script, data that included plain returns, and it appeared as double spaced
>> when pasted into Mac Mail. There was another user-driven in terms of
>> selecting text. This should probably be a bug in LiveCode (the same thing
>> happens when I copy a script from the editor in LiveCode).
>> 
>> In any case, I found a script solution which I sent to the list
>> (use-livecode Digest, Vol 172, Issue 24, item 5) and it works fine now.
>> Perhaps LiveCode should have a clipBoard key “plainTextREALLY” that uses
>> that script.
>> 
>> Thanks again for your help with this, Paul Hibbert.
>> 
>> Richard
>> 
>> Richard Burkett
>> richard.burk...@sbcglobal.net
>> 
>> 
>>> On Fri, Jan 12, 2018 Brian Milby wrote:
>>> 
>>> That is precisely why we are having this conversation.  An assumption was
>>> made that creating an HTML version of plain text was needed for the
>>> clipboard.
>>> 
>>> On Fri, Jan 12, 2018 at 4:51 PM Bob Sneidar via use-livecode <
>>> use-livecode@lists.runrev.com >
>> wrote:
>>> 
 Non- starter. Can't make assumptions about the end user's intent. What
>> if
 what he was copying was SUPPOSED to have double line breaks or carriage
 returns? The complaint would be that LC was taking liberties with user's
 data!
 
 Bob S
 
 
> On Jan 12, 2018, at 09:42 , Brian Milby via use-livecode <
 use-livecode@lists.runrev.com >
>> wrote:
> 
> If it was changed to use  for single line breaks and only assuming
>> a
> paragraph when there are 2
 
 
 ___
 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 <
>> 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: Problem pasting from Livecode to Mac Mail

[Brian Milby via use-livecode]

The text on the clipboard is fine. The problem is that too much is put on
the clipboard. Plain text converted to HTML is likely the real problem.
That is why a trip through a plain text editor fixes the issue. It takes
the plain text from the clipboard and only puts plain text on the
clipboard. There are 2 bug reports on this issue. I’m planning on
submitting a PR but was waiting for any reasoning behind the current method
that I may have overlooked.
On Sat, Jan 13, 2018 at 9:11 AM Richard Burkett via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Actually, the reason why we’re having this conversation is that I needed
> to load the clipboard with in what SHOULD be plain text format data via
> script, data that included plain returns, and it appeared as double spaced
> when pasted into Mac Mail. There was another user-driven in terms of
> selecting text. This should probably be a bug in LiveCode (the same thing
> happens when I copy a script from the editor in LiveCode).
>
> In any case, I found a script solution which I sent to the list
> (use-livecode Digest, Vol 172, Issue 24, item 5) and it works fine now.
> Perhaps LiveCode should have a clipBoard key “plainTextREALLY” that uses
> that script.
>
> Thanks again for your help with this, Paul Hibbert.
>
> Richard
>
> Richard Burkett
> richard.burk...@sbcglobal.net
>
>
> On Fri, Jan 12, 2018 Brian Milby wrote:
>
> > That is precisely why we are having this conversation.  An assumption was
> > made that creating an HTML version of plain text was needed for the
> > clipboard.
> >
> > On Fri, Jan 12, 2018 at 4:51 PM Bob Sneidar via use-livecode <
> > use-livecode@lists.runrev.com >
> wrote:
> >
> >> Non- starter. Can't make assumptions about the end user's intent. What
> if
> >> what he was copying was SUPPOSED to have double line breaks or carriage
> >> returns? The complaint would be that LC was taking liberties with user's
> >> data!
> >>
> >> Bob S
> >>
> >>
> >>> On Jan 12, 2018, at 09:42 , Brian Milby via use-livecode <
> >> use-livecode@lists.runrev.com >
> wrote:
> >>>
> >>> If it was changed to use  for single line breaks and only assuming
> a
> >>> paragraph when there are 2
> >>
> >>
> >> ___
> >> 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 <
> 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: Problem pasting from Livecode to Mac Mail

[Richard Burkett via use-livecode]

Actually, the reason why we’re having this conversation is that I needed to 
load the clipboard with in what SHOULD be plain text format data via script, 
data that included plain returns, and it appeared as double spaced when pasted 
into Mac Mail. There was another user-driven in terms of selecting text. This 
should probably be a bug in LiveCode (the same thing happens when I copy a 
script from the editor in LiveCode). 

In any case, I found a script solution which I sent to the list (use-livecode 
Digest, Vol 172, Issue 24, item 5) and it works fine now. Perhaps LiveCode 
should have a clipBoard key “plainTextREALLY” that uses that script.

Thanks again for your help with this, Paul Hibbert.

Richard

Richard Burkett
richard.burk...@sbcglobal.net


On Fri, Jan 12, 2018 Brian Milby wrote:

> That is precisely why we are having this conversation.  An assumption was
> made that creating an HTML version of plain text was needed for the
> clipboard.
> 
> On Fri, Jan 12, 2018 at 4:51 PM Bob Sneidar via use-livecode <
> use-livecode@lists.runrev.com > wrote:
> 
>> Non- starter. Can't make assumptions about the end user's intent. What if
>> what he was copying was SUPPOSED to have double line breaks or carriage
>> returns? The complaint would be that LC was taking liberties with user's
>> data!
>> 
>> Bob S
>> 
>> 
>>> On Jan 12, 2018, at 09:42 , Brian Milby via use-livecode <
>> use-livecode@lists.runrev.com > wrote:
>>> 
>>> If it was changed to use  for single line breaks and only assuming a
>>> paragraph when there are 2
>> 
>> 
>> ___
>> 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: Anyone else got two-monitor issues with LC9 on Mac?

[Graham Samuel via use-livecode]

Hi Matthias

Your solution sounds interesting, but to me it’s just a workaround. I simply 
want more screen real estate for debugging - so as far as I can see, using 
different spaces would provide that. After reading what Martin Koob has to say, 
I’m pretty certain that there really is a bug. Even though it’s holding up some 
urgent work, I think I have to make a proper examination of this and report it 
(maybe as additional material on an existing bug report).

Graham

> On 13 Jan 2018, at 14:47, Matthias Rebbe via use-livecode 
>  wrote:
> 
> Graham,
> 
> i followed your steps here on my system (iMac 5K and Thunderbolt display). It 
> works here without problems.
> 
> Maybe it works here, because i have setup that my monitors use different 
> spaces. You can set this in SystemControl->MissionControl. I do not know the 
> exact english expression as i have here a german Mac OS X running.
> 
> One of the advantages  of this option is that i can run other programs (in my 
> case DVD-Player) in fullscreen  on one screen and the other screen is still 
> visible and not black. 
> 
> Maybe you should try that set this option in mission control too.
> 
> Regards,
> Matthias
> 
> 
> 
> 
> Matthias Rebbe
> Tel +49 5741 31
> ‌https://matthiasrebbe.eu ‌
> 
>> Am 13.01.2018 um 13:14 schrieb Graham Samuel via use-livecode 
>> mailto:use-livecode@lists.runrev.com>>:
>> 
>> Sorry this is a bit long, but it needs an accurate description IMHO.
>> 
>> I’ve already submitted a bug report on some strangeness with using the IDE 
>> with LC9.0.0 (dp11) on a two-screen system, with the suspicion that it was 
>> me doing something wrong - it was just very muddling. However, today I seem 
>> to have found something a bit more generic and I’d like to know if anyone 
>> else has seen it, before I start the tedious business of simplifying the 
>> issue for a bug report.
>> 
>> This is what I’m seeing, on a MacBook Pro running High Sierra 10.3.2. 
>> Attached to the machine is a monitor, in the logical top left position, so 
>> the mouse can travel from the Mac screen to the monitor by moving North 
>> West, as it were. The MacPro screen is 2560 x 1600 Retina (which AFAIKS 
>> means it’s acting like 1280 x 800 for normal display purposes), and the 
>> monitor is 1920 x 1080. The system is configured so that the initial Mac 
>> menu bar is on the MacPro screen (since we don’t always use the monitor).
>> 
>> If I open LC9, the initial screen comes up on the MacPro, as expected. I 
>> open a stack I’m working on and drag the initial display (just the first 
>> card of the first stack) to the monitor. Going back to the menu bar on the 
>> MacPro display, I open the Project Browser to see the stack details. If I 
>> click on the little plus (“+”) sign next to the stack name, the browser 
>> display unfolds to show the cards in the stack, exactly as expected. BUT if 
>> I move the Project Browser window to the monitor, the plus sign has no 
>> effect! I can still close the project browser window but I can’t activate 
>> it, whether or not I make sure that LC has the focus by clicking on my card 
>> display. If I close the Project Browser, switch to the monitor and activate 
>> LiveCode from there (for example by clicking on the mirrored menu for LC 
>> which appears at the top of the screen) and then open the Project Browser 
>> again so that it initially opens in the monitor, it works OK! If I drag the 
>> PB window back to the MacPro display, it goes on working.
>> 
>> This is the essence of the issue - there may be other variants with the Tool 
>> palette etc but I’m trying to keep it simple.
>> 
>> Does anyone else see this or know of any report? Can’t find anything in the 
>> Quality database.
>> 
>> TIA
>> 
>> Graham
>> ___
>> 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: Anyone else got two-monitor issues with LC9 on Mac?

[Graham Samuel via use-livecode]

Thanks Martin - yes I do have a Mac Book Pro Retina, and since it’s normally on 
my desk with the monitor on a stand, the monitor is above the MacBook as you 
say. My search for bugs related to this didn’t turn up anything relevant: maybe 
I don’t understand how to do searches for unresolved bugs in particular areas. 
Anyway I missed the bugs you mention. Obviously I will now look at them and see 
what I can contribute.

Thanks again

Graham

> On 13 Jan 2018, at 14:34, Martin Koob via use-livecode 
>  wrote:
> 
> I have experienced problems with dual monitors attached to my Mac Book Pro
> Retina with LC 8 and posted bugs.
> 
> http://quality.livecode.com/show_bug.cgi?id=19300
> http://quality.livecode.com/show_bug.cgi?id=19302
> 
> There are links on 19302  to other bugs I thought might be related.  
> http://quality.livecode.com/show_bug.cgi?id=15366
> http://quality.livecode.com/show_bug.cgi?id=18363
> 
> It seems the issue occurs only when the arrangement is that  secondary
> external monitor is above the Mac Book Pro's monitor.  If in the Display
> Preferences > arrangement I drag the secondary monitor to the side of the
> primary monitor the issues I experienced were resolved.   It may also be an
> issue with my retina display.  Do you have a Mac Book Pro Retina as well?
> 
> You should post what you are seeing as a bug and reference these other ones.
> 
> Martin Koob
> 
> 
> 
> --
> Sent from: 
> http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html
> 
> ___
> 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: Anyone else got two-monitor issues with LC9 on Mac?

[Matthias Rebbe via use-livecode]

Graham,

i followed your steps here on my system (iMac 5K and Thunderbolt display). It 
works here without problems.

Maybe it works here, because i have setup that my monitors use different 
spaces. You can set this in SystemControl->MissionControl. I do not know the 
exact english expression as i have here a german Mac OS X running.

One of the advantages  of this option is that i can run other programs (in my 
case DVD-Player) in fullscreen  on one screen and the other screen is still 
visible and not black. 

Maybe you should try that set this option in mission control too.

Regards,
Matthias




Matthias Rebbe
Tel +49 5741 31
‌https://matthiasrebbe.eu ‌

> Am 13.01.2018 um 13:14 schrieb Graham Samuel via use-livecode 
> mailto:use-livecode@lists.runrev.com>>:
> 
> Sorry this is a bit long, but it needs an accurate description IMHO.
> 
> I’ve already submitted a bug report on some strangeness with using the IDE 
> with LC9.0.0 (dp11) on a two-screen system, with the suspicion that it was me 
> doing something wrong - it was just very muddling. However, today I seem to 
> have found something a bit more generic and I’d like to know if anyone else 
> has seen it, before I start the tedious business of simplifying the issue for 
> a bug report.
> 
> This is what I’m seeing, on a MacBook Pro running High Sierra 10.3.2. 
> Attached to the machine is a monitor, in the logical top left position, so 
> the mouse can travel from the Mac screen to the monitor by moving North West, 
> as it were. The MacPro screen is 2560 x 1600 Retina (which AFAIKS means it’s 
> acting like 1280 x 800 for normal display purposes), and the monitor is 1920 
> x 1080. The system is configured so that the initial Mac menu bar is on the 
> MacPro screen (since we don’t always use the monitor).
> 
> If I open LC9, the initial screen comes up on the MacPro, as expected. I open 
> a stack I’m working on and drag the initial display (just the first card of 
> the first stack) to the monitor. Going back to the menu bar on the MacPro 
> display, I open the Project Browser to see the stack details. If I click on 
> the little plus (“+”) sign next to the stack name, the browser display 
> unfolds to show the cards in the stack, exactly as expected. BUT if I move 
> the Project Browser window to the monitor, the plus sign has no effect! I can 
> still close the project browser window but I can’t activate it, whether or 
> not I make sure that LC has the focus by clicking on my card display. If I 
> close the Project Browser, switch to the monitor and activate LiveCode from 
> there (for example by clicking on the mirrored menu for LC which appears at 
> the top of the screen) and then open the Project Browser again so that it 
> initially opens in the monitor, it works OK! If I drag the PB window back to 
> the MacPro display, it goes on working.
> 
> This is the essence of the issue - there may be other variants with the Tool 
> palette etc but I’m trying to keep it simple.
> 
> Does anyone else see this or know of any report? Can’t find anything in the 
> Quality database.
> 
> TIA
> 
> Graham
> ___
> 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: Anyone else got two-monitor issues with LC9 on Mac?

[Martin Koob via use-livecode]

I have experienced problems with dual monitors attached to my Mac Book Pro
Retina with LC 8 and posted bugs.

http://quality.livecode.com/show_bug.cgi?id=19300
http://quality.livecode.com/show_bug.cgi?id=19302

There are links on 19302  to other bugs I thought might be related.  
http://quality.livecode.com/show_bug.cgi?id=15366
http://quality.livecode.com/show_bug.cgi?id=18363

It seems the issue occurs only when the arrangement is that  secondary
external monitor is above the Mac Book Pro's monitor.  If in the Display
Preferences > arrangement I drag the secondary monitor to the side of the
primary monitor the issues I experienced were resolved.   It may also be an
issue with my retina display.  Do you have a Mac Book Pro Retina as well?

You should post what you are seeing as a bug and reference these other ones.

Martin Koob



--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
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: Server-side xml validator anyone ?

[jbv via use-livecode]

On Sat, January 13, 2018 2:08 pm, Mark via use-livecode wrote:
> If your XML is UTF8-enconded and your UTF8 data is correct, it will
> work. Your probably isn't invalid XML but either a problem with the
> encoding of the entire file or a particular string.
>
> The best way to validate XML on your server is to install a little
> command line utility and use the shell function.
>
>

Thanks for your reply.
Yes, that's exactly what I'm doing : I'm using a small php script
I found on the web; but as the xml can be quite large, I need to
use temporary files, and things get a bit slow at times.
That's why I was hoping for a 100% LC solution.

Best.


___
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: Server-side xml validator anyone ?

[Mark via use-livecode]

If your XML is UTF8-enconded and your UTF8 data is correct, it will 
work. Your probably isn't invalid XML but either a problem with the 
encoding of the entire file or a particular string.


The best way to validate XML on your server is to install a little 
command line utility and use the shell function.



Op 12-01-18 om 13:19 schreef jbv via use-livecode:

Hi list,
I have several server-side LC scripts that transform text and data
uploaded by end users on web pages into xml to be stored in a database and
used later in other web pages or apps.
The problem is, despite all the correction scripts I have added, that
sometimes the uploaded content corrupts the xml structure. This happens
for instance when some weird UTF-8 text is uploaded.
Is there a ready-to-use piece of code that would check the conformity of
some xml data that I could include in my LC scripts ?

Thanks in advance,
jbv




___
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

Anyone else got two-monitor issues with LC9 on Mac?

[Graham Samuel via use-livecode]

Sorry this is a bit long, but it needs an accurate description IMHO.

I’ve already submitted a bug report on some strangeness with using the IDE with 
LC9.0.0 (dp11) on a two-screen system, with the suspicion that it was me doing 
something wrong - it was just very muddling. However, today I seem to have 
found something a bit more generic and I’d like to know if anyone else has seen 
it, before I start the tedious business of simplifying the issue for a bug 
report.

This is what I’m seeing, on a MacBook Pro running High Sierra 10.3.2. Attached 
to the machine is a monitor, in the logical top left position, so the mouse can 
travel from the Mac screen to the monitor by moving North West, as it were. The 
MacPro screen is 2560 x 1600 Retina (which AFAIKS means it’s acting like 1280 x 
800 for normal display purposes), and the monitor is 1920 x 1080. The system is 
configured so that the initial Mac menu bar is on the MacPro screen (since we 
don’t always use the monitor).

If I open LC9, the initial screen comes up on the MacPro, as expected. I open a 
stack I’m working on and drag the initial display (just the first card of the 
first stack) to the monitor. Going back to the menu bar on the MacPro display, 
I open the Project Browser to see the stack details. If I click on the little 
plus (“+”) sign next to the stack name, the browser display unfolds to show the 
cards in the stack, exactly as expected. BUT if I move the Project Browser 
window to the monitor, the plus sign has no effect! I can still close the 
project browser window but I can’t activate it, whether or not I make sure that 
LC has the focus by clicking on my card display. If I close the Project 
Browser, switch to the monitor and activate LiveCode from there (for example by 
clicking on the mirrored menu for LC which appears at the top of the screen) 
and then open the Project Browser again so that it initially opens in the 
monitor, it works OK! If I drag the PB window back to the MacPro display, it 
goes on working.

This is the essence of the issue - there may be other variants with the Tool 
palette etc but I’m trying to keep it simple.

Does anyone else see this or know of any report? Can’t find anything in the 
Quality database.

TIA

Graham
___
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 build executable on test device fails

[MWCM via use-livecode]

> Testing on an Android device, the "Standalone builder progress" window
> shows first "Building classes" and then for a brief moment "Building
> executable", after which an error window reads "Unable to build app for
> testing: could not open module file".
> 
> Searched the forums but no mention at all of this problem.
> 
> --
> Nicolas Cueto
> 

Someone else on the list had this problem within the week, but had a different 
subject for the thread. I believe their issue was some code or widget lurking 
around without proper inclusions. 

What version of Livecode are you compiling with? I’ve had the same problem 
recently with a stack that I’ve tried to compiler in 8.1.8. I fear I opened 
this in 9dp11 to see the new dataGrid2 in action and saved the stack without 
backwards compatibility. This isn’t strictly Android as I was building for iOS 
when the error manifested. 

—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