Find-dialog remnants after macro execution, macOS

[JairoMartinezA]

Hi Alex,

If you can replicate this issue:

I have the next text extract:

{"Estatus":1,"Mensaje":"{\"idServicio\":\"4182223\",\"tripnumber\":\"10786\"}"}

And I have a macro with these replace commands:

{
    "ver": "20151204",
    "list": [
        {
            "id": 89825,
            "nm": "CleanJSON",
            "rec": "",
            "evl": [
                "ed.cmd(cmds.cmd_FinderAction,'repall\\x01\\\\\"\\x01\"\\x01')",
                "ed.cmd(cmds.cmd_FinderAction,'repall\\x01:\"{\"\\x01:{\"\\x01')",
                "ed.cmd(cmds.cmd_FinderAction,'repall\\x01\":\"[{\\x01\":[{\\x01')",
                "ed.cmd(cmds.cmd_FinderAction,'repall\\x01]\"}\\x01]}\\x01')",
                "ed.cmd(cmds.cmd_FinderAction,'repall\\x01}\"}\\x01}}\\x01')"
            ]
        }
    ],
    "dlg_prs": {},
    "tm_ctrl": {
        "rp_ctrl": 300,
        "tm_wait": 10
    }
}

After the macro execution, CudaText paints this:

[Alexey-T]

did not repro on linux. seems the Find dlg remnants? what if you make option "find_separate_form":true ?

[JairoMartinezA]

Correct, with that setting, the "issue" dissapears.

[Alexey-T]

btw, I dont see that Find dlg is showing by itself on macro running (in debugger). did you have Find dlg shown before macro run? did it hide by itself?

[JairoMartinezA]

No, the Find Dialog starts as hidden.

[Alexey-T]

Original issue - is it still here? Maybe Lazarus changes fixed it?

[JairoMartinezA]

Hi Alex,

The issue is still present. Internally my macro makes some replaces:

# CleanJSONFormat [Shift+Meta+Alt+L]
ed.cmd(cmds.cmd_FinderAction,'repall\x01\\"\x01"\x01')
ed.cmd(cmds.cmd_FinderAction,'repall\x01:"{"\x01:{"\x01')
ed.cmd(cmds.cmd_FinderAction,'repall\x01":"[{\x01":[{\x01')
ed.cmd(cmds.cmd_FinderAction,'repall\x01]"}\x01]}\x01')
ed.cmd(cmds.cmd_FinderAction,'repall\x01}"}\x01}}\x01')
app.app_proc(app.PROC_EXEC_PLUGIN, 'cuda_fmt,format,')

And indeed, is related to the Find/Replace dialog

[Alexey-T]

Hi @rich2014, sorry to bother, but I don't have Mac setup yet. can you reproduce the issue in CudaText with Macros plugin? (with specified macros which calls CudaFormatter plugin).

[JairoMartinezA]

Alex, in my case, in the latest builds of CudaText, I cannot see the error. I just checked right now and I don't see the error.

[Alexey-T]

So it was fixed in the meantime, in Lazarus... Closing..