" It's like when you double-click on a file and it opens in an editor - most will not enable the save button at that point. "
I'm not sure about that claim... pretty much every application I use (MS Office suite, Adobe suite, vim, notepad, GIMP, etc.) all give you an enabled Save for any opened document, Indeed, of my commonly-used apps, the only one that does *not* enable the save button unless changes are made is Eclipse, but that's likely to be tied to the fact that it has to do incremental builds with every save, so there's probably a justification for that behaviour.
Otherwise, you have to ask "does the user actually benefit from having the Save button disabled?" If you can't come up with a really compelling reason why it shouldn't be enabled, then what's the point of going through the extra coding effort to disable something that doesn't need to be disabled (and is likely to cause confusion/annoyance)?
On 18/07/2019 14:43, Michael Shapiro wrote:
> Then what?
>
> On Thu, Jul 18, 2019 at 8:31 AM Ray O'Donnell <ray@rodonnell.ie
> <mailto:ray@rodonnell.ie>> wrote:
>
> On 18/07/2019 14:28, Michael Shapiro wrote:
> > After selecting an object (eg a view) how do I save the SQL that
> > PgAdmin4 extracts from the server? I don't see a "SAVE" button.
> >
>
> Hi there,
>
> Right-click on it in the object tree (Left of screen), then select
> Scripts -> (type of script required).
[Please keep replies on-list, and avoid top-posting - thanks.]
Now that you ask, that's a good question.... I just tried it myself
(Scripts -> Create script), and the "Save" button is greyed out.
You can activate it by making some small edit in the generated SQL, but
this seems like a bug.
Depends how you look at it. The button is looking for changes the user has made, not pre populated or loaded text. It's like when you double-click on a file and it opens in an editor - most will not enable the save button at that point.
--