thanks for these mark...they will be an interesting read.
On Wed, Oct 30, 2019 at 12:56 PM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Pure heresy! I CAN write perfect code first time every time! I just have
> to try harder!! ;-)
>
> Bob S
>
>
> > On Oct 30, 2019, at
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
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 |
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
Brian Milby wrote:
> https://github.com/livecode/livecode/pull/7214
>
> We'll see where it goes this time...
Thank you, Brian. This is a good step forward for the usability of the
language.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile,
https://github.com/livecode/livecode/pull/7214
We'll see where it goes this time...
On Thu, Oct 31, 2019 at 12:27 PM Brian Milby wrote:
> I’ll submit a PR tonight.
>
> Thanks,
> Brian
> On Oct 31, 2019, 12:26 PM -0400, Richard Gaskin via use-livecode <
> use-livecode@lists.runrev.com>, wrote:
Whoops! I forgot one important thing:
global gBuildingStandalone
Bob S
> On Oct 31, 2019, at 15:12 , Bob Sneidar via use-livecode
> wrote:
>
> Here's what I do. In the stackScript of the mainStack:
>
> on savingStandalone
> put true into gBuildingStandAlone
> end savingStandalone
There is a set of commands that in certain scripts like opesStack and
closeStack that will check to see if the standalone builder is running, and
then you can abort the handler.
The reason they do this is because your app could be doing anything at the
moment the standalone is being built.
There is a breaking change in 9 where lock messages is no longer issued when
closing and opening the stacks as a part of the build process. There is some
suggested code around. It revolves around testing for being in the build
process for the (pre)openXxx messages. That May be the issue you
I am having an issue with using "any" business version of 9 (9.04, 9.05,
9.5-32bit, 9.5-64bit) to generate a standalone output of my application. I am
using Windows 7 Enterprise SP1 and have tried building the identical script
(with the same result) on two different installations of said OS on
Hi Bob,
> Am 31.10.2019 um 20:03 schrieb Bob Sneidar via use-livecode
> :
>
> OK New version with error checking, and also addresses the issue where Klaus
> could not compile:
>
> on exportScaledImage pSourceFile, pDestFile, pScaleFactor, pFormat
> -- Validate parameters
> -- pSourceFile
OK New version with error checking, and also addresses the issue where Klaus
could not compile:
on exportScaledImage pSourceFile, pDestFile, pScaleFactor, pFormat
-- Validate parameters
-- pSourceFile
if not there is a file pSourceFile then \
answer error "Source file does not
I should put a disclaimer in the comments of any code I write:
Note: The Author is not responsible for the loss of functionality or any
consequences derived from to the alteration of any segment of this code.
:-)
Bob S
> On Oct 31, 2019, at 10:37 , Bob Sneidar wrote:
>
> You removed the
You removed the parenthesis. PUT 'EM BACK! LOL!
Bob S
> On Oct 31, 2019, at 10:34 , Klaus major-k via use-livecode
> wrote:
>
> Hi all,
>
>> On Oct 31, 2019, at 10:01 , Klaus major-k via use-livecode
>> wrote:
>>>
>>> Hi Bob,
>>>
Am 31.10.2019 um 16:00 schrieb Bob Sneidar via
Hi all,
> On Oct 31, 2019, at 10:01 , Klaus major-k via use-livecode
> wrote:
>>
>> Hi Bob,
>>
>>> Am 31.10.2019 um 16:00 schrieb Bob Sneidar via use-livecode
>>> :
>>>
>>> Or better yet: -- No error checking, assumes parameters are correct. Also
>>> not tested. :-)
>>>
>>> on
> Am 31.10.2019 um 18:22 schrieb Bob Sneidar via use-livecode
> :
>
> BTW do you use strict variables?
NEVER! :-)
> Bob S
>
>> On Oct 31, 2019, at 10:20 , Bob Sneidar via use-livecode
>> wrote:
>>
>> Me too. I just tested it and got a 50% scaled image as a JPEG file. Let me
>> try
BTW do you use strict variables?
Bob S
> On Oct 31, 2019, at 10:20 , Bob Sneidar via use-livecode
> wrote:
>
> Me too. I just tested it and got a 50% scaled image as a JPEG file. Let me
> try sending it to you again private email.
>
> Bob S
Me too. I just tested it and got a 50% scaled image as a JPEG file. Let me try
sending it to you again private email.
Bob S
> On Oct 31, 2019, at 10:07 , Klaus major-k via use-livecode
> wrote:
>
>
>
>> Am 31.10.2019 um 18:04 schrieb Bob Sneidar via use-livecode
>> :
>>
>> When you
> Am 31.10.2019 um 18:04 schrieb Bob Sneidar via use-livecode
> :
>
> When you call the command or when you save the script?
when hitting ENTER in the script editor = compiling
> Mine compiled.
???
I use LC 9.5 on macOS 10.14.6
> In any case I'll update it to use DO.
>
> Bob S
> ...
>>
When you call the command or when you save the script? Mine compiled. In any
case I'll update it to use DO.
Bob S
> On Oct 31, 2019, at 10:01 , Klaus major-k via use-livecode
> wrote:
>
> Hi Bob,
>
>> Am 31.10.2019 um 16:00 schrieb Bob Sneidar via use-livecode
>> :
>>
>> Or better yet:
Possibly, but then where is the original file? And why make a new file when
closed without saving?
Bob S
> On Oct 31, 2019, at 09:54 , J. Landman Gay via use-livecode
> wrote:
>
> Or could this be a result of OS Xs decision to save iterative versions of a
> file whether you want it to or
Hi Bob,
> Am 31.10.2019 um 16:00 schrieb Bob Sneidar via use-livecode
> :
>
> Or better yet: -- No error checking, assumes parameters are correct. Also not
> tested. :-)
>
> on exportScaledImage pSourceFile, pDestFile, pScaleFactor, pFormat
> ...
> switch pFormat
> case "JPEG"
>
Or could this be a result of OS Xs decision to save iterative versions of a
file whether you want it to or not?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On October 31, 2019 11:46:29 AM Richard Gaskin via use-livecode
wrote:
Bob Sneidar wrote:
> I would expect I could open a file to look at it, close it without
> saving, and absolutely nothing would change. But it does.
>
> I know this because I tested it with one of the aforementioned Address
> Book Export files. I exported the file, then imported it without
>
The "import snapshot" command had an "at size" option added several
versions ago to facilitate some scaling tasks:
import snapshot from the selectedObject at size 100,100
But oddly, no such option has been added to the "export snapshot" command.
--
Richard Gaskin
Fourth World Systems
I gave the wrong impression. I was saying that other apps and it perhaps the OS
X system itself takes liberties with conversion of line endings. For instance,
Mocrosoft Word and Excel. I would expect I could open a file to look at it,
close it without saving, and absolutely nothing would
I’ll submit a PR tonight.
Thanks,
Brian
On Oct 31, 2019, 12:26 PM -0400, Richard Gaskin via use-livecode
, wrote:
> Ben Rubinstein wrote:
>
> > Brian Milby wrote:
> > > My suggestion is to just bite the bullet and build LC where 'file'
> > > exports using LF on Mac
> >
> > Oh please yes!
>
>
Ben Rubinstein wrote:
> Brian Milby wrote:
>> My suggestion is to just bite the bullet and build LC where 'file'
>> exports using LF on Mac
>
> Oh please yes!
Seconded.
Containing the scope of the remedy to text writes should affect very
few, and those affected will probably welcome the
Hi Ben,
> Am 31.10.2019 um 16:16 schrieb Ben Rubinstein via use-livecode
> :
>
>> My suggestion is to just bite the bullet and build LC where 'file' exports
>> using LF on Mac
> Oh please yes!
> It's been 18 years since the Mac standardised on LF. (And AFAIK Metacard only
> started supporting
My suggestion is to just bite the bullet and build LC where 'file' exports
using LF on Mac
Oh please yes!
It's been 18 years since the Mac standardised on LF. (And AFAIK Metacard only
started supporting the Mac eight years before that, so
Metacard/Revolution/LiveCode has already been writing
Or better yet: -- No error checking, assumes parameters are correct. Also not
tested. :-)
on exportScaledImage pSourceFile, pDestFile, pScaleFactor, pFormat
## My good ol' banana, older users of MC might remember that one :-D
set the filename of the templateimage to pSourceFile
##
Not to disagree, but just to mention this is not exclusive to LC. If I download
the address book of a Toshiba copier, then just OPEN it with Microsoft Office
ot TextEdit, then close without saving, I can no longer import that file into
the copier again.
Upon examining the ascii value of every
Interesting. This may be why when I copy code from the SE and paste it into an
email I get double line spacing.
Bob S
> On Oct 30, 2019, at 19:08 , Brian Milby via use-livecode
> wrote:
>
> The reason for the difficulty is that internally LC uses LF as the line
> ending. The cr, lf, and
33 matches
Mail list logo
