Re: Refactoring is your friend / moving from 6.x to 9.x

> On 7 Jan 2019, at 17:00, Richard Gaskin via use-livecode > wrote: > > Perhaps the biggest flaw I've seen with v9 is the bug report tracking: the > Release Notes only include a subset of all issues addressed since work began > on it two years ago. My understanding from conversations with

Re: Refactoring is your friend / moving from 6.x to 9.x

Simon Knight wrote: > ...I do agree that the team does an extraordinary job of bug > reduction while adding features and keeping on top of all the > changes to the list of OS’s that livecode runs on. LC v9 is particularly strong in this regard. We have some in our community who've dreamed of a

Re: Refactoring is your friend / moving from 6.x to 9.x

> On 7 Jan 2019, at 08:16, Kay C Lan via use-livecode > wrote: > > And a spookily well timed questions; it's as if the late great Bill > Marriot hearkens from the grave. Bill was responsible for the focus > that took a very flakey Revolution, create the RQCC and develop what > is clearly a

Re: Refactoring is your friend / moving from 6.x to 9.x

On Mon, Jan 7, 2019 at 4:26 AM Richard Gaskin via use-livecode wrote: > > Simon Knight wrote: > > One question why does this thread refer to RQCC ? > Richard Replied: > Old habits. The bug database used to be called the "Revolution Quality > Control Center", and the acronym is forever stuck in

Re: Refactoring is your friend / moving from 6.x to 9.x

Thanks for that confirmation Trevor great to hear that. On Sun, Jan 6, 2019 at 9:45 PM Trevor DeVore via use-livecode < use-livecode@lists.runrev.com> wrote: > On Sun, Jan 6, 2019 at 4:56 PM Tom Glod via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > > Seems like signing the exec

Re: Refactoring is your friend / moving from 6.x to 9.x

On Sun, Jan 6, 2019 at 4:56 PM Tom Glod via use-livecode < use-livecode@lists.runrev.com> wrote: > > Seems like signing the exec is a good idea and certainly can't hurtand > if I have to write some emails to get whitelisted I can do that too. FWIW I always sign my Windows standalones and I

Re: Refactoring is your friend / moving from 6.x to 9.x

Thanks, everyone for chiming in here, I want to help narrow down the circumstances in which windows defender affects the ide but more importantly standalones. Richard, I demoed my stack on my mother in laws laptop and her AV (one I was not familiar with) put my executable into quarantine

Re: Refactoring is your friend / moving from 6.x to 9.x

Richard, Your are correct but Malte did ask ask about general refactoring (i think) so I just mentioned my latest problem / finding. As to the PDF “feature” itsself I think its now up to Edinburgh to decide what to do; I doubt that they intended to have Adobe menus and button bars popping up

Re: Refactoring is your friend / moving from 6.x to 9.x

Richard: > If you're satisfied the the progress on yours then of course you > can safely ignore my passing that along. Thanks Richard - all great things to bear in mind, when kept realistic. Areas affected by performance were pretty widespread, so it'll be easier to isolate any remaining

Re: Refactoring is your friend / moving from 6.x to 9.x

Malte Pfaff-Brill wrote: > If there were a list of things that do no longer work as they did non > previous engines it would have been beneficial for me to check off > points like „Yes, using that, need to fix / No, does not affect my > work" Half of that problem is solved in the Engine Changes

Re: Refactoring is your friend / moving from 6.x to 9.x

And of course, please also be vocal on the positives!!! Old engine Mac: Hi res images were a problem to render (for whatever reason, I had to use video player instead of image object to display those images). Limitations here have been lifted which for me is a very pleasant change! Cheers,

Re: Refactoring is your friend / moving from 6.x to 9.x

Hi Richard, >I didn't see Malte's mention of PDF in the post that began this thread, While that is true, but I am actually (as stated) keen to learn about everything that could be a gotcha when transitioning from the old engine to the latest, so this is welcome input. Also Marks mention of TAB

Re: Refactoring is your friend / moving from 6.x to 9.x

Simon Knight wrote: > This thread seems to have diverted away from Malte’s original post. Somewhat. His post from Dec 30 listed three issues: - IDE spams a lot of IDE only messages when creating many objects by script -> remedy: Lock messages Locking messages is a good habit for any

Re: Refactoring is your friend / moving from 6.x to 9.x

Curry Kenworthy wrote: > Richard: ... > > As hodge podge of what appear to be very different optimization > > opportunities under the hood, it may be difficult for the team to > > take action on it/them, and impossible to track. [... ... ...] ... > ..Moot point, because I didn't have time for

Re: Refactoring is your friend / moving from 6.x to 9.x

This thread seems to have diverted away from Malte’s original post. For Malte and others I have found that the revBrowser control is slower to render PDFs and may insert unwanted menus and button thanks to Adobe in version 9.02. See

Re: Refactoring is your friend / moving from 6.x to 9.x

Richard: > It's a bit confusing, since the Target Version shown there is 7, > but it was submitted just a few months ago, many years after v7 > was EOL'd. As you can see (in the message you replied to) I inquired back then, and was advised officially then. BTW, that's a bit like the concrete

Re: Refactoring is your friend / moving from 6.x to 9.x

Curry Kenworthy wrote: > Richard: > > I'd like to follow their progress [...] > > supporting the QA process benefits my work as well. > > Thanks, Richard! Yes, if you're not on the list for that bug, that > would superb to sign up. I thought it might be considered old or > familiar news here

Re: Refactoring is your friend / moving from 6.x to 9.x

On Sat, Jan 5, 2019 at 10:13 AM Bob Sneidar via use-livecode wrote: > > I just finished a little utility that takes accounting data export from > Toshiba copiers ...The customer LOVES us. OT You might want to contact the Cuyahoga County Recorder's Office in Ohio as they clearly have

Re: Refactoring is your friend / moving from 6.x to 9.x

Richard: > I'd like to follow their progress [...] > supporting the QA process benefits my work as well. Thanks, Richard! Yes, if you're not on the list for that bug, that would superb to sign up. I thought it might be considered old or familiar news here since tests and observations had

Re: Refactoring is your friend / moving from 6.x to 9.x

Curry Kenworthy wrote: > http://curryk.com/NeverGonna.mp4 Thank you for the link to test results relating to specific issues. What bug reports can I find those test stacks attached to? I'd like to follow their progress, and perhaps re-run them to see where there may have been changes after

Re: Refactoring is your friend / moving from 6.x to 9.x

Richard: > Is there an actual list of concrete concerns here [...] > or did I just spend an hour reading that I'll never get back? > I feel rickrolled. A profound question, my friend. :D You may notice something special about the following link, adapted in honor of the situation:

Re: Refactoring is your friend / moving from 6.x to 9.x

+1 I'm just elated I can write apps again after such a long drought from Hypercard, and the disappointment I had with Supercard. I personally think LC is what Hypercard should ALWAYS have been, or would have become had Apple had kept it up, or had someone else taken it up. Now I do not develop

Re: Refactoring is your friend / moving from 6.x to 9.x

On 1/4/19 3:40 AM, Malte Pfaff-Brill via use-livecode wrote: Actually I did not expect this thread to turn into philosophical discussions. What I was searching for was input on gotchas you guys and girls may have experienced when moving from the monolith engine to the refactored one., so

Re: Refactoring is your friend / moving from 6.x to 9.x

> Of course, the latter is making the assumption that > Malte has a Retina mac... Indeed he has (now and did not back in the days where the app was written) Actually I did not expect this thread to turn into philosophical discussions. What I was searching for was input on gotchas you guys and

Re: Refactoring is your friend / moving from 6.x to 9.x

On 2019-01-04 09:03, Kay C Lan via use-livecode wrote: So what I can't confirm is whether PR6671 has been implemented into a current version of LC9, but what I will say is this, if it hasn't then Malte can look forward to an eventual speed improvement in large Array operations as Mark Wa has

Re: Refactoring is your friend / moving from 6.x to 9.x

On 2019-01-04 07:40, Richard Gaskin via use-livecode wrote: Read through this whole thread, optimistic that I'd find the list of things that differentiate v6 and v9 so we can hone in on actual solutions. I learned two things: - lock/unlock changed Except it hasn't - lock/unlock screen work

Re: Refactoring is your friend / moving from 6.x to 9.x

On Fri, Jan 4, 2019 at 6:03 PM Richard Gaskin via use-livecode wrote: > Is there an actual list of concrete concerns here that the team may be > able to take action on ... I think the closest would be: >Malte wrote: >Not yet fixable for me: >Array operations on larger data sets still slower

Re: Refactoring is your friend / moving from 6.x to 9.x

Geoff Canyon wrote: > I wasn't sure what people were talking about with lock screen > performance issues, so I did a simple test ... > ...and found that in 6.7.3 that change increased the duration to about > 1.25 seconds -- a performance hit of about 30x just because a locked- > screen button is

Re: Refactoring is your friend / moving from 6.x to 9.x

I wasn't sure what people were talking about with lock screen performance issues, so I did a simple test: I set up a button to either lock the screen once, or twice, and then timed setting the loc of the button while the screen was locked. I didn't time locking the screen; just the movement while

Re: Refactoring is your friend / moving from 6.x to 9.x

Read through this whole thread, optimistic that I'd find the list of things that differentiate v6 and v9 so we can hone in on actual solutions. I learned two things: - lock/unlock changed - It's apparently easier to write a thousands of words philosophizing about how a small team of C++

Re: Refactoring is your friend / moving from 6.x to 9.x

Sorry Bob (not to single you out, on the contrary thanks for your reply and sharing your experience) but just be aware I never not enter a thread lightly, nor were my words hasty. This has been a situation years in the making, with plenty of evidence behind it, and I've been many years in

Re: Refactoring is your friend / moving from 6.x to 9.x

Not to put too fine a point on this, but ALL development environments suffer from this. Even if everything is done "right", future OS enhancements, new and improved plugins, LC feature enhancements and even developer enhancements can all lend themselves to the necessity for refactoring. It

Re: Refactoring is your friend / moving from 6.x to 9.x

Bob: > This is largely due to unicode support in everything, > as I understand it. Nope, I think that was more of a prior assumption going in, and held onto despite test results to the contrary, than a conclusion derived from testing. :) Some tests were designed to rule out the effects of

Re: Refactoring is your friend / moving from 6.x to 9.x

This is largely due to unicode support in everything, as I understand it. This performance hit is, I think, completely understandable. But there definitely is/was something else going on when developing under Windows. As other threads have amply demonstrated, V9 introduced a massive performance

Re: Refactoring is your friend / moving from 6.x to 9.x

On 2019-01-03 12:13, Malte Pfaff-Brill via use-livecode wrote: It might be that I stand corrected for the behaviour of lock / unlock screen. But then I also stand puzzled on the effect it has between engines. Same code which redrew the screen within 2.5 seconds on the 5.x series took 11 secs in

Re: Refactoring is your friend / moving from 6.x to 9.x

Howdy LiveCoders, I'm very happy to see people succeeding, optimizing, and coming back and LiveCoding. That's heartwarming. But I'm making one of my rare appearances here, chiming in lest this thread end while consisting only of celebrating extra work that was put in to overcome

Re: Refactoring is your friend / moving from 6.x to 9.x

I'm curious if issuing a new screen lock inadvertently and for an instant unlocks the screen and a redraw happens? Not the desired effect obviously but that would explain things somewhat. Bob S > On Jan 3, 2019, at 03:13 , Malte Pfaff-Brill via use-livecode > wrote: > > It might be that I

Re: Refactoring is your friend / moving from 6.x to 9.x

It might be that I stand corrected for the behaviour of lock / unlock screen. But then I also stand puzzled on the effect it has between engines. Same code which redrew the screen within 2.5 seconds on the 5.x series took 11 secs in 8/9. After debugging libraries. Being used to make sure that

Re: Refactoring is your friend / moving from 6.x to 9.x

On Mon, Dec 31, 2018 at 9:17 AM Mark Wieder via use-livecode wrote: > > Yes, it is definitely a change in behavior. I want to strongly disagree with your conclusion here ;-) > > This isn't the only place where the dictionary is wrong. My 9.0.2 Dictionary quite clearly states for the property

Re: Refactoring is your friend / moving from 6.x to 9.x

I first saw this loop in a script by Brett Sher, who called it "unlockReally", so you're close. :) (I accidentally put this response in the wrong thread at first where it doesn't make any sense, sorry about that.) -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software |

Re: Refactoring is your friend / moving from 6.x to 9.x

I first saw this loop in a script by Brett Sher, who called it "unlockReally", so you're close. :) -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On January 2, 2019 5:26:09 AM Andre Garzia via use-livecode wrote: That loop is

Re: Refactoring is your friend / moving from 6.x to 9.x

only sqLite. Bob S > On Dec 31, 2018, at 13:32 , J. Landman Gay via use-livecode > wrote: > > I'm generally deficient when it comes to databases but curious how one > creates a memory based one. Is there a trick, and does it work with others > besides sql? > > This is probably a newbie

Re: Refactoring is your friend / moving from 6.x to 9.x

put revOpenDatabase("sqlite",":memory:") into tDBID Bob S > On Dec 31, 2018, at 13:32 , J. Landman Gay via use-livecode > wrote: > > I'm generally deficient when it comes to databases but curious how one > creates a memory based one. Is there a trick, and does it work with others > besides

Re: Refactoring is your friend / moving from 6.x to 9.x

What if you accidentally use the wrong name reference, then want to change it? Bob S > On Dec 31, 2018, at 10:38 , Geoff Canyon via use-livecode > wrote: > >> I wish we had better refactoring tools >> so that we could rename a handler and all code that called that handler >> was fixed, or

Re: Refactoring is your friend / moving from 6.x to 9.x

> Is there a way to "safely" add to LC contextual menu in the script editor? Yes! It is in a script-only stack behavior of the editor field: https://github.com/livecode/livecode-ide/blob/develop/Toolset/palettes/script%20editor/behaviors/revseeditorbehavior.livecodescript#L1024 There is also the

Re: Refactoring is your friend / moving from 6.x to 9.x

Bob, Yes but it is not as ergonomic. Let me tell an example from a different platform. I was working in WebStorm IDE in a JavaScript project. I was refactoring a ton of it. One of the functions worked better with a different parameter order than what I originally used. I could select the

Re: Refactoring is your friend / moving from 6.x to 9.x

That loop is briliant. I am tempted to place it into a command called "unlockScreenForReal" On Mon, Dec 31, 2018, 16:38 dunbarxx via use-livecode < use-livecode@lists.runrev.com wrote: > Not sure if this is still relevant in LC, but in HC, lock screen commands > were queued. So the fix, so that

Re: Refactoring is your friend / moving from 6.x to 9.x

Malte, I think the info you were probably looking for is buried within the dictionary entry for the “lockScreen” Property, maybe this should be referenced a little better in the dictionary entries for “lock screen” and “unlock screen”, see below: LiveCode keeps count of how many times the

Re: Refactoring is your friend / moving from 6.x to 9.x

ion Services > rdim...@evergreeninfo.net > > -Original Message- > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf > Of J. Landman Gay via use-livecode > Sent: Monday, December 31, 2018 4:32 PM > To: How to use LiveCode > Cc: J. Landma

RE: Refactoring is your friend / moving from 6.x to 9.x

runrev.com] On Behalf Of J. Landman Gay via use-livecode Sent: Monday, December 31, 2018 4:32 PM To: How to use LiveCode Cc: J. Landman Gay Subject: Re: Refactoring is your friend / moving from 6.x to 9.x I'm generally deficient when it comes to databases but curious how one creates a memory

Re: Refactoring is your friend / moving from 6.x to 9.x

I'm generally deficient when it comes to databases but curious how one creates a memory based one. Is there a trick, and does it work with others besides sql? This is probably a newbie question. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software |

Re: Refactoring is your friend / moving from 6.x to 9.x

On 12/30/18 8:52 PM, Tom Glod via use-livecode wrote: and definitely had a couple of "how did this code ever work?" moments ...heh...been there... -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list

Re: Refactoring is your friend / moving from 6.x to 9.x

On Sun, Dec 30, 2018 at 11:58 AM Andre Alves Garzia via use-livecode < use-livecode@lists.runrev.com> wrote: > I wish we had better refactoring tools > so that we could rename a handler and all code that called that handler > was fixed, or stuff such as rename variable... > One of the reasons I

Re: Refactoring is your friend / moving from 6.x to 9.x

Find/Replace works great. I've done it a few times, so long as the thing you are finding has a unique name that cannot be a part of any other bit of code, you should be fine. Backup your stack of course before doing something so drastic. A while ago, the LC dev team optimized the search

Re: Refactoring is your friend / moving from 6.x to 9.x

For multiple recursions into an array I came up with a method for loading an array into a memory based sql database. Subsequent queries take less time, depending of course on how complex they are, but you can do lots of cool thinks, like complex filtering / sorts, calculations, etc. to a

Re: Refactoring is your friend / moving from 6.x to 9.x

> Craig wrote: > Not sure if this is still relevant in LC, but in HC, lock screen > commands were queued. So the fix, so that one did not have to count > the number of locks through perhaps several handlers, was: > > repeat until the lockScreen is false >unlock screen > end repeat Yes! Or

Re: Refactoring is your friend / moving from 6.x to 9.x

Not sure if this is still relevant in LC, but in HC, lock screen commands were queued. So the fix, so that one did not have to count the number of locks through perhaps several handlers, was: repeat until the lockScreen is false unlock screen end repeat Craig -- Sent from:

Re: Refactoring is your friend / moving from 6.x to 9.x

In 6.7.3 on a Mac, this results in true for me. Checked in 5.0, also resulted in true. On Sun, Dec 30, 2018 at 1:26 PM Malte Pfaff-Brill via use-livecode < use-livecode@lists.runrev.com> wrote: > > Regarding lock screen, here is one simple example: > > on mouseUp > lock screen >

Re: Refactoring is your friend / moving from 6.x to 9.x

a very interesting thread ...lots to learn. I refactored a project from 7 to 9 and definitely had a couple of "how did this code ever work?" moments, meaning i found the most recent versions of the engine to be more strict with syntax. As far as performance comparisons I don't have a lot to

RE: Refactoring is your friend / moving from 6.x to 9.x

Task: Add ellipses if text does not fit visible field width. V4, v5 and v6 I put the data into the field and then looped thru the lines. If text was too wide I chopped off 1/2 of the overflow chars(rough guess) and then iterated what was left using the formattedwidth as the last chars were

Re: Refactoring is your friend / moving from 6.x to 9.x

On 12/30/18 1:55 PM, Malte Pfaff-Brill via use-livecode wrote: Hey Mark, At least it is behaviour that changed between engine releases. :-) Thinking of a counter here is a good way to describe the behaviour, however, it is not what is written in the dictionary. Yes, it is definitely a change

Re: Refactoring is your friend / moving from 6.x to 9.x

Hey Mark, At least it is behaviour that changed between engine releases. :-) Thinking of a counter here is a good way to describe the behaviour, however, it is not what is written in the dictionary. "unlock screen Sets the lockScreen property to false, updating the screen and displaying any

Re: Refactoring is your friend / moving from 6.x to 9.x

On 12/30/18 1:25 PM, Malte Pfaff-Brill via use-livecode wrote: Hi Kaveh, Thanks for the kind words. :-) Regarding lock screen, here is one simple example: on mouseUp lock screen subhandler unlock screen answer the lockscreen end mouseUp on subhandler

Re: Refactoring is your friend / moving from 6.x to 9.x

Hi Kaveh, Thanks for the kind words. :-) Regarding lock screen, here is one simple example: on mouseUp lock screen subhandler unlock screen answer the lockscreen end mouseUp on subhandler lock screen — other stuff may follow, but do not unlock

Re: Refactoring is your friend / moving from 6.x to 9.x

I don't think LiveCode without Malte is really LiveCode, so glad you are back. :-) Could you pls elaborate on the lock screen strategy? You said we should not nest, and you also said that screen will not immediately be unlocked after a handler. I was under the impression that multiple locks were

Re: Refactoring is your friend / moving from 6.x to 9.x

Malte, So happy that you're back here my friend. I too spent some time away. So, refactoring and constantly trying to erase mistakes of my past coding self are a constant here. I wish we had better refactoring tools so that we could rename a handler and all code that called that handler was