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

2019-11-02 Thread Richard Gaskin via use-livecode
doc hawk wrote: If I’m not missing something, it’s a bug in Livecode if it generates a pdf of a field with no backgroundColor and false opaque for Sheffield, card, and stack. I wonder if it's related to this mystery in the forums: https://forums.livecode.com/viewtopic.php?f=8=33238 And as

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

2019-11-02 Thread Jerry Jensen via use-livecode
I have no clue about the intricacies involved, but as a crazy idea to throw out, could you make the source pdf transparent at put it -on top- of the one you generate? .Jerry > On Nov 2, 2019, at 2:24 PM, doc hawk via use-livecode > wrote: > > > On Nov 1, 2019, at 5:42 PM, Mark mentioned, >

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

2019-11-02 Thread doc hawk via use-livecode
On Nov 1, 2019, at 5:42 PM, Mark mentioned, > > Is it possible to pick up the background color from the mouseColor or the > backgroundColor or something and set the background color of the field to > that? (and obviously forget the bit about setting the blendlevel) The problem there is that

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

2019-11-02 Thread Niggemann, Bernd via use-livecode
What happens when you set the opaque of group "oGrp" to false? Richard E. Hawkins, Esq. wrote: I’m printing each LC page with set the backgroundColor of otCd to empty set the opaque of group "oGrp" to true set the blendlevel of group "oGrp" to 100 set the blendlevel of otCd to 100 print

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

2019-11-01 Thread Mark Wieder via use-livecode
On 11/1/19 5:27 PM, Dr. Hawkins via use-livecode wrote: Now my head is spinning . . . anything more you can tell me beyond what the dictionary says would help, as my head is spinning . . . Yeah, now that I think back on this the blendlevel would make the text transparent as well as the

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

2019-11-01 Thread Dr. Hawkins via use-livecode
On Nov 1, 2019, at 4:37 PM, Mark Wieder via use-livecode wrote: > > Untested, but maybe setting the opaques to true and the blendlevel to 100? A > bit counerintuitive, but ya never know... No less intuitive than there being fundamental technical reasons that it was necessary to sacrifice

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

2019-11-01 Thread Mark Wieder via use-livecode
While on screen, my generated objects act correctly, being just black text with transparent background. When merging, though, the livecode pdf has grey instead of clear for the entire object generated with print to pdf. Untested, but maybe setting the opaques to true and the blendlevel

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

2019-11-01 Thread doc hawk via use-livecode
On Nov 1, 2019, at 10:03 AM, Richard rumbled > > I'm certain that I don't understand the layout, because from the description > it sounds like you have an object which is not visible and therefore cannot > be printed but which is causing a problem when printed. > > I'm sure you've considered

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

2019-11-01 Thread Richard Gaskin via use-livecode
doc hawk wrote: > On Oct 31, 2019, at 5:42 PM, J. Landman Gay wrote: >> >> A light gray is the system default on OS X windows. You might have >> better luck setting the stack background to opaque and white > > But if the background is opaque, it will block the text underneath > it for the

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

2019-10-31 Thread doc hawk via use-livecode
On Oct 31, 2019, at 5:42 PM, J. Landman Gay via use-livecode wrote: > > A light gray is the system default on OS X windows. You might have better > luck setting the stack background to opaque and white. But take that with a > grain of salt, I've never done what you're attempting. But if

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

2019-10-31 Thread J. Landman Gay via use-livecode
A light gray is the system default on OS X windows. You might have better luck setting the stack background to opaque and white. But take that with a grain of salt, I've never done what you're attempting. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software |

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

2019-10-31 Thread Dr. Hawkins via use-livecode
On Oct 30, 2019, at 10:39 PM, Tom Glod via use-livecode wrote: > Don't things inherit attributes?. so if empty, that means the card > would inherit the stacks background color?? The card and the stack also are set to empty backgroundcolor I’ve also set the opaque of stack, card, and

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

2019-10-30 Thread Tom Glod via use-livecode
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 >

"empty" background in printed pdf is actually grey

2019-10-30 Thread Dr. Hawkins via use-livecode
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