Re: "empty" background in printed pdf is actually grey

Don't things inherit attributes?. so if empty, that means the card would inherit the stacks background color?? On Wed, Oct 30, 2019 at 8:21 PM Dr. Hawkins via use-livecode < use-livecode@lists.runrev.com> wrote: > > I’m within spitting distance on this merging of pdfs, using livecode to >

Re: cr, lf, and reading in terminals/vim

My suggestion is to just bite the bullet and build LC where 'file' exports using LF on Mac. The change required is literally a couple of characters in one file (maybe two files to include the server default, but you can already change it there on demand). Leave the constants as they are (LF). It

Re: cr, lf, and reading in terminals/vim

Brian Milby wrote: > The reason for the difficulty is that internally LC uses LF as the > line ending. The cr, lf, and return constants all actually map to LF. > When you write a text file, LC will convert line endings to the native > format. So for Windows you get CRLF, Linux gets LF, and Mac

Re: cr, lf, and reading in terminals/vim

The reason for the difficulty is that internally LC uses LF as the line ending. The cr, lf, and return constants all actually map to LF. When you write a text file, LC will convert line endings to the native format. So for Windows you get CRLF, Linux gets LF, and Mac gets CR. I take issue with

"empty" background in printed pdf is actually grey

I’m within spitting distance on this merging of pdfs, using livecode to generate python code and using the PyPDF2 library. My last problem is that the pdf generated by livecode creates a great background, whereas it should be transparent. set the backgroundColor of otCd to empty print otCd

Re: cr, lf, and reading in terminals/vim

In case your python file becomes a bit more complicated, you shouldn't use workarounds as using backspace to come to a binary format, because you then need exact indents (could be tabs). Better use (without replacing anything in mrgCmds) Matthias' answer to use binary write. Or the usual variant

Re: cr, lf, and reading in terminals/vim

On Oct 30, 2019, at 2:57 PM, Klaus major-k via use-livecode wrote: > > no idea, but it worked for me years ago. :-) which is the ultimate test . . . and, now that you mention it, *far* for the oddest fix . . . — Richard E. Hawkins, Esq. The Hawkins Law Firm 3430 E. Flamingo Rd. Suite 232

Re: cr, lf, and reading in terminals/vim

Hi Richard, > Am 30.10.2019 um 22:55 schrieb Dr. Hawkins via use-livecode > : > > On Oct 30, 2019, at 2:42 PM, Matthias mentioned >> I am not sure, if this will help with your task, but if i want to avoid >> that the os replaces the line breaks with it´s default i am writing a binary >> file

Re: cr, lf, and reading in terminals/vim

On Oct 30, 2019, at 2:42 PM, Matthias mentioned > I am not sure, if this will help with your task, but if i want to avoid that > the os replaces the line breaks with it´s default i am writing a binary file > instead of a text file. So in your case you would open the file for "binary >

Re: cr, lf, and reading in terminals/vim

Hi Richard, > Am 30.10.2019 um 22:28 schrieb Dr. Hawkins via use-livecode > : > > I’ve tried every combination of cr, lf, and crlf, but whenever I assemble > into a file, I get something that neither the OSX terminal or vim recognizes > as having lf in it > > I build a set of commands in

Re: cr, lf, and reading in terminals/vim

I am not sure, if this will help with your task, but if i want to avoid that the os replaces the line breaks with it´s default i am writing a binary file instead of a text file. So in your case you would open the file for "binary write". Regards, Matthias Matthias Rebbe free tools for

Re: Need trig & LCB help

Greg, I've been away from LCB for a while. When reading the last post again I remembered an improvement that you could try to use: The current version computes the pathes with every redraw (onPaint). This is far too often. We could compute the pathes once (in onCreate) and then update ONLY when

cr, lf, and reading in terminals/vim

I’ve tried every combination of cr, lf, and crlf, but whenever I assemble into a file, I get something that neither the OSX terminal or vim recognizes as having lf in it I build a set of commands in mrgCmds, appending cr as I go, but I get a bunch of ^M in the otherwise uninterrupted stream

Re: Need trig & LCB help

This works much better than what I was trying. THANKS! - Replace the last part of your handler with the following. variable tBNum as Number variable tBCenters as List put tBigRad - tLilRad into tInnerRad put the number of elements in mData into tBNum

Fun with the templateimage

Hi all, we know that "the templatexx" is a very helpful thingie. But I was really surprised that we can even EXPORT something from the templateimage until I tried this: - on mouseUp ## My good ol' banana, older users of MC might remember

Re: The Roadmap

Thanks Bernard. Exactly what I think. Only I could not express it that way in English. Matthias Matthias Rebbe free tools for Livecoders: InstaMaker WinSignMaker Mac > Am 30.10.2019 um 17:17 schrieb Bernard Devlin via

Re: The Roadmap

+1 > On Oct 30, 2019, at 09:17 , Bernard Devlin via use-livecode > wrote: > > On Tue, Oct 29, 2019 at 7:00 PM Richard Gaskin via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> >> If it were up to me I'd ditch it altogether. >> > > Whatever frustrations I have with Livecode

Re: The Overflow

Pure heresy! I CAN write perfect code first time every time! I just have to try harder!! ;-) Bob S > On Oct 30, 2019, at 09:22 , Mark Wieder via use-livecode > wrote: > > My Most Embarrassing Mistakes as a Programmer (so far) >

Re: The Overflow

Done! Bob S > On Oct 30, 2019, at 09:22 , Mark Wieder via use-livecode > wrote: > > If you're not already getting Stack Overflow's email newsletter (published > every two weeks) I want to recommend it highly. I just got issue #3 in the > mail today and it's got some fascinating articles

Re: The Roadmap

On 10/30/19 9:17 AM, Bernard Devlin via use-livecode wrote: IBM with all their resources and access to capital markets couldn't hold themselves to their own limited roadmap. ...and now IBM has bought RedHat. -- Mark Wieder ahsoftw...@gmail.com

The Overflow

If you're not already getting Stack Overflow's email newsletter (published every two weeks) I want to recommend it highly. I just got issue #3 in the mail today and it's got some fascinating articles in it. A couple from the current issue: The Lines of Code That Changed Everything

Re: The Roadmap

On Tue, Oct 29, 2019 at 7:00 PM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > > If it were up to me I'd ditch it altogether. > Whatever frustrations I have with Livecode they are vastly outweighed by the things that it can do and the things it can do now that it

Re: in case you need another reason to love LiveCode...

This is probably why it took so long for RunRev to incorporate localization and unicode. What a mess! Bob S > On Oct 29, 2019, at 20:59 , Richard Gaskin via use-livecode > wrote: > > Mark Wieder wrote: > > > How hard can text editing be? > > > >

The Roadmap

Sorry about starting this as a new thread: email client misbehaving. Richard Gaskin wrote: "Richmond wrote: > Of course if certain long-term stuff from the Kickstarters don't > appear on the Roadmap it is easier to hold LC to account than if > the Roadmap were to disappear completely. Which