Re: [pgadmin-hackers] [pgAdmin4][Patch]: RM #1807 Query Tool Does NotRecognize When File Changes Have Been Saved - Mailing list pgadmin-hackers

From Dave Page
Subject Re: [pgadmin-hackers] [pgAdmin4][Patch]: RM #1807 Query Tool Does NotRecognize When File Changes Have Been Saved
Date
Msg-id CA+OCxoye7d0F8dt8UKAQan2b+fzVB=v919=MTkwVZ4R-wx3Hug@mail.gmail.com
Whole thread Raw
In response to [pgadmin-hackers] [pgAdmin4][Patch]: RM #1807 Query Tool Does Not Recognize When FileChanges Have Been Saved  (Akshay Joshi <akshay.joshi@enterprisedb.com>)
Responses Re: [pgadmin-hackers] [pgAdmin4][Patch]: RM #1807 Query Tool Does NotRecognize When File Changes Have Been Saved  (Akshay Joshi <akshay.joshi@enterprisedb.com>)
List pgadmin-hackers
Hi

On Fri, Dec 16, 2016 at 8:47 AM, Akshay Joshi <akshay.joshi@enterprisedb.com> 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

pgadmin-hackers by date:

Previous
From: Ashesh Vashi
Date:
Subject: [pgadmin-hackers] Re: PATCH: RM# 1679 - Background process for "restore" not reportingstatus back to pgAdmin
Next
From: Dave Page
Date:
Subject: [pgadmin-hackers] pgAdmin 4 commit: Show index columns in the correct order in RE-SQL.Fi