-
Notifications
You must be signed in to change notification settings - Fork 11
Description
Checked for duplicates
Yes - I've already checked
Is this a regression?
No - This is a new bug
Version
4.0.0
Describe the bug
This is a workflow concern raised by Parker...
The sequence editor defaults to .txt (instead of .seq) – it does this in two ways: 1) when you first open a workspace, there is a untitled .txt file in the editor pane where you can start typing directly; and 2) when you add a new file (by clicking "+"), you get a .txt file unless you add the .seq extension to the file name (which then cannot be changed after).
The user perspective from Clipper is that this is firstly a sequence editor (which can also handle .txt files), and so a sequence file type should be the assumed default. Parker also runs into the following workflow issue when trying to quickly spin up a sequence for testing: he opens a workspace and starts typing into the empty untitled file but because it's a .txt file, he doesn't get the hinting features associated with the command dictionary unless he saves the file first (adding ".seq" to the file name).
Reproduction
Open or create a Workspace and start typing into the empty untitled file; or click "+" then "New File" and give the file a name without the .seq extension.
Logs
System Info
ChromeSeverity
Minor