SE: restore default handlers?

2018-02-06 Thread Richard Gaskin via use-livecode
I have "Show Default Handlers" checked in my SE, but I don't see them. Is this yet another case where I have to toss my prefs stack and then go back and restore all my settings to get this one thing to work, or is there a simpler way to show default handlers in the SE? -- Richard Gaskin Fou

Re: SE: restore default handlers?

2018-02-06 Thread panagiotis merakos via use-livecode
Do you see the non-default handlers of the script? If you see no handlers at all, then either there is a syntax error in the script and LC for some reason does not see it, or something else happens and trashing your Prefs will probably fix it :) PS: I guess you have already tried unchecking and r

Re: SE: restore default handlers?

2018-02-06 Thread Richard Gaskin via use-livecode
panagiotis merakos wrote: > On Tue, Feb 6, 2018 at 5:21 PM, Richard Gaskin wrote: > >> I have "Show Default Handlers" checked in my SE, but I don't see >> them. ... > Do you see the non-default handlers of the script? Yes. > If you see no handlers at all, then either there is a syntax error in

Re: SE: restore default handlers?

2018-02-06 Thread panagiotis merakos via use-livecode
I cannot reproduce this, tested on Ubuntu 16.04 with LC 9 DP-11. Could it be the case that there is a bad interaction with a Plugin? What happens if you try first to "put true into grevdevelopment" and then uncheck and recheck "Show Default handlers"? If something was failing silently before, th

Re: SE: restore default handlers?

2018-02-06 Thread Richard Gaskin via use-livecode
panagiotis merakos wrote: > I cannot reproduce this, tested on Ubuntu 16.04 with LC 9 DP-11. > > Could it be the case that there is a bad interaction with a Plugin? > > What happens if you try first to "put true into grevdevelopment" and > then uncheck and recheck "Show Default handlers"? > > If s

Re: SE: restore default handlers?

2018-02-06 Thread panagiotis merakos via use-livecode
Thanks Richard. So, a guess is that for some reason LC cannot open the sqlite database that holds all the dictionary entries, thus it cannot fetch the list of the default handlers per object. I am wondering if this is related to the other bug report you have filed, where the dictionary opens but it

Re: SE: restore default handlers?

2018-02-06 Thread Richard Gaskin via use-livecode
panagiotis merakos wrote: Thanks Richard. So, a guess is that for some reason LC cannot open the sqlite database that holds all the dictionary entries, thus it cannot fetch the list of the default handlers per object. I am wondering if this is related to the other bug report you have filed, where

Re: SE: restore default handlers?

2018-02-06 Thread Geoff Canyon via use-livecode
Does this do what I think it does!? i.e. make it so rev code can throw errors, be debugged, breakpointed, and stepped through. If so, oh my goodness you just made my day. I have been debugging Navigator for fourteen years now, all with answer statements and puts. My code is literally riddled

Re: SE: restore default handlers?

2018-02-06 Thread Mark Wieder via use-livecode
On 02/06/2018 02:46 PM, Geoff Canyon via use-livecode wrote: Does this do what I think it does!? i.e. make it so rev code can throw errors, be debugged, breakpointed, and stepped through. Yes, it does... but be careful with it. It will also pinpoint all the ugly errors in the IDE stacks. I on

Re: SE: restore default handlers?

2018-02-06 Thread Geoff Canyon via use-livecode
On Tue, Feb 6, 2018 at 2:59 PM, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 02/06/2018 02:46 PM, Geoff Canyon via use-livecode wrote: > >> Does this do what I think it does!? i.e. make it so rev code can throw >> errors, be debugged, breakpointed, and stepped through.

Re: SE: restore default handlers?

2018-02-07 Thread Bob Sneidar via use-livecode
Of course, sqlite DBs are single user only so any attempt to open it a second time would fail. Just tossing that out there. Bob S > On Feb 6, 2018, at 11:30 , panagiotis merakos via use-livecode > wrote: > > Thanks Richard. So, a guess is that for some reason LC cannot open the > sqlite dat

Re: SE: restore default handlers?

2018-02-07 Thread Mike Kerner via use-livecode
@Bob are you sure that's true? I seem to recall being able to accidentally reopen the db over and over without an error. I can't remember if the dbid increments when I do this, but I think it does. On Wed, Feb 7, 2018 at 11:04 AM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wro

Re: SE: restore default handlers?

2018-02-07 Thread Bob Sneidar via use-livecode
Spiceworks Inventory and Help Desk uses a local sqlite dbfile. They stress that you cannot open this DB directly, or else if Spiceworks tries to write to it you can corrupt the DB. You *can* open the sqlite file read only, but two people cannot open it for write at the same time. sqlite is a sin

RE: SE: restore default handlers?

2018-02-07 Thread Ralph DiMola via use-livecode
[mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Mike Kerner via use-livecode Sent: Wednesday, February 07, 2018 1:44 PM To: How to use LiveCode Cc: Mike Kerner Subject: Re: SE: restore default handlers? @Bob are you sure that's true? I seem to recall being able to accidentally reopen t

Re: SE: restore default handlers?

2018-02-07 Thread Bob Sneidar via use-livecode
OIC I thought the question was, could 2 processes have the same sqlite db open. I don't think the LC engine opens the file over and over in different threads. I also think that it closes the connection when it is idle, hence the new DBID. I just checked for sqlite V3, and it appears multiple pr