Page 1 of 1
Problems mentioned over there, #1
Posted: Sun Mar 09, 2025 7:25 pm
by richmond62
https://forums.livecode.com/viewtopic.p ... 62#p233462
The "Replace" controls get disabled if you have selected anything but "Current tab" or "All tabs". It's always been like this, as far as I know.
This refers to
SEARCH AND REPLACE in the scriptEditor.
Is it possible that all the other options (err: why are they present if they do NOT work) can be activated:
-

- Screenshot 2025-03-09 at 21.22.59.jpg (188.93 KiB) Viewed 5424 times
Re: Problems mentioned over there, #1
Posted: Sun Mar 09, 2025 8:40 pm
by tperry2x
Yes, if you choose anything other than "current tab" / "all tabs" - then the options are disabled.
However, the find and replace which you find at the bottom of the standard edit menu when viewing a stack seems to be able to process find and replaces in stacks... so, I wonder if it's worth showing this expanded find & replace if you were to choose any other options instead?

- 2025-03-09-20-37-06.png (38.82 KiB) Viewed 5411 times
Re: Problems mentioned over there, #1
Posted: Sun Mar 09, 2025 9:19 pm
by richmond62
What really amazes me is that this has never been brought up 'over there' in donkey's years.
Re: Problems mentioned over there, #1
Posted: Sun Mar 09, 2025 9:40 pm
by tperry2x
The more stones we turn over, the more bugs we are likely to find
It does make me wonder how far back this happens. Has it always been the case, or is it something that crept in at version 9 for example. I'll have to do some testing.
Re: Problems mentioned over there, #1
Posted: Mon Mar 10, 2025 12:55 pm
by axwald
Hi,
always thought it makes sense that you need to have the script open to be able to "Replace" - after all you need to "Apply" (error checking!) after anyways.
Funny, in all these years I never discovered the "Find" (Ctrl-F) with a stack in front - I always searched from the ScriptEditor where "Ctrl-F" has another function, and "Ctrl-Shift-F" brings the "lesser Replace". There's some quite useful options that I missed.
But I don't know if I'd be comfortable to mass-replace in scripts w/o being able to inspect the context first. Especially when it always just targets the topstack, without any indication what that is at the moment (it doesn't stay with the stack you called it for!).
Observations made in LC 6.7.10.
Re: Problems mentioned over there, #1
Posted: Mon Mar 10, 2025 1:19 pm
by richmond62
Observations made in LC 6.7.10.
Um?
Re: Problems mentioned over there, #1
Posted: Mon Mar 10, 2025 8:02 pm
by axwald
Above my post, tperyy2x wondered:
It does make me wonder how far back this happens. Has it always been the case, or is it something that crept in at version 9 for example.
Now he knows how far it goes back, at least ;-)
Re: Problems mentioned over there, #1
Posted: Tue Mar 11, 2025 7:24 pm
by tperry2x
axwald wrote: ↑Mon Mar 10, 2025 8:02 pm
Now he knows how far it goes back, at least
Wow. Yonks then.
How about we go for the simple fix and just limit the find & replace in the script editor to the top two options (disabling / commenting out the rest). Leaving the find and replace to the main one you find in the edit menu when in a stack?
Re: Problems mentioned over there, #1
Posted: Tue Mar 11, 2025 7:47 pm
by axwald
Hi,
tperry2x wrote: ↑Tue Mar 11, 2025 7:24 pm
How about we go for the simple fix and just limit the find & replace in the script editor to the top two options (disabling / commenting out the rest).
Why? These options are needed to find something! Then you can locate the hits in the scripts, close the scripts you don't want to touch, switch the popup and replace in all tabs.
The problem is that the one popup is used in 2 different ways: First "where to search", and then "where to replace", so you need to readjust every time. Sloppy design. There should be a second popup for "where to replace".
.
tperry2x wrote: ↑Tue Mar 11, 2025 7:24 pm
Leaving the find and replace to the main one you find in the edit menu when in a stack?
This one (that I only found due to your post!) looks very promising, but I cannot help to feel uncomfortable with it. Call it on a stack, minimize this stack, and it searches (& replaces?) in the one below, w/o telling you ...