Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cHr4P-0008CZ-TH for pgadmin-hackers@arkaria.postgresql.org; Fri, 16 Dec 2016 11:53:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cHr4P-0006TH-3Y for pgadmin-hackers@arkaria.postgresql.org; Fri, 16 Dec 2016 11:53:01 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cHr4O-0006TA-86 for pgadmin-hackers@postgresql.org; Fri, 16 Dec 2016 11:53:00 +0000 Received: from mail-io0-x22e.google.com ([2607:f8b0:4001:c06::22e]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cHr4G-0000WB-5u for pgadmin-hackers@postgresql.org; Fri, 16 Dec 2016 11:52:58 +0000 Received: by mail-io0-x22e.google.com with SMTP id h30so95014977iod.2 for ; Fri, 16 Dec 2016 03:52:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zIWqODsi3Ez0z/SmUkp0fmuMP9JL9qw9+De+vv/PW5s=; b=HkDhhrI0ehpb8OSU9SdvLrozqlG45EZ2+7y6On2b2nQnasVI9g9oS7FNAoziNOf1++ q1+nPBjvVAyolUCM/3L1ZIMhzBznnGp8GSVtlJAmSPMyuJu6DyMnh6SRJq2GSDuR9UiV sxvUyIxvckbzsBg+pgWVEFAosDL9uz/y2LVP+AgZBjp3xB56P8jxlYrBKFez9haAlRGK VXPi461RZpK0pFbSb/m3ju64KeqksxhyP9Fxd/CQ5LKlzmD3lYWUmpxYy1QQLyYMLoIu ckJLOCv6q14xUaXwxIa/N/2Un87qalj5PTaYni9XSV96tVr7RcdeQWb7kqhVLnX/9vcg woPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zIWqODsi3Ez0z/SmUkp0fmuMP9JL9qw9+De+vv/PW5s=; b=Fe1D2WZLLc9zM+jpRk5CzFT7V2EDXNTjI9ZQCoTJU6q3ToMF5IEISLrGh7qYi0Jmem MRcqThNZJL/PqWW2AT5S7xsy9fcDbsi4OCD9CHI5N5VFhe7nhfBNb7DU5v5Up99rlFka HBWyD0jRnz/FN9EITGRshz5BF8gNf4S3B8smLSpuOYdk15yZI7deZQe1Fyd7Vmp89iqR XVrXHnksLlAlUO8vmqRtEQtBz59C2MADFPJ9raywmJzgyF/qoHIyrwvXUTGzuGpjXriU VG6Gc8kfzbwprKz+wGlt8wyAJJUUqIJXOMrgIiXPubDtRugA1aaUVu99dYBXch3IIs7W FsPg== X-Gm-Message-State: AIkVDXJ/BDy1vZewQH+RFiLuZHLk6IGbxdOWtRont77R718MTRTeooziPO42ax7SVk6TqyS6vFukeBB2FxZa3Q== X-Received: by 10.107.57.5 with SMTP id g5mr2131042ioa.208.1481889170988; Fri, 16 Dec 2016 03:52:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.224.198 with HTTP; Fri, 16 Dec 2016 03:52:50 -0800 (PST) In-Reply-To: References: From: Dave Page Date: Fri, 16 Dec 2016 11:52:50 +0000 Message-ID: Subject: Re: [pgAdmin4][Patch]: RM #1807 Query Tool Does Not Recognize When File Changes Have Been Saved To: Akshay Joshi Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary=001a114abd02a236930543c535a5 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --001a114abd02a236930543c535a5 Content-Type: text/plain; charset=UTF-8 Hi On Fri, Dec 16, 2016 at 8:47 AM, Akshay Joshi wrote: > Hi All > > Please find the attached patch to fix the RM #1807 Query Tool Does Not > Recognize When File Changes Have Been Saved. > If I open a file with the patch applied, and make a change (add a space to the end), it's correctly detected. If I then undo the change by deleting the space, the file is still marked as dirty. If I then clear the window entirely, the save button is disabled, but the tab still shows the file is dirty (the *). Also - the patch seems to undo the change I made in 4a280b251755091af9bf56bcdee964601df104ae. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --001a114abd02a236930543c535a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi

On Fri, Dec 16, 2016 at 8:47 AM, Akshay Joshi <<= a href=3D"mailto:akshay.joshi@enterprisedb.com" target=3D"_blank">akshay.jo= shi@enterprisedb.com> wrote:
Hi All=

Please find the attached patch to fix the RM=C2=A0#1807 Query Tool Does N= ot Recognize When File Changes Have Been Saved.

If I open a file with the patch applied, and make a change= (add a space to the end), it's correctly detected.=C2=A0
If I then undo the change by deleting the space, the file is st= ill marked as dirty.=C2=A0

If I then clear the win= dow entirely, the save button is disabled, but the tab still shows the file= is dirty (the *).

Also - the patch seems to undo = the change I made in=C2=A04a280b251755091af9bf56bcdee964601df104ae.

--
Dave Page
Blog:= http://pgsnake.b= logspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com=
The Enterprise PostgreSQL Company
--001a114abd02a236930543c535a5--