Tree View / Custom Properties PI

Before going too far, I'd like to get some feedback on the best way to address one of the issues that Curry brought up. Currently, when in the Tree View widget (which is used in the Custom Properties PI), if you click on the "+" icon to add a new array key, the value in the existing key is lost if

Re: Regaining IDE Efficiency: Property Inspector

Me either. I tried to like them, and tested at least three, and even made my own. But in the long run it's all muscle memory for me. I need landmarks, and colors aren't enough. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On August 9,

Re: Regaining IDE Efficiency: Property Inspector

I've briefly looked at a few issues and have some comments: I should be able to put together something on the Custom Properties portion of the PI. I'm looking at the code and am not sure yet if the change needs to be in the widget, the PI, or both. I think that the widget should have a warning

Re: Regaining IDE Efficiency: Property Inspector

Mike Kerner wrote: > I'm not a fan of sheets. I find myself doing constant scrolling You're not using v9's PI? ;) > because the property I'm looking for never seems to be on the screen, > or if I'm changing multiple properties and messing with settings to > see what the combination does, I'm

Re: Regaining IDE Efficiency: Property Inspector

I'm not a fan of sheets. I find myself doing constant scrolling because the property I'm looking for never seems to be on the screen, or if I'm changing multiple properties and messing with settings to see what the combination does, I'm constantly going up down up down, overshooting the property,

Re: Regaining IDE Efficiency: Property Inspector

On 08/09/2018 04:21 PM, Curry Kenworthy via use-livecode wrote: Hint: A property sheet doesn't necessarily need to look like one. True, but it also shouldn't get in my way. And you've done a great job in listing most of the annoyances of the PI. -- Mark Wieder ahsoftw...@gmail.com

Re: Regaining IDE Efficiency: Property Inspector

> On 10 Aug 2018, at 9:07 am, Curry Kenworthy via use-livecode > wrote: > > Whatever you need is absolutely fine with me, feel free to parse and > slice/dice this into any number of pieces with my blessing. OK for anyone else following along the best way to discuss issues with us is to fol

Re: stackfiles

Bob Sneidar wrote: > On Aug 9, 2018, at 11:45 , Richard Gaskin wrote: > Yes, the stackFiles property is every bit as global as any other use > of stack names. > > Not to belabor the point, but the stackfiles is a property of a STACK, > not a global system property. A stack's name is also a prope

Re: Regaining IDE Efficiency: Property Inspector

Richard: > Many (most?) development environments use a property sheet Wieder: > I'm a big fan of property sheets. Hint: A property sheet doesn't necessarily need to look like one. It could be useful to consider the value that the past and current PI appearance has for users. The effect it

Re: Regaining IDE Efficiency: Property Inspector

Monte: > We really need a single report per issue. Howdy Monte! Whatever you need is absolutely fine with me, feel free to parse and slice/dice this into any number of pieces with my blessing. However I myself will NOT be filing dozens or hundreds of report; impossible. I wasn't kidding or

Re: Regaining IDE Efficiency: Property Inspector

On 08/09/2018 08:14 AM, Richard Gaskin via use-livecode wrote: Many (most?) development environments use a property sheet* instead, to handle the deep, rich variety of detailed properties developers need to control. Much like revNavigator, no? I'm a big fan of property sheets. -- Mark Wied

Re: stackfiles

Not to belabor the point, but the stackfiles is a property of a STACK, not a global system property. It would be like setting the foo of stack "test1" to the filename of stack "splash", quitting LC, relaunching LC, opening stack "test1", then expecting to be able to open stack "splash" using it'

Re: Regaining IDE Efficiency: Property Inspector

> On 10 Aug 2018, at 1:53 am, Curry Kenworthy via use-livecode > wrote: > > Here's the QA enhancement request for Property Inspector defects: > > https://quality.livecode.com/show_bug.cgi?id=21479 > Hi Curry We really need a single repor

Re: Intersect outputs different result in desktop and LC server

I think LC9 is faster, but I've never tested, so that's purely "anecdotal". Yes, I believe it does mean that a new stable release will replace the older one; I've quoted Robin's mail from my support ticket conversation below ... This might be worth a discussion with on-rev support, to see whe

Re: Intersect outputs different result in desktop and LC server

Hi Alex, Thanks for the tip. I'm on sage too. Is it me or is LC9 server much faster than previous versions ? One more thing : you wrote : "any file with extension .lc9 will use the latest stable release of LC9" Does that mean that LC server will be updated every time a new stable version is releas

Re: Regaining IDE Efficiency: Property Inspector

Curry Kenworthy wrote: > Here's the QA enhancement request for Property Inspector defects: > > https://quality.livecode.com/show_bug.cgi?id=21479 Thanks for submitting that, Curry. I have a dream in which an increasing amount of IDE stuff gets done by the community, leaving more C++ programmer

Re: stackfiles

Bob Sneidar wrote: > How odd though. The stackfiles is acting like a global property. > Imagine I have 2 projects open, each referencing 2 different versions > of the same stack in different locations on the disk. Any attempt to > open that stack using it's short name might yield the wrong stack.

Re: Tutorial for MAP widget

Klaus- After further inspection I agree with you that this widget needs a proper tutorial. I was looking at the module itself trying to find some undocumented features (like a polygon or circle overlay instead of just a polyline) and came up empty handed. After looking at the W3Schools tu

Re: HTML to text in field

Hmm . . . On 9/8/2018 4:21 pm, David V Glasgow via use-livecode wrote: Thanks Richmond, I will mess about with your suggestions. It's always much appreciated when someone takes the time to suggest a complete handler. But …. I want more! * **Just as long as I can call you Oliver Twist. :)*

Re: HTML to text in field

Possibly as it was lifted verbatim from "elsewhere'. :/ Although it works the way it is in LC 8.1.10. Richmond. On 9/8/2018 4:31 pm, Richard Gaskin via use-livecode wrote: Richmond Mathewson wrote: >put (URL ("file:" & it),"UTF8") into CHEESE Was uniDecode intended there? -- Richar

Re: Regaining IDE Efficiency: Property Inspector

This one escaped me at first as well, but if you click on the sprocket widget in the upper-right of the PI you have the option for "Header/Footer Size" to grow and shrink the tabs. I'm not sure what "Footer" is referring to. --Andrew Bell PI window and tabs: - The PI tabs (Basic, Conten

Re: Tutorial for MAP widget

Like this? https://livecode.com/docs/9-0-0/components/map-widget/ I will be talking a little about my Map widget implementation during a LC Global talk next month. --Andrew Bell From: Klaus major-k To: How to use LiveCode Subject: Tutorial for MAP widget Message-ID: Content-Type: text/pl

Re: stackfiles

Should be: open stack tFullStackPath > On Aug 9, 2018, at 09:23 , Bob Sneidar via use-livecode > wrote: > > open tFullStackPath ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage y

Re: stackfiles

The safe way then to do this would be: put the stackfiles of stack "test1" into tStackFiles -- or whatever your stack is named filter lines of tStackFiles with "splash*" -- or whatever your stack short name is put item 2 of tStackFiles into tFullStackPath open tFullStackPath Bob S > On Aug 9,

Re: stackfiles

How odd though. The stackfiles is acting like a global property. Imagine I have 2 projects open, each referencing 2 different versions of the same stack in different locations on the disk. Any attempt to open that stack using it's short name might yield the wrong stack. I know you will say: "W

Re: stackfiles

Ah! I get it now. I tested this. 2 stacks, one with the stackfiles set to a third stack somewhere on disk. Second one with a button that opens the stack listed in the stackfiles of the first stack using it's short name. With both stacks open, Clicking the button opens the stack listed in the

Re: stackfiles

Hi Richard, > Am 09.08.2018 um 17:20 schrieb Richard Gaskin via use-livecode > : > > Klaus major-k wrote: > ... > When a stack file is included among the stackfiles property of an open stack, > you should be able to address it by short name if you like. thank you, that finally answers my quest

Re: Regaining IDE Efficiency: Property Inspector

Here's the QA enhancement request for Property Inspector defects: https://quality.livecode.com/show_bug.cgi?id=21479 Sorry I didn't see some of the replies here until already submitted, but feel free to add comments there, and sign on if y

Re: stackfiles

Klaus major-k wrote: > I mean if stack xyz has its stackfile property set, can other stack > access this property just like the stack xyz scripts? Every property of every object in every stack on your hard drive is available to every script. An object does no need to be loaded into memory to

Re: Regaining IDE Efficiency: Property Inspector

- The PI tabs (Basic, Contents, Custom...) are one thing that is almost more efficient now than in 6. Good! But still needs improvement. I say "almost" efficient because the little tab buttons are way too small - about 11x10 px on my screen. That's takes more effort and concentration to click, and

Re: Regaining IDE Efficiency: Property Inspector

I’ve done a bit of work in the tree widget, so I can take care of submitting a PR against a bug/enhancement request there. Thanks, Brian On Aug 9, 2018, 9:56 AM -0500, Bob Sneidar via use-livecode , wrote: > I'm using rc1, and the PI issues persist so far as I can see. As I mentioned, > the ele

Re: stackfiles

Hi Bob, > Am 09.08.2018 um 17:15 schrieb Bob Sneidar via use-livecode > : > >> On Aug 9, 2018, at 08:07 , Klaus major-k via use-livecode >> wrote: >> >> I mean if stack xyz has its stackfile property set, can other stack access >> this property just like the stack xyz scripts? > > If I unde

Re: Regaining IDE Efficiency: Property Inspector

Inspectors are popular in drawing and layout programs, where object properties are relatively limited. Many (most?) development environments use a property sheet* instead, to handle the deep, rich variety of detailed properties developers need to control. Property sheets can help address eve

Re: stackfiles

> On Aug 9, 2018, at 08:07 , Klaus major-k via use-livecode > wrote: > > I mean if stack xyz has its stackfile property set, can other stack access > this property just like the stack xyz scripts? If I understand you, then another stack can reference the stackfiles of xyz by getting the st

Re: stackfiles

Hi Bob, > Am 09.08.2018 um 17:03 schrieb Bob Sneidar via use-livecode > : > > I see, you are asking if the scripts of the stackfiles are inserted into the > message heirarchy? No. It can't work that way if you think about it. You > would never be able to include another stack in a standalone w

Re: stackfiles

I see, you are asking if the scripts of the stackfiles are inserted into the message heirarchy? No. It can't work that way if you think about it. You would never be able to include another stack in a standalone without having every stack script of every stack in the message heirarchy. If you a

Re: Regaining IDE Efficiency: Property Inspector

I'm using rc1, and the PI issues persist so far as I can see. As I mentioned, the element portion of the PI is actually a tree widget, so some of the issues are really with the tree widget, not the PI itself. Bob S > On Aug 9, 2018, at 06:23 , Paul Dupuis via use-livecode > wrote: > > My u

Re: stackfiles

Hi Bob, > Am 09.08.2018 um 16:48 schrieb Bob Sneidar via use-livecode > : > > Start Using simply inserts the script of that stack in the back, so it is now > in the message path which > is global to everything running in that instance of livecode or the > standalone. yes, I know, this way it

Re: Regaining IDE Efficiency: Property Inspector

Oh never mind. PI (Property Inspector) Bob S > On Aug 9, 2018, at 07:51 , Bob Sneidar via use-livecode > wrote: > > if you insert cr's you get more lines. But a single line will not wrap. Not > sure tooltips in any version did. > > Bob S > > >> On Aug 9, 2018, at 01:29 , Curry Kenworthy

Re: Regaining IDE Efficiency: Property Inspector

if you insert cr's you get more lines. But a single line will not wrap. Not sure tooltips in any version did. Bob S > On Aug 9, 2018, at 01:29 , Curry Kenworthy via use-livecode > wrote: > > - PI Tooltip field is short, only one line high, can't resize unless you > resize window or visit a

Re: stackfiles

Start Using simply inserts the script of that stack in the back, so it is now in the message path which is global to everything running in that instance of livecode or the standalone. Bob S > On Aug 9, 2018, at 02:58 , Klaus major-k via use-livecode > wrote: > > Hi friends, > > quick ques

Re: HTML to text in field

Hi David, I’m working on something thing similar at the moment (although I’m stripping out almost everything except for basic HTML formatting). I too found that nugget by JLG and had the similar results. I’ve also looked at using XML and regex. The problem with HTML is that while it’s a standar

Re: How to get LiveCode to return 'Today' & 'Now'?

Thanks Brian (& Tore) - a brain-fade meant I clearly forgot ‘the obvious’ syntax :-) Best, Keith > On 9 Aug 2018, at 14:57, Brian Milby via use-livecode > wrote: > > the date > the time > > Thanks, > Brian > On Aug 9, 2018, 8:56 AM -0500, Keith Clarke via use-livecode > , wrote: >> Hi folk

Tutorial for MAP widget

Hi all, could someone (the mothership?) please create a little tuorial for the new MAP widget? This is really not self-explaining. How to let the user create a new marker etc... Thanks a lot! Best Klaus -- Klaus Major http://www.major-k.de kl...@major-k.de ___

Re: How to get LiveCode to return 'Today' & 'Now'?

Use any form of the date (short, long,international,system) for today, an any form of the time (short, long,international,system) for the time. To see the difference between them look them up in the dictionary. Regards Tore Nilsen --- This mail contains no viruses or bacteria as it is ele

Re: How to get LiveCode to return 'Today' & 'Now'?

the date the time Thanks, Brian On Aug 9, 2018, 8:56 AM -0500, Keith Clarke via use-livecode , wrote: > Hi folks, > Please can anyone share the magic syntax to > > put today into tDate > > put now into the tTime > > I haven’t found a magic keyword to seed the docs or Google. > Thanks > Keith > __

How to get LiveCode to return 'Today' & 'Now'?

Hi folks, Please can anyone share the magic syntax to put today into tDate put now into the tTime I haven’t found a magic keyword to seed the docs or Google. Thanks Keith ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit th

Re: HTML to text in field

D’OH! > On 9 Aug 2018, at 2:23 pm, Klaus major-k via use-livecode > wrote: > > > "replacetext ()" is a FUNCTION and not a handler! :-) ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and ma

Re: Regaining IDE Efficiency: Property Inspector

great breakdown of the issues.. i have been ramping up tp sit down and make all those notes. its hard to do when you go work to do. So thanks Curry for going through that. Once these are fixed, I think the IDE will be quite good. On Thu, Aug 9, 2018 at 9:23 AM, Paul Dupuis via use-livec

Re: HTML to text in field

Richmond Mathewson wrote: >put (URL ("file:" & it),"UTF8") into CHEESE Was uniDecode intended there? -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web amba

Re: Regaining IDE Efficiency: Property Inspector

I second Curry's list of LC 9.0.0 IDE issue - especially when the PI resizes itself switching between tabs to cut off display of fields below the current window size. My understanding from something I (think I) saw on this list was that 9.0.1 is focused on IDE improvements. I have not yet download

Re: HTML to text in field

Hi David, > Am 09.08.2018 um 15:21 schrieb David V Glasgow via use-livecode > : > > Thanks Richmond, I will mess about with your suggestions. It's always much > appreciated when someone takes the time to suggest a complete handler. > But …. I want more! Can you see anything wrong with this? >

Re: HTML to text in field

Thanks Richmond, I will mess about with your suggestions. It's always much appreciated when someone takes the time to suggest a complete handler. But …. I want more! Can you see anything wrong with this? replaceText (ttemp, "<*>", "|") or have a clue about the error message? “button "Impo

Re: HTML to text in field

Well, although this might sound a bit goofy, how about just bunging your html text into a scrolling list field and every time you came across a moving down to a new line? This works: on mouseUp set the text of fld "SLF1" to empty answer file "Choose an HTML file to import" if the re

HTML to text in field

Hello folks, I am having an interesting time (MacOS 10.13.5 LC 8.1.9) trying to load some HTML files (≤ 5 ish MB). Most of them will be lists or tables, generated by various users on various systems. I don’t want to retain any of the formatting, except line endings, so I would be happy for ta

Re: Intersect outputs different result in desktop and LC server

I sent a support request asking for it :-) AFAIK, at least on sage, it is installed systemwide - so any file with extension .lc9 will use the latest stable release of LC9 (this is a similar scheme to what HostM use). I suspect you can use .htaccess to ensure it is used for all .lc files, but

stackfiles

Hi friends, quick question: When I "start using stack xyz" then all stack can access the scripts etc. of stack xyz. Does this also apply to the stackfiles of stack xyz? Thanks in advance! Best Klaus -- Klaus Major http://www.major-k.de kl...@major-k.de ___

Regaining IDE Efficiency: Property Inspector

Howdy Folks, As more client projects have caught up with 9, now I'm currently spending the majority of my time in LiveCode 9 IDE. That's both good and bad. The bad is that the 8/9 IDE's UI is much less efficient and much less polished than 6 was. And I'm starting to feel the cumulative impac