Project

General

Profile

Bug #9366

How to commit files after editing

Added by Vadim Mutilin 4 months ago. Updated 4 months ago.

Status:
Open
Priority:
Urgent
Category:
Bridge
Target version:
Start date:
11/07/2018
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

I've opened file job.json for editing and changed it.
After that I'm pressing 'Save' button, but the pop up dialog says "Are you sure? The file you changed is not commited".
I do not see any button to commit changes

klever-absent-commit-file.png (95.3 KB) klever-absent-commit-file.png Vadim Mutilin, 11/07/2018 06:54 PM

History

#1 Updated by Ilja Zakharov 4 months ago

  • Status changed from New to Closed

To save files use ctrl+s shortcut. This is correct behavior.

P.S. cannot reject the bug, so keep the status as is.

#2 Updated by Vadim Mutilin 4 months ago

This looks ugly and user unfriendly

#3 Updated by Evgeny Novikov 4 months ago

  • Status changed from Closed to Rejected

#4 Updated by Evgeny Novikov 4 months ago

  • Assignee set to Vladimir Gratinskiy
  • Status changed from Rejected to Open

I thought more about this, let's fix the warning message first of all, since there is no more button "commit", but users need to press "Ctrl+s". In addition, it would be great that Bridge will show this warning in any case when users may loose changes. For instance, when I open another file for editing, changes in the first one are lost.

Also available in: Atom PDF