Re: One Rect For All specificaiton

More results: I was going “nuts” and results in the simulator seemed to depend on the time of day, current humidity and wind speed and position of the stars at any given moment… making too many changes on each iteration is dangerous… I narrowed it down: setting the bottom of a control

Re: [BUG] write to file

On Tue, Jan 26, 2016 at 9:49 AM, Richard Gaskin wrote: > > Good find. How did you come across that bit of archaeology? Not that good, what you really need to know is whether the enhancement request was ever actioned. I was searching the QCC DB to ensure I wasn't

Re: [BUG] write to file

I do the same if I am modifying a specific line in an existing file. However, if I am appending to a file such as for logging, I use the before or after modifiers in a file URL. put "Log entry data" after URL ("file:" & specialFolderPath("documents") & tLogFileName) ~Roger On Mon, Jan 25, 2016

Re: [BUG] write to file

It probably hasn't broken mine because I don't rely on the file pointers. I always read the entire file, modify, then write the entire container back. On Sun, Jan 24, 2016 at 10:46 PM, Kay C Lan wrote: > The Dictionary says that if I open a file for 'update', then

Re: [BUG] write to file

I may be wrong, but I think they've made the URL syntax smarter because it sure is fast enough for me, even on fairly large log files. ~Roger On Mon, Jan 25, 2016 at 12:36 PM, J. Landman Gay wrote: > I'm not the team, but logic tells me that opening a file for append

Re: One Rect For All specificaiton

Were the tools part of the card, or other stacks? If they’re part of the card then they add to the width, making it more than 16:9. Even if they’re other stacks it could force it to become part of the showAll area. In other words, if you’re using showAll, don’t use clever code to position the

Re: [BUG] write to file

On 1/24/2016 9:46 PM, Kay C Lan wrote: The Dictionary says that if I open a file for 'update', then 'read from file' to a specific position that when I 'write to file' it will occur at the position I've read to but that's not what I'm seeing in 6.6.5GM, 7.1.1 rc4 and 8.0 dp13 - OS X 10.9.5. In

Re: [BUG] write to file

Roger Eller wrote: > I do the same if I am modifying a specific line in an existing file. > However, if I am appending to a file such as for logging, I use the > before or after modifiers in a file URL. > > put "Log entry data" after URL ("file:" &> specialFolderPath("documents") &

Love, love, love the idea of a business plan tool kit in LiveCode with SLIDERS

Mark Rauterkus wrote > I really love the idea of a set of sliders that can help to set a number of units > (widgets, costs, sales, expenses) and have them display numbers and > projections in other line items. > > For example, > > If I have 200 kids in our water polo

Re: [BUG] write to file

Kay C Lan wrote: > The Dictionary says that if I open a file for 'update', then 'read > from file' to a specific position that when I 'write to file' it > will occur at the position I've read to but that's not what I'm > seeing in 6.6.5GM, 7.1.1 rc4 and 8.0 dp13 - OS X 10.9.5. In the > msg box:

Re: [BUG] write to file

I'm not the team, but logic tells me that opening a file for append will always be faster and more efficient because the URL syntax works as a container, like a field or a variable. Every time you reference a URL, the entirety is read into RAM. I've always used "open for append" for that reason

Re: One Rect For All specificaiton

I've moved a 16:9 stack to Android and the problem with right/left edges wasn't minor. There was a significant gap at the edges that made toolbars and images appear to be hanging in space. I think the general rule to use 75% of the internal area for the content will probably translate to

Re: One Rect For All specificaiton

On 1/25/2016 2:59 PM, Colin Holgate wrote: With showAll, I wouldn’t even use code. Have the tools centered in one direction and aligned to the edges in the other direction. If you want tools to hug a corner, then it gets more complicated. For the stack in question, the toolbar needed to

Re: One Rect For All specificaiton

Disclaimer on my “Safe Zone’ stack The initial discovery “target” for that initiative was simply to come up with something to tell our illustrators and artists. I believe the 75% “middle area is your safe zone” but 12.5% top/Bottom (or left-right) holds as an instruction for artists. BUT:

Re: One Rect For All specificaiton

With showAll, I wouldn’t even use code. Have the tools centered in one direction and aligned to the edges in the other direction. If you want tools to hug a corner, then it gets more complicated. > On Jan 25, 2016, at 8:49 PM, Sannyasin Brahmanathaswami > wrote: > >

Re: One Rect For All specificaiton

If I understand what you're trying to do, I accommodate this by designing groups to position themselves when the card is open, using preOpenControl or openControl. Simple example: -- SCRIPT OF TAB BAR GROUP OR SIMILAR on preOpenControl put rect of this card into theRect put item 4 of

Re: One Rect For All specificaiton

On 25/01/2016 9:09 pm, "use-livecode on behalf of Colin Holgate" wrote: >The 4:3 to 16:9 is a range, it¹s not that it only takes care of those two >cases. If you use a 4:3 card and have 16:9 content, on a 16:10 device,

Re: [BUG] write to file

Folks, Richard has confirmed he's not seeing this on Linux. Jacque has confirmed the Bug on OS X. If I can just get a Win user to check I'll then add a Bug report. So please Win users can you, in the msg box: >> >> set the defaultFolder to specialFolderPath("documents") >> put "trash this

Re: [BUG] write to file

I've gone ahead and added a Bug report 16761. When a Windows user report back I'll add it - or they can add to the report themselves. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage

Sending emails, with attachments, on your server

Folks: I’ve put together a little tutorial stack for those who want to send email from their server, rather than from the user’s local email system. This can be very useful when users sit at different and possibly public computers, where there may be no email system installed, or where the

Re: One Rect For All specificaiton

The 4:3 to 16:9 is a range, it’s not that it only takes care of those two cases. If you use a 4:3 card and have 16:9 content, on a 16:10 device, you’ll see most of the 16:9 content. There are cases where a device might exceed 16:9. For example, a 16:9 device that is showing some sort of

[ANN] This Week in LiveCode 17

Hi all, Read about new developments in LiveCode open source and the open source community in today's edition of the "This Week in LiveCode" newsletter! Read issue #15 here: https://goo.gl/9sy2fM This is a weekly newsletter about LiveCode, focussing on what's been going on in and around

Re: [BUG] write to file

Kay C Lan wrote: > On Mon, Jan 25, 2016 at 11:49 PM, Richard Gaskin wrote: >> >> > put "Log entry data" after URL ("file:" &> >> specialFolderPath("documents") & tLogFileName) >> >> When using the statement above, is the engine clever enough to use an >> append operation for that, or does it