Re: Enhancement request: show the execution contexts in debugger UI

There's a popdown button at the top left of the editor that shows the execution contexts. Do you need more information than that? -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On April 20, 2021 5:49:28 AM Andre Garzia via use-livecode

Re: Enhancement request: show the execution contexts in debugger UI

I will join in to support (as soon as I remember which password gives me access). But I think it would be more useful to have this displayed as a "value" palette - similar to what you get when you double-click a variable - rather than another tabbed pane. Alex. On 20/04/2021 11:46, Andre G

Re: enhancement request

On Tue, Oct 14, 2014 at 3:55 PM, J. Landman Gay wrote: > I rely on exact pasting positions when duplicating a card object to a > different card or across stacks. LC's "duplicate" menu item does offset the > duplicates. And thanks Jacque,. I knew about that but had forgotten about it. When try

Re: enhancement request

Thanks Jerry, didn't know about that, very useful Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin On Tue, Oct 14, 2014 at 3:35 PM, Jerry Jensen wrote: > If you use Option-drag to

Re: enhancement request

I actually use naming to discern which fields display input from a SQL database. Every field that begins with “fld” is associated with a column in a table i.e. fldCustomerName is associated with the column customername. Bob S On Oct 14, 2014, at 14:15 , J. Landman Gay wrote: > Agree, I thin

Re: enhancement request

Either the option key is stuck, or else the engine thinks it’s down. Sounds like you are cloning the second copy. Bob S On Oct 14, 2014, at 13:16 , la...@significantplanet.org wrote: > Hello, > I've had this situation before and had it again today, which cost me a couple > of hours. > > I d

Re: enhancement request

On 10/14/2014, 5:26 PM, Peter Haworth wrote: Going back to the original problem, it might be useful to offset a pasted control by a few pixels to the right and lower to make it more obvious it's there. Or just keep the app browser or the project browser open, where it would be easy to spot.

Re: enhancement request

And now I remember how I got into the same predicament a long time ago: I option-dragged and then thought "oops, I didn't want to do that" and tried to undo my action by carefully putting the new one exactly over the original. WRONG MOVE JENSEN! On Oct 14, 2014, at 3:35 PM, Jerry Jensen wrote:

Re: enhancement request

That is an excellent idea and would solve the problem for him. It is nice to visually see something has changed. Sometimes your keyboard does not catch the paste command and then when you drag the supposed pasted field to a new location you mess up the location of the original field. John Balgen

Re: enhancement request

If you use Option-drag to make a copy, you can for sure see that there are two. .Jerry On Oct 14, 2014, at 3:26 PM, Peter Haworth wrote: > Going back to the original problem, it might be useful to offset a pasted > control by a few pixels to the right and lower to make it more obvious it's > the

Re: enhancement request

Going back to the original problem, it might be useful to offset a pasted control by a few pixels to the right and lower to make it more obvious it's there. Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin

Re: enhancement request

I like to reference my fields and buttons by id number and then I don’t need to worry about it. John Balgenorth On Oct 14, 2014, at 2:15 PM, J. Landman Gay wrote: > Agree, I think the feature is more desirable than not. I frequently name all > label fields the same so I can loop over all the

Re: enhancement request

Agree, I think the feature is more desirable than not. I frequently name all label fields the same so I can loop over all the controls and skip any named "lbl". On October 14, 2014 4:05:49 PM CDT, dunb...@aol.com wrote: >As for a warning that you already have one of that name, there are >insta

Re: enhancement request

Larry. Sure you didn't hit "paste" twice? Anyway. LC would "see" the field with the lowest layer number as the one to reference, if, say, you "put something into fld myInput". This, of course, is the field at the bottom. As for a warning that you already have one of that name, there are insta

Re: [Enhancement Request] Support of webM and webP

Hi Dar, Dar Scott wrote > I guessing one could write a library (LiveCode) to get webP images, > or use an external. Those could be displayed. > But, I’m not sure what one would do with webM. Save it to a file > in some other format? Play it? That looks like it would need an > enhancement of

Re: [Enhancement Request] Support of webM and webP

I guessing one could write a library (LiveCode) to get webP images, or use an external. Those could be displayed. But, I’m not sure what one would do with webM. Save it to a file in some other format? Play it? That looks like it would need an enhancement of player. Is that what you were

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

On 24/04/2014 23:15, Richard Gaskin wrote: Ben Rubinstein wrote: > I'd love to know: what do other people do to customise their > environment? Is that all?!? ___ use-livecode mailing list use-liv

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

On Fri, Apr 25, 2014 at 2:56 AM, Ben Rubinstein wrote: > > It's got various things on it, but the main ones are a big backup+save > button, and a display of the rev version - actually, the buildnumber(), > version() and revAppVersion() - so just by glancing at the top-right corner > of my screen

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

It is interesting how different people work in different ways. In my lcStackBrowser plugin I tried to include functionality that I've found useful in my own work environment and also keep the number of open utility stacks to a minimum, hoping to provide as much flexibility as possible. Like Richar

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

J. Landman Gay wrote: On 4/24/14, 5:15 PM, Richard Gaskin wrote: Where do you put the stacks you're working on? :) You and I have exactly opposite work habits. Maybe not so much. Most of those stacks aren't open all the time, some seldom

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

On 4/24/14, 5:15 PM, Richard Gaskin wrote: Where do you put the stacks you're working on? :) You and I have exactly opposite work habits. I mentioned "choice" earlier in this thread. Choice is good. It's a credit to LC that we can work howev

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

Ben Rubinstein wrote: > I'd love to know: what do other people do to customise their > environment? -- Richard Gaskin Fourth World LiveCode training and consulting: http://www.fourthworld.com Webzine for LiveCode developers: http://www.LiveC

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

On 4/24/14, 1:56 PM, Ben Rubinstein wrote: I'd love to know: what do other people do to customise their environment? I use a system I started in HC 25+ years ago and have been adding to ever since. Back then it was additions to the Home script, today it's a library plugin that inserts one scr

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of J. Landman Gay Sent: Wednesday, April 23, 2014 10:13 PM To: How to use LiveCode Subject: Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC I got tired of that so now I just type "the version"

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

On 24/04/14 00:26, Alejandro Tejada wrote: Hi Richmond, Richmond Mathewson-2 wrote How about something like this: on saveStackRequest put (the short name of this stack & the version) into NOM put NOM into fld "NOM" set the name of this stack to NOM pass saveStackRequest en

RE: [Enhancement Request] Open and BackUp in LiveCode DP and RC

rev.com] On >Behalf >Of J. Landman Gay >Sent: Wednesday, April 23, 2014 10:13 PM >To: How to use LiveCode >Subject: Re: [Enhancement Request] Open and BackUp in LiveCode DP and >RC > >I got tired of that so now I just type "the version" into the message >box. &g

RE: [Enhancement Request] Open and BackUp in LiveCode DP and RC

ssage- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of J. Landman Gay Sent: Wednesday, April 23, 2014 10:13 PM To: How to use LiveCode Subject: Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC I got tired of that so now I just type "the version

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

With a file-format change happening, and two fronts of development, this is even more important. Maybe the mouse pointer can be red for dp and orange for rc. Or it can speak “seven point zero” whenever I bring a window forward. Or a way to make version icons for aliases. Dar On Apr 23, 20

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

I got tired of that so now I just type "the version" into the message box. On April 23, 2014 8:20:56 PM CDT, Kay C Lan wrote: >The problem I have is I occasionally accidentally start the wrong version >so I'm constantly needing to visit the About LiveCode to confirm which version >is open --

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

On Thu, Apr 24, 2014 at 3:37 AM, Richard Gaskin wrote: > Stacks can be opened many ways. > I'm with Richard on this one. I have stacks I wont risk with anything other than GM versions of LC. Those stacks I am willing to risk I simply duplicate then start them up with an RC or DP version. The pro

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

Hi Richmond, Richmond Mathewson-2 wrote > How about something like this: > > on saveStackRequest > put (the short name of this stack & the version) into NOM > put NOM into fld "NOM" > set the name of this stack to NOM > pass saveStackRequest > end saveStackRequest > > Certainly

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

On 23/04/14 23:04, Alejandro Tejada wrote: Then, a plug-in stack would do. Does LiveCode includes the Engine version in each saved stack? http://docs.runrev.com/Function/version http://docs.runrev.com/Property/stackFileVersion If this is true, then LiveCode could provide a warning when develop

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

On 23/04/14 22:22, Alejandro Tejada wrote: Hi All, Just added this enhancement request: http://quality.runrev.com/show_bug.cgi?id=12279 Every announcement of a new LiveCode version includes this message: WARNING: this is not a stable release. Please ensure you back up your stacks before test

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

Then, a plug-in stack would do. Does LiveCode includes the Engine version in each saved stack? http://docs.runrev.com/Function/version http://docs.runrev.com/Property/stackFileVersion If this is true, then LiveCode could provide a warning when developers open a stack created with a different eng

Re: [Enhancement Request] Open and BackUp in LiveCode DP and RC

Stacks can be opened many ways. In most of my projects I only manually open one stack in the IDE, and the scripts in that stack may load as many as a dozen others. To satisfy the request the engine would have to intercept all attempts to open stacks, or maybe just the save command, and then i