Re: Navigator now supports converting controls to script-only stack behaviors

On 01/25/2018 05:25 PM, Geoff Canyon via use-livecode wrote: Also: the bug has been fixed. GitHub and the download on my Navigator page have been updated. I also have a separate branch where I'm improving the handlers menu. Woot! Woot indeed. Sounds like you're on a roll. -- Mark Wieder

Re: Navigator now supports converting controls to script-only stack behaviors

Also: the bug has been fixed. GitHub and the download on my Navigator page have been updated. I also have a separate branch where I'm improving the handlers menu. Woot! ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to

Navigator saves stackfiles, script menu supports unlimited behaviors

Added a "Save StackFiles" menu item to the popup menu when right-clicking on a stack or multiple stacks. This is especially useful for stacks using script-only behaviors. With one command it saves all the stacks referenced in the stack's stackfiles property. This is particularly useful for stacks

Re: What Env Variable set when saving standalone?

On 01/25/2018 05:03 PM, Bob Sneidar via use-livecode wrote: Oh how the pure have fallen! ;-) That would work but it's s dirty! True, but your stack isn't exactly living in HelloWorldLand. -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode

Re: Navigator now supports converting controls to script-only stack behaviors

I think I have it figured out -- Mikey suggested GitKraken, and that seems to work pretty well. I got the hang of how the branch/commit process works with a test directory and some simple text files. I'm thinking of making a "seriously, for beginners" video of that process. The one remaining

Re: What Env Variable set when saving standalone?

I might not have been clear. You'd keep the login stack a toplevel stack all the time. In whatever handler actually launches that stack, you'd check the environment and only open it as modal if the environment is "standalone". During development the login stack is toplevel. It should be able

Re: Chained behavior performance seems fine

cool thanks for sharing that little test. solves that curiosity. On Wed, Jan 24, 2018 at 3:59 PM, Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > Wow, I hope you scripted setting up that test... > On Wed, Jan 24, 2018 at 1:35 PM Geoff Canyon via use-livecode < >

Re: Bug: in 8.18 Stable and 9 Dp11 legacy stack import

Lagi- If I removed and saved I would get a stack corruption on next load , if I left them in after some changes - I would assume additions to the main stack I'm not sure the stack would load saying it couldn't find 2 substacks. When I loaded the stack as a binary the full stack scripts of both

Re: What Env Variable set when saving standalone?

On 01/25/2018 08:17 AM, Bob Sneidar via use-livecode wrote: Thanks Mark. I have a mainstack called Forms Generator. In the openStack handler in the card script of that stack, I open modally another substack called Login. This is so that no one can access the app without logging in first.

Re: What Env Variable set when saving standalone?

Thanks Mark. I have a mainstack called Forms Generator. In the openStack handler in the card script of that stack, I open modally another substack called Login. This is so that no one can access the app without logging in first. When I Save As Standalone, this Login stack opens (why I do not

Re: What Env Variable set when saving standalone?

I did. I moved them to the card script. Issue persists. And it doesn't explain why it's opening modally, which can only happen if my openStack handler in the card script of the MAINSTACK is executing. IMHO the standalone builder should not be executing any scripts, unless by doing so it finds

Re: problem with fullscreen option on HTML5 apps

"Fullscreen" never worked for me (other than getting a scaled display). It was probably not reported since HTML5 deployment is still experimental (means: It's easier to list what's working than what's not working). > T.J. wrote: > I’ve been trying out the fullscreen option (via the checkbox on

Re: regex deconstructor

Unfortunately I'm trying to fix the indenting in ST, so I'm stuck with it. Then I asked for help. The help is definitely better than what I came up with, but I have a couple of things I want to fix. The help disappeared, and I'm having a hell of a time reading this because it uses some advanced

Re: Navigator now supports converting controls to script-only stack behaviors

Any suggestions where to go to figure this out? At the most basic level, all I need is: 1. A "current released version" of Navigator on GitHub. 2. A work-in-progress version on my computer, in my LiveCode installation. 3. The ability to merge my copy into the GitHub version. And obviously, have

get URL problem on on-rev account

Hi list, I have a problem on my on-rev account for which I am awaiting an answer from the support; but since I haven't got it yet, I am asking this list. In an LC script I have 3 successive requests in the form : get URL "http://www.mydomain.fr/irev/myscript.lc?0_4; get URL

Bold textStyle on 'Header Bar' widget?

Hi there, How do I set the label of a 'Header Bar' widget to bold? greetings, William ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

Re: get URL problem on on-rev account

Try checking 'the result' after each get URL line and see if it gives an error indication - that might help work out what the problem is. Warmest Regards, Mark. Sent from my iPhone > On 25 Jan 2018, at 20:02, jbv via use-livecode > wrote: > > Hi list, > I

Re: RevQueryDatabase error in standalone

whats the error? ... i use sqlite with standalones as files and in memory ..without problems. On Wed, Jan 24, 2018 at 7:58 PM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi all. > > In dev mode I create a memory database, populate it, query it everythign > works fine.

Re: What Env Variable set when saving standalone?

You could try it a different way. Save/keep the login stack as toplevel all the time, then in the handler that opens the login stack: if the environment is not "development" then modal "login" else go stack "login" On 1/25/18 10:48 AM, Bob Sneidar via use-livecode wrote: I did. I moved them

Re: get URL problem on on-rev account

On Thu, January 25, 2018 9:28 pm, Mark Waddingham via use-livecode wrote: > Try checking 'the result' after each get URL line and see if it gives an > error indication - that might help work out what the problem is. > I did that, but the result is always empty; both requests just don't go

Re: get URL problem on on-rev account

is it only the url calls that don't work? Meaning, if you do a simple: put "after url # " following each attempt, do THOSE work? If so, then i'm not sure what to say, especially since you mentioned that the logs don't show the requests. If any of the following "puts" fail, it might help you

Re: What Env Variable set when saving standalone?

On 01/25/2018 01:57 PM, J. Landman Gay via use-livecode wrote: You could try it a different way. Save/keep the login stack as toplevel all the time, then in the handler that opens the login stack: if the environment is not "development" then modal "login" else go stack "login" I was just

Re: RevQueryDatabase error in standalone

Unfortunately, the error comes from the standalone CTD dialog, and it only provides the command that failed. I verified that it was in fact that command by putting an answer dialog just before and just after the query command. I got the first but not the second answer dialog. I can put the

Re: What Env Variable set when saving standalone?

Trouble is I DO want to open the login stack modally in development, because it pulls setup information for each user from the Login database, such as custom settings (like local file paths, recent customers list, access level etc). The only time I do NOT want to open that stack is when I am

Re: What Env Variable set when saving standalone?

On 1/25/18 5:26 PM, Mark Wieder via use-livecode wrote: On 01/25/2018 01:57 PM, J. Landman Gay via use-livecode wrote: You could try it a different way. Save/keep the login stack as toplevel all the time, then in the handler that opens the login stack: if the environment is not "development"

Re: What Env Variable set when saving standalone?

Bob, Is the problem that at app-login time, the app doesn't know whether its opening was caused by the standalone builder or by the user? If so, maybe something this would work: on standaloneSaved     put true into url (specialFolderPath("temp") & "/saved" end standaloneSaved on appLogin

Re: regex deconstructor

Is that the same stuff that Atom uses? I’m not that good at writing RegEx from scratch, but wouldn’t mind taking a look. I don’t have ST, so I wouldn’t be able to test there. On Thu, Jan 25, 2018 at 1:04 PM Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > Unfortunately I'm

Re: What Env Variable set when saving standalone?

A couple more ideas: in the Stack script… on savingStandalone processLogin "false" pass savingStandalone end savingStandalone command processLogin pLogin if pLogin = "false" then exit processLogin modal stack "Login" end processLogin I tested this, but I’m not 100% sure it would be

Re: Navigator now supports converting controls to script-only stack behaviors

The files on GitHub and your workstation should be pretty much the same. Like Trevor was saying, you would have a develop branch that contained your in progress code. The master branch would be the release. Every beta could be a commit in the dev branch. When ready for a final release, the code is

Re: What Env Variable set when saving standalone?

Regardless of the stack mode, why wouldn't it retrieve info? As the developer you'd know not to click elsewhere until the data is there, right? -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On January 25,

Re: What Env Variable set when saving standalone?

On 01/25/2018 03:31 PM, Bob Sneidar via use-livecode wrote: Trouble is I DO want to open the login stack modally in development, because it pulls setup information for each user from the Login database, such as custom settings (like local file paths, recent customers list, access level etc).

Re: Navigator now supports converting controls to script-only stack behaviors

On 01/25/2018 11:53 AM, Geoff Canyon via use-livecode wrote: > Any suggestions where to go to figure this out? At the most basic level, > all I need is: > > 1. A "current released version" of Navigator on GitHub. > 2. A work-in-progress version on my computer, in my LiveCode installation. > 3.

Re: regex deconstructor

It's similar. It takes a bit of massaging to get one into the other, especially once you get into the more advanced regex because there are features that one supports and the other doesn't. ST's regex engine is customized more than Atom's is. Here's the proposed not-quite-final indent rules

Re: What Env Variable set when saving standalone?

Thanks Phil. It's actually the opposite. At App Builder time, the login stack does not know that the app builder was what opened it, or rather called the script that opens it as a modal window. Bob S > On Jan 25, 2018, at 16:13 , Phil Davis via use-livecode >

Re: What Env Variable set when saving standalone?

Tried this. I used savingStandalone to set a global that I check when opening the Login Stack. It seems the message does not get sent until the standalone *actually* gets around to saving it. The Login stack gets opened while the standalone builder is in the process of gathering information

Re: What Env Variable set when saving standalone?

I assume because it's opened modally, and the builder obviously needs to open another stack but can't because the modal stack is blocking the progress of the script that told my app to open it. (I know it's confisung but that is how modality works I guess). Bob S > On Jan 25, 2018, at 16:24

Re: What Env Variable set when saving standalone?

Oh how the pure have fallen! ;-) That would work but it's s dirty! Bob S > On Jan 25, 2018, at 16:28 , Mark Wieder via use-livecode > wrote: > > Heretical idea: > > Put a 'Cancel' button on the modal stack. > If it's clicked, toplevel the stack and move

Re: RevQueryDatabase error in standalone

ya you have to look at the error.sometimes its not what you'd expect expect. On Thu, Jan 25, 2018 at 6:28 PM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Unfortunately, the error comes from the standalone CTD dialog, and it only > provides the command that failed.

Re: Bug: in 8.18 Stable and 9 Dp11 legacy stack import

Hi Brian Yes I am. It was a very insidious problem - at first I thought it was Dropbox playing up because all the versions were faulty - but when I had it backing up on the desktop as well using Max's plugin and checking for the first 5 or six updates and all ok then 2 hours or more of work all

Re: Bug: in 8.18 Stable and 9 Dp11 legacy stack import

Hi Lagi, If you could file a bug describing how you reproduce the stack corruption, and send us the stack to use to reproduce we'll look into it. It sounds like there is a problem somewhere with loading of pre-7 stacks with certain field content - we'd obviously like to fix this :)

Re: Navigator now supports converting controls to script-only stack behaviors

I found one bug: if you try to save the script-only stacks in the same folder as any of the stacks containing the objects you're converting, the conversion process will hang partway through. The hang should occur before anything has been changed, but still: Don't Do This. I have a fix coded, but

Re: Bug: in 8.18 Stable and 9 Dp11 legacy stack import

Hi Mark, I have rethunked overnight and I'm not sure whether the stack was "sort of corrupted" but working and might have something to do with it. I am under pressure with some deadlines till the middle of next week but I will take out an older version of the stack that was not corrupted and see

Re: Navigator now supports converting controls to script-only stack behaviors

On Thu, Jan 25, 2018 at 3:36 AM Geoff Canyon via use-livecode < use-livecode@lists.runrev.com> wrote: > > I have a fix coded, but I'm in the middle of another update, so I will > update the whole thing tomorrow morning. (This is the sort of thing GitHub > is supposed to be good for, right? Heh --