Code: Select all
repeat for each line aLine in tCollect
Code: Select all
repeat for each line aLine in pScript
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Code: Select all
repeat for each line aLine in tCollect
Code: Select all
repeat for each line aLine in pScript
Yes, the latter's correct.mwieder wrote: ↑Thu Aug 24, 2023 4:38 pm?shouldn't that readCode: Select all
repeat for each line aLine in tCollect
Code: Select all
repeat for each line aLine in pScript
Mark,mwieder wrote: ↑Thu Aug 24, 2023 4:38 pm?shouldn't that readCode: Select all
repeat for each line aLine in tCollect
Code: Select all
repeat for each line aLine in pScript
Code: Select all
put replaceText(pScript,"\/\*[\s\S]*?\*\/","") into pScript
Code: Select all
on actionInspect pPathToNode
actionDoubleClick pPathToNode
end actionInspect
Code: Select all
if pLookFor is not in tScript then return 0
Ah. I missed that feature. Yes, that's a nice touch.The one new feature I like best is the colorization of the path when clicking on a node. That helps a lot in interpreting the diagram when drilling down the dependencies.
That's good! But I may have been a little unclear in my explanation and/or labelling:
Yes, the standard setting should be (as it is now) that commented-out handlers are ignored. It doesn't make much sense to see them in the lists or flowchart. But I'll leave in the possibility to turn that filter off, just in case someone wants that.jacque wrote: ↑Wed Aug 30, 2023 10:07 pmJust tried version 1.1.3, it's terrific. The colored lines make it so much easier to trace paths. I tried with and without commented code and the speed didn't seem any different to me, but the flowchart seemed less complex with the option to omit commented handlers turned on. My test stack has a lot of commented handlers. Some are duplicates I kept for reference in case my changes didn't work, but others are independent handlers I no longer needed. So there is a difference there. I'd leave the option available I think in case others keep extra junk in their scripts like I do. (On final release I try to remove the unused stuff but during development I always think I might need it later.)
Oh yes, I've put some effort into the responsive design, and it's been in there since the early days really. I deliver the stack in it's minimum size just in case someone opens it on a laptop, but it's definitely easier to use on a large screen.This tool is becoming very professional. I was delighted to discover I can resize the mainstack as well as the flowchart. That makes long lists much easier to read.
I'm almost positive that I know what your blank flowchart problem is. It happened to me as well. It's actually nothing wrong at all: I bet you have unticked the Limit width box, right? And then a very large flowchart is produced, but your view in the browser widget is naturally scrolled to the top left when it loads. Enlarge the flowchart window, and/or try scrolling down and to the right, and you'll soon start seeing some nodes. Big flowcharts can have big areas of white space, it all depends on the code structure.I can't recall which monster script I used originally but this one has 75 handlers and a couple thousand lines. I didn't get the text limit warning.
I next tested a truly monster stack with 332 handler names. It analyzed correctly but I couldn't make a flowchart. No errors, but the window didn't display anything, it just remained blank. I added an extra zero to the character limit but that didn't help. Commented handlers were omitted. I also filtered out four or five handlers but I needed to see the others.
Still, this is a great tool.
You are exactly right. The chart is there but in this case it is too large to view even fullscreen on my 27" monitor. But yup, all good. I will practice scrolling.I'm almost positive that I know what your blank flowchart problem is.
*hmac* should do the trick.jacque wrote: ↑Thu Aug 31, 2023 7:55 pmFor the exclusions, I want to exclude everything containing the string "hmac" but I'm not sure what to use. I tried these variations without success:
.*hmac.*
*hmac*
My regex knowlege is pretty limited. The handlers I want to exclude are all in a library substack. Is there a way to exclude the entire substack?