Re: Regaining IDE Efficiency: Property Inspector

On Thu, Aug 9, 2018 at 3:49 PM Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > 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 propertie

Re: Regaining IDE Efficiency: Property Inspector

On 08/10/2018 09:50 AM, Brian Milby via use-livecode wrote: > Scroll wheel is set to move the whole group, so any individual control is not touched. It does not move any content itself, just the whole “card”. ftfy: adding this handler to the script of field "value" of group "template" of stac

Re: Regaining IDE Efficiency: Property Inspector

Not complaining, just saying, the scrollwheel should scroll whatever target the mouse is hovering over. You can use the mouseControl for that. Bob S > On Aug 10, 2018, at 09:50 , Brian Milby via use-livecode > wrote: > > Scroll wheel is set to move the whole group, so any individual control

Re: Regaining IDE Efficiency: Property Inspector

Scroll wheel is set to move the whole group, so any individual control is not touched. It does not move any content itself, just the whole “card”. Thanks, Brian On Aug 10, 2018, 11:32 AM -0500, Mark Wieder via use-livecode , wrote: > On 08/09/2018 07:47 PM, Brian Milby via use-livecode wrote: >

Re: Regaining IDE Efficiency: Property Inspector

On 08/09/2018 07:47 PM, Brian Milby via use-livecode wrote: For the PI, the raw keys are intercepted and scroll wheel is directed toward scrolling the PI group. So if you take the custom properties tab and grow it and then shrink it then the scroll wheel should work as expected to move the visi

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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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