I'm too lazy to look it up and I don't remember the exact details, but I believe you can change the 4th argument to 3 and it will not set edit mode, ala:

pd-$1data-marker donecanvasdialog 1 1 3 0 0 110 110 $2 $3 0 0 1 1 1;


3 is the key. If this is a different issue, sorry for the noise.

On Dec 14, 2018, at 9:36 AM, pd-list-request@lists.iem.at wrote:

Date: Fri, 14 Dec 2018 10:21:26 -0500
From: JTG III <jordanthomasgibbonsiii@gmail.com>
To: João Pais <jmmmpais@gmail.com>
Cc: "pd-list@lists.iem.at" <pd-list@mail.iem.at>, Miller Puckette
<msp@ucsd.edu>
Subject: Re: [PD] Pd Vanilla donecanvasdialog GOP starts edit mode
Message-ID:
<CAGbW+N=k2V4abfEUhyXXBsSbr719dW4cG2EpMBT=NuzLccvyBw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

yeah, I brought this up when pd-0.49,  or whatever it's going by these
days, was released, it seems to be something that was imported from L2ork
along with the infinite undo, perhaps, or maybe some other new, uh, smart
editing feature,  which I seem to be too simple to get much out of except
frustration, though I'm still using 0.48-2 and maybe I haven't given it a
chance yet.

On Thu, Dec 13, 2018, 9:09 PM João Pais, <jmmmpais@gmail.com> wrote:

Hello list,

I just noticed something new: when sending a donecanvasdialog message to a
subpatch in a GOP, it starts editmode in the parent patch. Afaik, this
wasn't the previous behaviour (it still isn't in pd extended).

Here is a patch to illustrate the problem. Doesn't happen with coords,
though.

Best,

Joao

--------
Dan Wilcox
@danomatika
danomatika.com
robotcowboy.com