Just another remark. I took a quick look at gedit. Their info bar has two<br>
buttons: &quot;Reload&quot; and &quot;Ignore&quot;. The buffer is also unmodifiable. After I<br>
press Ignore and tried to save I got another info bar with  buttons: &quot;Save<br>
anyway&quot; and  &quot;Don&#39;t save&quot;.  (That was basically my very first point. But,<br>
you explained why gedit and geany behaviors are different )<br>
However, if you found that the result is in fact &quot;terrible&quot;, no problem,<br>
we definitely can leave everything as is.<br>
<br>
On Tue, Oct 30, 2018 at 10:53 PM Yury Dubinsky &lt;yury.dubinsky@gmail.com&gt;<br>
wrote:<br>
<br>
&gt; Well, just one more remark. Currently after the Info bar appears the<br>
&gt; buffer becomes unmodifiable.So, we can&#39;t do anything with the content<br>
&gt; until we make a decision. Isn&#39;t it?<br>
&gt;<br>
&gt; On Tue, Oct 30, 2018 at 5:39 PM elextr &lt;notifications@github.com&gt; wrote:<br>
&gt;<br>
&gt;&gt; No, &quot;Undecided&quot; is not a good button label. I suggested it as a way to<br>
&gt;&gt; try to gently imply that I thought the whole thing was getting silly. Sorry<br>
&gt;&gt; that you took it seriously.<br>
&gt;&gt;<br>
&gt;&gt; Info bars are meant to convey information that is important but not<br>
&gt;&gt; urgent, it does not need immediate resolution. So info bars deliberately do<br>
&gt;&gt; not stop normal operations, unlike dialogs which must be actioned<br>
&gt;&gt; immediately. Thats why the file change notification was moved from a dialog<br>
&gt;&gt; to an info bar. The fact that the file on disk has changed does not need to<br>
&gt;&gt; be actioned immediately, the info bar does not need to be dismissed,<br>
&gt;&gt; editing can continue and the bar remains as a reminder. So info bars should<br>
&gt;&gt; not occupy large amounts of screen space and by that criteria I am afraid<br>
&gt;&gt; the result is in fact &quot;terrible&quot;.<br>
&gt;&gt;<br>
&gt;&gt; The button label &quot;Cancel&quot; is the standard GUI button label for &quot;close and<br>
&gt;&gt; do nothing&quot; so that is what that button should be (in English anyway).<br>
&gt;&gt;<br>
&gt;&gt; Since info bars do not block the user interface (unlike dialogs) the user<br>
&gt;&gt; is not restricted to just the options the info bar provides. So there is no<br>
&gt;&gt; need to provide copious options on the info bar. As @codebrainz<br>
&gt;&gt; &lt;https://github.com/codebrainz&gt; pointed out you still have access to the<br>
&gt;&gt; normal features of the application. For example, in the case of an<br>
&gt;&gt; unexpected file change notification a user could decide to load the changed<br>
&gt;&gt; file into another buffer to look at it, see what changed, and decide what<br>
&gt;&gt; to do. The info bar does not need a &quot;Load file into another buffer&quot; button<br>
&gt;&gt; to allow them to do that.<br>
&gt;&gt;<br>
&gt;&gt; The info bar should only have &quot;Cancel&quot; and maybe the most common<br>
&gt;&gt; operation available as a convenience.<br>
&gt;&gt;<br>
&gt;&gt; —<br>
&gt;&gt; You are receiving this because you modified the open/close state.<br>
&gt;&gt; Reply to this email directly, view it on GitHub<br>
&gt;&gt; &lt;https://github.com/geany/geany/issues/1885#issuecomment-434479890&gt;, or mute<br>
&gt;&gt; the thread<br>
&gt;&gt; &lt;https://github.com/notifications/unsubscribe-auth/Al5v5M8yzmmKBGNlxkUU3aSbklH-PxPuks5uqMcJgaJpZM4UsYx0&gt;<br>
&gt;&gt; .<br>
&gt;&gt;<br>
&gt;<br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/1885#issuecomment-434548466">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ_O_b0k7PfuD1ZMZp79GAZQ63Vv0ks5uqRh9gaJpZM4UsYx0">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJxA4cvs99cpkE7zOvfX08ArGXYD-ks5uqRh9gaJpZM4UsYx0.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@dyura in #1885: Just another remark. I took a quick look at gedit. Their info bar has two\nbuttons: \"Reload\" and \"Ignore\". The buffer is also unmodifiable. After I\npress Ignore and tried to save I got another info bar with  buttons: \"Save\nanyway\" and  \"Don't save\".  (That was basically my very first point. But,\nyou explained why gedit and geany behaviors are different )\nHowever, if you found that the result is in fact \"terrible\", no problem,\nwe definitely can leave everything as is.\n\nOn Tue, Oct 30, 2018 at 10:53 PM Yury Dubinsky \u003cyury.dubinsky@gmail.com\u003e\nwrote:\n\n\u003e Well, just one more remark. Currently after the Info bar appears the\n\u003e buffer becomes unmodifiable.So, we can't do anything with the content\n\u003e until we make a decision. Isn't it?\n\u003e\n\u003e On Tue, Oct 30, 2018 at 5:39 PM elextr \u003cnotifications@github.com\u003e wrote:\n\u003e\n\u003e\u003e No, \"Undecided\" is not a good button label. I suggested it as a way to\n\u003e\u003e try to gently imply that I thought the whole thing was getting silly. Sorry\n\u003e\u003e that you took it seriously.\n\u003e\u003e\n\u003e\u003e Info bars are meant to convey information that is important but not\n\u003e\u003e urgent, it does not need immediate resolution. So info bars deliberately do\n\u003e\u003e not stop normal operations, unlike dialogs which must be actioned\n\u003e\u003e immediately. Thats why the file change notification was moved from a dialog\n\u003e\u003e to an info bar. The fact that the file on disk has changed does not need to\n\u003e\u003e be actioned immediately, the info bar does not need to be dismissed,\n\u003e\u003e editing can continue and the bar remains as a reminder. So info bars should\n\u003e\u003e not occupy large amounts of screen space and by that criteria I am afraid\n\u003e\u003e the result is in fact \"terrible\".\n\u003e\u003e\n\u003e\u003e The button label \"Cancel\" is the standard GUI button label for \"close and\n\u003e\u003e do nothing\" so that is what that button should be (in English anyway).\n\u003e\u003e\n\u003e\u003e Since info bars do not block the user interface (unlike dialogs) the user\n\u003e\u003e is not restricted to just the options the info bar provides. So there is no\n\u003e\u003e need to provide copious options on the info bar. As @codebrainz\n\u003e\u003e \u003chttps://github.com/codebrainz\u003e pointed out you still have access to the\n\u003e\u003e normal features of the application. For example, in the case of an\n\u003e\u003e unexpected file change notification a user could decide to load the changed\n\u003e\u003e file into another buffer to look at it, see what changed, and decide what\n\u003e\u003e to do. The info bar does not need a \"Load file into another buffer\" button\n\u003e\u003e to allow them to do that.\n\u003e\u003e\n\u003e\u003e The info bar should only have \"Cancel\" and maybe the most common\n\u003e\u003e operation available as a convenience.\n\u003e\u003e\n\u003e\u003e —\n\u003e\u003e You are receiving this because you modified the open/close state.\n\u003e\u003e Reply to this email directly, view it on GitHub\n\u003e\u003e \u003chttps://github.com/geany/geany/issues/1885#issuecomment-434479890\u003e, or mute\n\u003e\u003e the thread\n\u003e\u003e \u003chttps://github.com/notifications/unsubscribe-auth/Al5v5M8yzmmKBGNlxkUU3aSbklH-PxPuks5uqMcJgaJpZM4UsYx0\u003e\n\u003e\u003e .\n\u003e\u003e\n\u003e\n"}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1885#issuecomment-434548466"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/1885#issuecomment-434548466",
"url": "https://github.com/geany/geany/issues/1885#issuecomment-434548466",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [geany/geany] An insufficient behavior when an open file was updated outside Geany (#1885)",
"sections": [
{
"text": "",
"activityTitle": "**dyura**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@dyura",
"facts": [

]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"geany/geany\",\n\"issueId\": 1885,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"geany/geany\",\n\"issueId\": 1885\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/geany/geany/issues/1885#issuecomment-434548466"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 347180148\n}"
}
],
"themeColor": "26292E"
}
]</script>