Re: Levure - flicker prior to displaying UI stack on iOS
On Tue, Jun 5, 2018 at 4:57 PM, Ralf Bitter via use-livecode < use-livecode@lists.runrev.com> wrote: > thanks a lot for offering your help. The test project > to demonstrate the issue is available at: > > https://spideroak.com/browse/share/soRabit/trevorSharing I’ve go the file Ralf. I’ll take a look at it tomorrow and let you know what I find out. -- Trevor DeVore ScreenSteps www.screensteps.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
Re: Datagrid selectionChanged bug?
On Tue, Jun 5, 2018 at 5:27 PM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > > I suppose I can get around it by using send in time so the actual > selectionChanged handler finishes before the cascade of form updates > happens. But if it is a bug and shouldn't be happening, I suppose I should > try to make a stack that reproduces it. (I may have already done so but I > don't keep track of my own bug reports!) > The issue you are seeing is probably caused by the inability of the engine to delete the object that is the target of the current event. When you replace the data grid contents during selectionChanged you are trying to delete the control that was clicked on and trigger the selectionChanged message. The engine doesn’t like that. You will need to use `send in time` to accomplish what you are after. -- Trevor DeVore ScreenSteps www.screensteps.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
Re: Differences between Commercial and Community versions of LiveCode
On 6/5/18 4:20 PM, Tom Glod via use-livecode wrote: so i went to check the standalone file from v9 ...and indeed the code cannot be seen. in previous versions, I could clearly see the script text of a stack by opening it up in notepad++. maybe i was hallucinating.. but i'm pretty sure i checked this before because of my own curiosities about this subject. can anyone confirm this change? Yes, scripts in standalones used to be plain-text but that was a long time ago. It may have been LC 7 where it changed but I think it was even before that. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.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
Re: THOUGHT: the [effective] [working] screenLoc
On 6/5/18 12:32 PM, Paul Dupuis via use-livecode wrote: Alternatively, if a small engine enhancment would give us "the [effective] [working] screenLoc and save the subraction, is it worth asking LiveCode to do it? Of course. It never hurts to ask. Then if LC doesn't do it, it's on them and I'm off the hook. :) -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.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
Re: Differences between Commercial and Community versions of LiveCode
Looking at the code, “deflate” is called on the stack as it is being written out (zlib). So while not easy, it should be possible to separate a stack file from the binary if deployed from the community edition. It would take a bit of work to figure out where the file started and ended. Well over what I would be willing to tackle at the moment. For anyone so motivated, the relevant source code is in deploy*.cpp (along with the header files). On Jun 5, 2018, 4:25 PM -0500, Tom Glod via use-livecode , wrote: > h. maybe i'm thinking all the way back to v6 or v7 standalones. cuz > v8 is also not visible. > > On Tue, Jun 5, 2018 at 5:20 PM, Tom Glod wrote: > > > so i went to check the standalone file from v9 ...and indeed the code > > cannot be seen. in previous versions, I could clearly see the script text > > of a stack by opening it up in notepad++. > > > > maybe i was hallucinating.. but i'm pretty sure i checked this before > > because of my own curiosities about this subject. can anyone confirm this > > change? > > > > > > On Tue, Jun 5, 2018 at 3:49 PM, Brian Milby via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > > > I believe this thread started as a result is someone asking if there was > > > a way to recover their work if all they could salvage was a built binary > > > (from community edition). It sounds like there should be a way based on > > > another response in the thread. > > > > > > Thanks, > > > Brian > > > On Jun 5, 2018, 2:16 PM -0500, Richard Gaskin via use-livecode < > > > use-livecode@lists.runrev.com>, wrote: > > > > Richmond Mathewson wrote: > > > > > > > > > Recently I ran off a very simple standalone with the Indy and the > > > > > Community version of LC 8.1.9 > > > > > and cracked both of them open with a text editor. > > > > > > > > > > In neither of the standalones could I access the code. > > > > > > > > > > Presumably this means that a standalone generated with the Community > > > > > version cannot be > > > > > reverse-engineered in such a way that its original code can be read? > > > > > > > > Binding the stack to the runtime engine makes the source difficult to > > > > access, and the objects impossible to modify. > > > > > > > > The requirement of GPL-governed works is that source code is available > > > > in a form that allows modification. > > > > > > > > I would not imagine requiring end-users to sift through bits of a binary > > > > executable would satisfy any definition of GPL compliance. > > > > > > > > Either the source stack files are made available to any user of the > > > > executable who wants them, or the entity distributing the executable is > > > > in violation of LiveCode Ltd's copyright. > > > > > > > > -- > > > > Richard Gaskin > > > > Fourth World Systems > > > > Software Design and Development for the Desktop, Mobile, and the Web > > > > > > > > ambassa...@fourthworld.com http://www.FourthWorld.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 > > > ___ > > > 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
Datagrid selectionChanged bug?
Hi all. What I once thought was an endless loop bug I have isolated now to something else. It seems that when selectionChanged for a datagrid is in the executionContexts, the dgData must not be changed. I am not sure if this causes an endless loop internally to the datagrid library or not. All I know is that I immediately CTD if I do it. What I want to know is if this is "unexpected behavior" or if I am just doing something stupid. I won't go too deep into the weeds on why this is an issue with me, but to give you an idea, I have a search mechanism that will populate a datagrid (say a device or devices that match my search criteria) when text is entered into a field. When the user clicks on the device, I must go back to the customer and sites and yes, the devices and reload the data for all of them. Everything works as it should up until I attempt to set the dgData for the device datagrid to ALL the devices for that site. Since the selectionChanged handler in the devices datagrid started the whole cascading effect, that handler is still running when the data gets swapped out. I suppose I can get around it by using send in time so the actual selectionChanged handler finishes before the cascade of form updates happens. But if it is a bug and shouldn't be happening, I suppose I should try to make a stack that reproduces it. (I may have already done so but I don't keep track of my own bug reports!) Bob S ___ 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: Levure - flicker prior to displaying UI stack on iOS
Hi Trevor, thanks a lot for offering your help. The test project to demonstrate the issue is available at: https://spideroak.com/browse/share/soRabit/trevorSharing Ralf > On 5. Jun 2018, at 21:15, Trevor DeVore via use-livecode > wrote: > > Can you upload a test stack for me to look at? If it is easy for me to > replicate I should be able to figure out what is going on. ___ 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: Differences between Commercial and Community versions of LiveCode
h. maybe i'm thinking all the way back to v6 or v7 standalones. cuz v8 is also not visible. On Tue, Jun 5, 2018 at 5:20 PM, Tom Glod wrote: > so i went to check the standalone file from v9 ...and indeed the code > cannot be seen. in previous versions, I could clearly see the script text > of a stack by opening it up in notepad++. > > maybe i was hallucinating.. but i'm pretty sure i checked this before > because of my own curiosities about this subject. can anyone confirm this > change? > > > On Tue, Jun 5, 2018 at 3:49 PM, Brian Milby via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> I believe this thread started as a result is someone asking if there was >> a way to recover their work if all they could salvage was a built binary >> (from community edition). It sounds like there should be a way based on >> another response in the thread. >> >> Thanks, >> Brian >> On Jun 5, 2018, 2:16 PM -0500, Richard Gaskin via use-livecode < >> use-livecode@lists.runrev.com>, wrote: >> > Richmond Mathewson wrote: >> > >> > > Recently I ran off a very simple standalone with the Indy and the >> > > Community version of LC 8.1.9 >> > > and cracked both of them open with a text editor. >> > > >> > > In neither of the standalones could I access the code. >> > > >> > > Presumably this means that a standalone generated with the Community >> > > version cannot be >> > > reverse-engineered in such a way that its original code can be read? >> > >> > Binding the stack to the runtime engine makes the source difficult to >> > access, and the objects impossible to modify. >> > >> > The requirement of GPL-governed works is that source code is available >> > in a form that allows modification. >> > >> > I would not imagine requiring end-users to sift through bits of a binary >> > executable would satisfy any definition of GPL compliance. >> > >> > Either the source stack files are made available to any user of the >> > executable who wants them, or the entity distributing the executable is >> > in violation of LiveCode Ltd's copyright. >> > >> > -- >> > Richard Gaskin >> > Fourth World Systems >> > Software Design and Development for the Desktop, Mobile, and the Web >> > >> > ambassa...@fourthworld.com http://www.FourthWorld.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 >> ___ >> 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: Differences between Commercial and Community versions of LiveCode
so i went to check the standalone file from v9 ...and indeed the code cannot be seen. in previous versions, I could clearly see the script text of a stack by opening it up in notepad++. maybe i was hallucinating.. but i'm pretty sure i checked this before because of my own curiosities about this subject. can anyone confirm this change? On Tue, Jun 5, 2018 at 3:49 PM, Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > I believe this thread started as a result is someone asking if there was a > way to recover their work if all they could salvage was a built binary > (from community edition). It sounds like there should be a way based on > another response in the thread. > > Thanks, > Brian > On Jun 5, 2018, 2:16 PM -0500, Richard Gaskin via use-livecode < > use-livecode@lists.runrev.com>, wrote: > > Richmond Mathewson wrote: > > > > > Recently I ran off a very simple standalone with the Indy and the > > > Community version of LC 8.1.9 > > > and cracked both of them open with a text editor. > > > > > > In neither of the standalones could I access the code. > > > > > > Presumably this means that a standalone generated with the Community > > > version cannot be > > > reverse-engineered in such a way that its original code can be read? > > > > Binding the stack to the runtime engine makes the source difficult to > > access, and the objects impossible to modify. > > > > The requirement of GPL-governed works is that source code is available > > in a form that allows modification. > > > > I would not imagine requiring end-users to sift through bits of a binary > > executable would satisfy any definition of GPL compliance. > > > > Either the source stack files are made available to any user of the > > executable who wants them, or the entity distributing the executable is > > in violation of LiveCode Ltd's copyright. > > > > -- > > Richard Gaskin > > Fourth World Systems > > Software Design and Development for the Desktop, Mobile, and the Web > > > > ambassa...@fourthworld.com http://www.FourthWorld.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 > ___ > 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: THOUGHT: the [effective] [working] screenLoc
subtraction Or addition! Best wishes, Curry K. ___ 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: Differences between Commercial and Community versions of LiveCode
I believe this thread started as a result is someone asking if there was a way to recover their work if all they could salvage was a built binary (from community edition). It sounds like there should be a way based on another response in the thread. Thanks, Brian On Jun 5, 2018, 2:16 PM -0500, Richard Gaskin via use-livecode , wrote: > Richmond Mathewson wrote: > > > Recently I ran off a very simple standalone with the Indy and the > > Community version of LC 8.1.9 > > and cracked both of them open with a text editor. > > > > In neither of the standalones could I access the code. > > > > Presumably this means that a standalone generated with the Community > > version cannot be > > reverse-engineered in such a way that its original code can be read? > > Binding the stack to the runtime engine makes the source difficult to > access, and the objects impossible to modify. > > The requirement of GPL-governed works is that source code is available > in a form that allows modification. > > I would not imagine requiring end-users to sift through bits of a binary > executable would satisfy any definition of GPL compliance. > > Either the source stack files are made available to any user of the > executable who wants them, or the entity distributing the executable is > in violation of LiveCode Ltd's copyright. > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > > ambassa...@fourthworld.com http://www.FourthWorld.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 ___ 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: Differences between Commercial and Community versions of LiveCode
Richmond Mathewson wrote: > Recently I ran off a very simple standalone with the Indy and the > Community version of LC 8.1.9 > and cracked both of them open with a text editor. > > In neither of the standalones could I access the code. > > Presumably this means that a standalone generated with the Community > version cannot be > reverse-engineered in such a way that its original code can be read? Binding the stack to the runtime engine makes the source difficult to access, and the objects impossible to modify. The requirement of GPL-governed works is that source code is available in a form that allows modification. I would not imagine requiring end-users to sift through bits of a binary executable would satisfy any definition of GPL compliance. Either the source stack files are made available to any user of the executable who wants them, or the entity distributing the executable is in violation of LiveCode Ltd's copyright. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.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
Re: Levure - flicker prior to displaying UI stack on iOS
On Tue, Jun 5, 2018 at 12:36 PM, Ralf Bitter via use-livecode < use-livecode@lists.runrev.com> wrote: > Currently I am developing an iOS app for iPad using > Trevor DeVore’s awesome Levure framework. > I’m glad you like it. > Unfortunately I am observing an annoying screen flicker > during the startup sequence while the UI stack is opened > and the Levure standalone is closed. > The iOS splash screen, as defined in settings, is shown, > then for a fraction of a second the screen is black just before > the UI stack becomes visible. This happens not only in the > simulator but on a real device (iPad Pro) too. > > Can you upload a test stack for me to look at? If it is easy for me to replicate I should be able to figure out what is going on. -- Trevor DeVore ScreenSteps www.screensteps.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
Re: Differences between Commercial and Community versions of LiveCode
Thanks: very useful information. Richmond. On 5/6/2018 10:08 pm, Tom Glod via use-livecode wrote: if u open up a lc standalone exe in a hex editor or even notepad++ you can totally read the code contained. at least it used to be the case before v9 (haven't looked) maybe your text editor wasn't able to display the code in some way but I assure you its there. Not so the case for non community stacks. those are encrypted. On Tue, Jun 5, 2018 at 3:05 PM, Richmond Mathewson via use-livecode < use-livecode@lists.runrev.com> wrote: On LiveCode's webpage there is a chart of differences between the Commercial veriosn and the Community version. I was given to understand one of the most important differences was that, in the Commercial versions, code in standalones was "obfuscated" in such a way that an end-user could not "peek round the back" and access that code. Recently I ran off a very simple standalone with the Indy and the Community version of LC 8.1.9 and cracked both of them open with a text editor. In neither of the standalones could I access the code. Presumably this means that a standalone generated with the Community version cannot be reverse-engineered in such a way that its original code can be read? Richmond. ___ 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: Differences between Commercial and Community versions of LiveCode
if u open up a lc standalone exe in a hex editor or even notepad++ you can totally read the code contained. at least it used to be the case before v9 (haven't looked) maybe your text editor wasn't able to display the code in some way but I assure you its there. Not so the case for non community stacks. those are encrypted. On Tue, Jun 5, 2018 at 3:05 PM, Richmond Mathewson via use-livecode < use-livecode@lists.runrev.com> wrote: > On LiveCode's webpage there is a chart of differences between the > Commercial veriosn > and the Community version. > > I was given to understand one of the most important differences was that, > in the Commercial versions, > code in standalones was "obfuscated" in such a way that an end-user could > not "peek round the back" > and access that code. > > Recently I ran off a very simple standalone with the Indy and the > Community version of LC 8.1.9 > and cracked both of them open with a text editor. > > In neither of the standalones could I access the code. > > Presumably this means that a standalone generated with the Community > version cannot be > reverse-engineered in such a way that its original code can be read? > > Richmond. > ___ > 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
Differences between Commercial and Community versions of LiveCode
On LiveCode's webpage there is a chart of differences between the Commercial veriosn and the Community version. I was given to understand one of the most important differences was that, in the Commercial versions, code in standalones was "obfuscated" in such a way that an end-user could not "peek round the back" and access that code. Recently I ran off a very simple standalone with the Indy and the Community version of LC 8.1.9 and cracked both of them open with a text editor. In neither of the standalones could I access the code. Presumably this means that a standalone generated with the Community version cannot be reverse-engineered in such a way that its original code can be read? Richmond. ___ 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
Levure - flicker prior to displaying UI stack on iOS
Currently I am developing an iOS app for iPad using Trevor DeVore’s awesome Levure framework. Unfortunately I am observing an annoying screen flicker during the startup sequence while the UI stack is opened and the Levure standalone is closed. The iOS splash screen, as defined in settings, is shown, then for a fraction of a second the screen is black just before the UI stack becomes visible. This happens not only in the simulator but on a real device (iPad Pro) too. Did tests using a very simple UI stack, no code included, just one card showing an image which is the same as the splash screen so that the transition from the splash screen to the UI stack should not be noticeable. Probably this is not a Levure issue, may be this is the way splash stack project setups behave on iOS. Anyway, does anybody know how this flicker can be avoided? Would be a great pity if I would have to ditch the Levure route. Ralf ___ 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: THOUGHT: the [effective] [working] screenLoc
All the proverbs are true. Still the core question is there. For those who may want to center a dialog in the working area of the screen, they can calculate that themselves in a home built function (or code snippet) by fetching the "effective working screenRect" and subtracting top from bottom and right from left to get a center point. Alternatively, if a small engine enhancment would give us "the [effective] [working] screenLoc and save the subraction, is it worth asking LiveCode to do it? On 6/5/2018 5:30 AM, Lagi Pittas via use-livecode wrote: > Hi > > > here's the third one I missed > > "Make something idiot-proof, and they will build a better idiot." > > It's a losing battle > > Lagi > > >>> Nothing can be made foolproof because fools are so ingenious. >>> Nothing is foolproof for a capable fool. >>> >>> Lagi >>> >>> >>> On 4 June 2018 at 20:51, Paul Dupuis via use-livecode < >>> use-livecode@lists.runrev.com> wrote: >>> >>> Okay, we're making progress: 2 people (Paul and Ralph) think having "the [effective] [working] screenLoc" might be a useful addition for the language for the likely effort to add it 2 people (Bob and Jacqueline) think that it is simple enough (which it is) to write your own function for this it is not worth the effort to add to the engine So far we have a tie. And, Jacqueline, screen resolutions can be changed dynamically on Windows (can't remember off the top of my head if the same is true for OSX). This changes the screenLoc. We also have customers who use multiple monitors, unplug them abruptly, change screen resolutions dynamically (say to connect to a projector) and so on, so are trying to make use of LC features like the desktopChanged message to recheck screen sizes and adjust windows in our app accordingly or re-position windows or recenter dialogs when a monitor is removed suddenly. Some user have "fat" taskbars (a lot of open stuff on them since the Windows toolbar can be resized) and the center of the working screen area is decidedly not the center of the current resolution of the primary monitor. In fact, the Windows taskbar can be resize to take up half the primary screen by the user (we have NOT had any one do that - YET) On 6/4/2018 12:07 PM, Paul Dupuis via use-livecode wrote: > Yes, that is why I said (read below) that if others did not think there > should be an effective and/or working key word for the screenLoc > function, I would roll my own based on the screenRect function. I was > asking whether other think the screenLoc function should or should not > have these keywords. > > > On 6/4/2018 11:55 AM, Bob Sneidar via use-livecode wrote: > >> Seems like you could subtract item 1 from item 3 and item 2 from item 4 >> > of the effective screenRect to get what you need. > Bob S >> >> On Jun 4, 2018, at 08:08 , Paul Dupuis via use-livecode < >> use-livecode@lists.runrev.com> wrote: > I posted the question below and got no responses so I thought I would >>> try again. >>> >>> I noticed that screenLoc has no effective or working keywords >>> >> associated > with it in LC9 or earlier. It seems to me that it should and that if it >>> has been done for the screenRect(s), it should be a small enhancement >>> >> to > add them to the screenLoc >>> Do others agree? If so I will submit and enhancement entry to the >>> quality center. if not, I'll drop this discussion thread and roll my >>> >> own > function based on the screenRect function. >> ___ >> 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
Re: Siva Siva App in iOS version 1.2 in now out
> On Jun 5, 2018, at 09:22 , Mark Wieder via use-livecode > wrote: > > On 06/05/2018 09:08 AM, J. Landman Gay via use-livecode wrote: >> On June 5, 2018 10:27:50 AM Sannyasin Brahmanathaswami via use-livecode >> wrote: >>> And believe me, people really code is different styles! >> I'll say. It's like handwriting, if you know someone's style you can often >> determine who wrote the code just by reading it. We all have our little >> conventions. > > Yeah. > You can tell my code because it's perfct. > > -- > 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
Re: Siva Siva App in iOS version 1.2 in now out
On 06/05/2018 09:08 AM, J. Landman Gay via use-livecode wrote: On June 5, 2018 10:27:50 AM Sannyasin Brahmanathaswami via use-livecode wrote: And believe me, people really code is different styles! I'll say. It's like handwriting, if you know someone's style you can often determine who wrote the code just by reading it. We all have our little conventions. Yeah. You can tell my code because it's perfct. -- 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
Re: Siva Siva App in iOS version 1.2 in now out
On June 5, 2018 10:27:50 AM Sannyasin Brahmanathaswami via use-livecode wrote: And believe me, people really code is different styles! I'll say. It's like handwriting, if you know someone's style you can often determine who wrote the code just by reading it. We all have our little conventions. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.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
Re: Message when moving windows
That’s it! Thanks. > On Jun 5, 2018, at 12:50 AM, Richmond via use-livecode > wrote: > > on moveStack LR, UD > > put "You moved me!" > > end moveStack > > Richmond. > > On 5.06.2018 10:12, Peter Bogdanoff via use-livecode wrote: >> Hi, >> >> Is there a message sent in LiveCode when the user moves an LC window around >> using the titlebar? >> >> I want to set a preference setting when this happens. I know I could do this >> when windows are closed, for for my situation it would be much better to do >> it immediately, if it’s possible. >> >> Peter Bogdanoff >> ArtsInteractive >> ___ >> 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: Siva Siva App in iOS version 1.2 in now out
Hi Brahmanathaswami, Congratulations for the release. Just a quick note for the landscape issue on Android, this is now fixed and it will be available in the next LC 9 release (9.0.1 RC-1): https://quality.livecode.com/show_bug.cgi?id=19465 Best, Panos -- On Tue, Jun 5, 2018 at 4:25 PM, Sannyasin Brahmanathaswami via use-livecode wrote: > It been many moons. I finally got a new version SivaSiva out the door to > iOS. > > I want to especially thank an unsung hero that is busy in Edinburgh > helping with support requests for business. > > Elanor Buchanan! Yay! > > She responsible is for the new "Listen" touch code for the new audio > screen. With icons for collections that go left and right and and up down. > Just like Spotify! I use a single json file to build that interface in > development and then to run it in the app. It scrolls *almost* as good an > regular web scrolling. The touch model of that screen is less on 50 lines > of code. > > Thanks also to Jacque for the code for the fetching an .ics file, > download it and display a Hindu Calender (Panchangam) and for Andre, who > did a little "experiment" in the Read Module, Hindu Dictionary, but develop > it as HTML5 that we should show in the browser widget and which > communicates with the local SQLlite database (i.e. it not using web > storage!). > > Given all the year of support from the community, I make the code open > source. > > If you want to check out the app. > > https://github.com/Himalayan-Academy/Siva-Siva-App/tree/nightly > > DISCLAIMER: Its a labyrinth, slowly working to refactor. But, original > decision I made works well: > Different modules are virtually independent, and only require the > developer minimal access global framework. This way I can hire out new > "pieces" (stacks) to people, and they code the way they want. This has pros > and cons. But allows agile development across a team, who doesn't need to > know the conventions of another developer. And believe me, people really > code is different styles! > > DOWNSIDE Side: > > This app would "huge" in gets Android, my target audience is gigantic in > India, Malaysia, Sri Lanka and Singapore.. BUT > > Android: still unresponsive to navigation buttons, move from one stack to > the next is like crap shoot, Seven on good day and snake eyes the next > moment, we have to "minutely" manage accelerateRendering otherwise "all > hell breaks loose" - landscape is not in parity to iOS. I have a landscape > stack, on iOS it switch to landscape. I have browser code that allows you > to rotate the phone.. works on iOS, but does not on android. 8.1.10 > mobileSetFullScreenRectForOrientations orientations[, rect]. Does not > work as expect (perhaps I am implementing wrongly, TBD) > > OPEN LETTER TO KEVIN: > > We are not in a situation as bad a Sean Cole. Non-profit. And not the same > situation. But I feel for him. If I were an developer depending on Android, > I would be dead the water, belly floating up I have been working TWO > YEARs to get an app that runs fine on iOS and breaks to Android. > > Of course, I would expect a lot "in the platform in Android, then do it > this way" but no such thing... I love the platform. You can "rule world" > with Livecode in just 200 lines. My God! It already does everything, > anything I can think of, I can get it done in 500 line of English readable > code (minus the motion graphics). We don’t need features. Please PLEEZE, > consolidate, put as much effort as you can afford in solving Android bugs. > > Brahmanathaswami > > Get the SivaSiva app, it's free: > https://www.himalayanacademy.com/apps/sivasiva > > ___ > 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
Siva Siva App in iOS version 1.2 in now out
It been many moons. I finally got a new version SivaSiva out the door to iOS. I want to especially thank an unsung hero that is busy in Edinburgh helping with support requests for business. Elanor Buchanan! Yay! She responsible is for the new "Listen" touch code for the new audio screen. With icons for collections that go left and right and and up down. Just like Spotify! I use a single json file to build that interface in development and then to run it in the app. It scrolls *almost* as good an regular web scrolling. The touch model of that screen is less on 50 lines of code. Thanks also to Jacque for the code for the fetching an .ics file, download it and display a Hindu Calender (Panchangam) and for Andre, who did a little "experiment" in the Read Module, Hindu Dictionary, but develop it as HTML5 that we should show in the browser widget and which communicates with the local SQLlite database (i.e. it not using web storage!). Given all the year of support from the community, I make the code open source. If you want to check out the app. https://github.com/Himalayan-Academy/Siva-Siva-App/tree/nightly DISCLAIMER: Its a labyrinth, slowly working to refactor. But, original decision I made works well: Different modules are virtually independent, and only require the developer minimal access global framework. This way I can hire out new "pieces" (stacks) to people, and they code the way they want. This has pros and cons. But allows agile development across a team, who doesn't need to know the conventions of another developer. And believe me, people really code is different styles! DOWNSIDE Side: This app would "huge" in gets Android, my target audience is gigantic in India, Malaysia, Sri Lanka and Singapore.. BUT Android: still unresponsive to navigation buttons, move from one stack to the next is like crap shoot, Seven on good day and snake eyes the next moment, we have to "minutely" manage accelerateRendering otherwise "all hell breaks loose" - landscape is not in parity to iOS. I have a landscape stack, on iOS it switch to landscape. I have browser code that allows you to rotate the phone.. works on iOS, but does not on android. 8.1.10 mobileSetFullScreenRectForOrientations orientations[, rect]. Does not work as expect (perhaps I am implementing wrongly, TBD) OPEN LETTER TO KEVIN: We are not in a situation as bad a Sean Cole. Non-profit. And not the same situation. But I feel for him. If I were an developer depending on Android, I would be dead the water, belly floating up I have been working TWO YEARs to get an app that runs fine on iOS and breaks to Android. Of course, I would expect a lot "in the platform in Android, then do it this way" but no such thing... I love the platform. You can "rule world" with Livecode in just 200 lines. My God! It already does everything, anything I can think of, I can get it done in 500 line of English readable code (minus the motion graphics). We don’t need features. Please PLEEZE, consolidate, put as much effort as you can afford in solving Android bugs. Brahmanathaswami Get the SivaSiva app, it's free: https://www.himalayanacademy.com/apps/sivasiva ___ 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: THOUGHT: the [effective] [working] screenLoc
Hi here's the third one I missed "Make something idiot-proof, and they will build a better idiot." It's a losing battle Lagi >> Nothing can be made foolproof because fools are so ingenious. >> Nothing is foolproof for a capable fool. >> >> Lagi >> >> >> On 4 June 2018 at 20:51, Paul Dupuis via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> >> Okay, we're making progress: >>> >>> 2 people (Paul and Ralph) think having "the [effective] [working] >>> screenLoc" might be a useful addition for the language for the likely >>> effort to add it >>> 2 people (Bob and Jacqueline) think that it is simple enough (which it >>> is) to write your own function for this it is not worth the effort to >>> add to the engine >>> >>> So far we have a tie. >>> >>> And, Jacqueline, screen resolutions can be changed dynamically on >>> Windows (can't remember off the top of my head if the same is true for >>> OSX). This changes the screenLoc. We also have customers who use >>> multiple monitors, unplug them abruptly, change screen resolutions >>> dynamically (say to connect to a projector) and so on, so are trying to >>> make use of LC features like the desktopChanged message to recheck >>> screen sizes and adjust windows in our app accordingly or re-position >>> windows or recenter dialogs when a monitor is removed suddenly. Some >>> user have "fat" taskbars (a lot of open stuff on them since the Windows >>> toolbar can be resized) and the center of the working screen area is >>> decidedly not the center of the current resolution of the primary >>> monitor. In fact, the Windows taskbar can be resize to take up half the >>> primary screen by the user (we have NOT had any one do that - YET) >>> >>> >>> On 6/4/2018 12:07 PM, Paul Dupuis via use-livecode wrote: >>> Yes, that is why I said (read below) that if others did not think there should be an effective and/or working key word for the screenLoc function, I would roll my own based on the screenRect function. I was asking whether other think the screenLoc function should or should not have these keywords. On 6/4/2018 11:55 AM, Bob Sneidar via use-livecode wrote: > Seems like you could subtract item 1 from item 3 and item 2 from item 4 > of the effective screenRect to get what you need. >>> Bob S > > > On Jun 4, 2018, at 08:08 , Paul Dupuis via use-livecode < >> > use-livecode@lists.runrev.com> wrote: >>> I posted the question below and got no responses so I thought I would >> try again. >> >> I noticed that screenLoc has no effective or working keywords >> > associated >>> with it in LC9 or earlier. It seems to me that it should and that if it >> has been done for the screenRect(s), it should be a small enhancement >> > to >>> add them to the screenLoc >> >> Do others agree? If so I will submit and enhancement entry to the >> quality center. if not, I'll drop this discussion thread and roll my >> > own >>> function based on the screenRect function. >> > ___ > 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 > ___ 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: THOUGHT: the [effective] [working] screenLoc
Yes, indeed, and the equivalent sort of thing to the Windows taskbar in the XFCE environment on Linux can be resized to cover the whole screen! I know as my computers in my school have "Peekaboo" taskbars that take up about 40% of the screen (i.e. they pop in and out of the bottom of the screen) with launchers for some 60 EFL programs I have authored for EFL (English as a Fizziy Language). But, fools or not, one cannot plan for all eventualities . . . anymore than a shoe factory can make shoes in giant sizes on the off-chance that Finn MacCool will pop in to buy hisself some baffies! Richmond. On 5/6/2018 12:14 pm, Lagi Pittas via use-livecode wrote: " Windows taskbar can be resize to take up half the primary screen by the user (we have NOT had any one do that - YET)" Which reminds me of 3 variants of Murphy's law :- Nothing can be made foolproof because fools are so ingenious. Nothing is foolproof for a capable fool. Lagi On 4 June 2018 at 20:51, Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote: Okay, we're making progress: 2 people (Paul and Ralph) think having "the [effective] [working] screenLoc" might be a useful addition for the language for the likely effort to add it 2 people (Bob and Jacqueline) think that it is simple enough (which it is) to write your own function for this it is not worth the effort to add to the engine So far we have a tie. And, Jacqueline, screen resolutions can be changed dynamically on Windows (can't remember off the top of my head if the same is true for OSX). This changes the screenLoc. We also have customers who use multiple monitors, unplug them abruptly, change screen resolutions dynamically (say to connect to a projector) and so on, so are trying to make use of LC features like the desktopChanged message to recheck screen sizes and adjust windows in our app accordingly or re-position windows or recenter dialogs when a monitor is removed suddenly. Some user have "fat" taskbars (a lot of open stuff on them since the Windows toolbar can be resized) and the center of the working screen area is decidedly not the center of the current resolution of the primary monitor. In fact, the Windows taskbar can be resize to take up half the primary screen by the user (we have NOT had any one do that - YET) On 6/4/2018 12:07 PM, Paul Dupuis via use-livecode wrote: Yes, that is why I said (read below) that if others did not think there should be an effective and/or working key word for the screenLoc function, I would roll my own based on the screenRect function. I was asking whether other think the screenLoc function should or should not have these keywords. On 6/4/2018 11:55 AM, Bob Sneidar via use-livecode wrote: Seems like you could subtract item 1 from item 3 and item 2 from item 4 of the effective screenRect to get what you need. Bob S On Jun 4, 2018, at 08:08 , Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote: I posted the question below and got no responses so I thought I would try again. I noticed that screenLoc has no effective or working keywords associated with it in LC9 or earlier. It seems to me that it should and that if it has been done for the screenRect(s), it should be a small enhancement to add them to the screenLoc Do others agree? If so I will submit and enhancement entry to the quality center. if not, I'll drop this discussion thread and roll my own function based on the screenRect function. ___ 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: THOUGHT: the [effective] [working] screenLoc
" Windows taskbar can be resize to take up half the primary screen by the user (we have NOT had any one do that - YET)" Which reminds me of 3 variants of Murphy's law :- Nothing can be made foolproof because fools are so ingenious. Nothing is foolproof for a capable fool. Lagi On 4 June 2018 at 20:51, Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote: > Okay, we're making progress: > > 2 people (Paul and Ralph) think having "the [effective] [working] > screenLoc" might be a useful addition for the language for the likely > effort to add it > 2 people (Bob and Jacqueline) think that it is simple enough (which it > is) to write your own function for this it is not worth the effort to > add to the engine > > So far we have a tie. > > And, Jacqueline, screen resolutions can be changed dynamically on > Windows (can't remember off the top of my head if the same is true for > OSX). This changes the screenLoc. We also have customers who use > multiple monitors, unplug them abruptly, change screen resolutions > dynamically (say to connect to a projector) and so on, so are trying to > make use of LC features like the desktopChanged message to recheck > screen sizes and adjust windows in our app accordingly or re-position > windows or recenter dialogs when a monitor is removed suddenly. Some > user have "fat" taskbars (a lot of open stuff on them since the Windows > toolbar can be resized) and the center of the working screen area is > decidedly not the center of the current resolution of the primary > monitor. In fact, the Windows taskbar can be resize to take up half the > primary screen by the user (we have NOT had any one do that - YET) > > > On 6/4/2018 12:07 PM, Paul Dupuis via use-livecode wrote: > > Yes, that is why I said (read below) that if others did not think there > > should be an effective and/or working key word for the screenLoc > > function, I would roll my own based on the screenRect function. I was > > asking whether other think the screenLoc function should or should not > > have these keywords. > > > > > > On 6/4/2018 11:55 AM, Bob Sneidar via use-livecode wrote: > >> Seems like you could subtract item 1 from item 3 and item 2 from item 4 > of the effective screenRect to get what you need. > >> > >> Bob S > >> > >> > >>> On Jun 4, 2018, at 08:08 , Paul Dupuis via use-livecode < > use-livecode@lists.runrev.com> wrote: > >>> > >>> I posted the question below and got no responses so I thought I would > >>> try again. > >>> > >>> I noticed that screenLoc has no effective or working keywords > associated > >>> with it in LC9 or earlier. It seems to me that it should and that if it > >>> has been done for the screenRect(s), it should be a small enhancement > to > >>> add them to the screenLoc > >>> > >>> Do others agree? If so I will submit and enhancement entry to the > >>> quality center. if not, I'll drop this discussion thread and roll my > own > >>> function based on the screenRect function. > >> ___ > >> 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: Message when moving windows
on moveStack LR, UD put "You moved me!" end moveStack Richmond. On 5.06.2018 10:12, Peter Bogdanoff via use-livecode wrote: Hi, Is there a message sent in LiveCode when the user moves an LC window around using the titlebar? I want to set a preference setting when this happens. I know I could do this when windows are closed, for for my situation it would be much better to do it immediately, if it’s possible. Peter Bogdanoff ArtsInteractive ___ 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
Message when moving windows
Hi, Is there a message sent in LiveCode when the user moves an LC window around using the titlebar? I want to set a preference setting when this happens. I know I could do this when windows are closed, for for my situation it would be much better to do it immediately, if it’s possible. Peter Bogdanoff ArtsInteractive ___ 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
Bug 17062 - Browser Widget: Context menu is not under script control
Can someone at LC please bump Bug 17062 and take a look at it? Would be great to be able to pass right-clicks into the browser widget rather than automatically popping up the "Back|Reload" menu. https://quality.livecode.com/show_bug.cgi?id=17228 cheers Alan ___ 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
