Box selecting ".." in the file browser makes "Parent Directory" the default action. #63263

Closed
opened 2019-04-04 01:25:39 +02:00 by Michael Hermann · 36 comments

System Information
Operating system: Linux-5.0.5-arch1-1-ARCH-x86_64-with-arch 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56

Blender Version
Broken: version: 2.80 (sub 53), branch: blender2.7, commit date: 2019-04-02 19:53, hash: a813e259d6
Worked: (optional)

Short description of error
A box selection that includes files AND ".." turns the button on the right side to "Parent Directory" and the default action for pressing ENTER becomes going to the parent directory. ".." should be clickable, but not selectable, and the default action should always be "open" or "import" (e.g.).

Exact steps for others to reproduce the error

  1. Go to "File" > "Open"
  2. Press B to box select. Select a .blend file and ".." the parent directory.
  3. Observe the Button to the right, that turns from "Open Blender File" to "Parent Directory"
  4. Press the Button, or simply ENTER.

Works for File > Import/Expert as well. Basically everywhere.

**System Information** Operating system: Linux-5.0.5-arch1-1-ARCH-x86_64-with-arch 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56 **Blender Version** Broken: version: 2.80 (sub 53), branch: blender2.7, commit date: 2019-04-02 19:53, hash: `a813e259d6` Worked: (optional) **Short description of error** A box selection that includes files AND ".." turns the button on the right side to "Parent Directory" and the default action for pressing ENTER becomes going to the parent directory. ".." should be clickable, but not selectable, and the default action should always be "open" or "import" (e.g.). **Exact steps for others to reproduce the error** 1. Go to "File" > "Open" 2. Press B to box select. Select a .blend file and ".." the parent directory. 3. Observe the Button to the right, that turns from "Open Blender File" to "Parent Directory" 4. Press the Button, or simply ENTER. Works for File > Import/Expert as well. Basically everywhere.

Added subscriber: @MichaelHermann

Added subscriber: @MichaelHermann

Added subscriber: @StephenSwaney

Added subscriber: @StephenSwaney

I would label this is a quirk rather than a bug.
If you select a file AND "..", you have selected two things with different, incompatible semantics
I'm willing to argue that going to the parent directory takes precedence.

Making ".." clickable but unselectable just adds another quirky corner case.

I would label this is a quirk rather than a bug. If you select a file AND "..", you have selected two things with different, incompatible semantics I'm willing to argue that going to the parent directory takes precedence. Making ".." clickable but unselectable just adds another quirky corner case.

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

I wonder if we should remove the ‘..’ button, given that we also have a way to jump to the parent directory using a more standard button. Modern GUIs (read: since the 80s) don’t use ‘..’ to go to parent directories.

I wonder if we should remove the ‘..’ button, given that we also have a way to jump to the parent directory using a more standard button. Modern GUIs (read: since the 80s) don’t use ‘..’ to go to parent directories.

@StephenSwaney :

I'm willing to argue that going to the parent directory takes precedence.

When I box select e.g. 5 materials and accidentally ".." the I would definitely like to append the materials, rather than go to parent dir.

@WilliamReynish
My suggestion would be to keep the ".." button. It's good for keyboard-only navigation and also much easier/faster to reach with the mouse than smaller button in the top left.
I think this could be solved by either ignoring ".." when included in a selection of many items, or by auto-removing ".." from a selection of many items.
Or it could be unselectable by box selection in the first place. Why would you ever box select ".." ?! ;)

@StephenSwaney : > I'm willing to argue that going to the parent directory takes precedence. When I box select e.g. 5 materials and accidentally ".." the I would definitely like to append the materials, rather than go to parent dir. @WilliamReynish My suggestion would be to keep the ".." button. It's good for keyboard-only navigation and also much easier/faster to reach with the mouse than smaller button in the top left. I think this could be solved by either ignoring ".." when included in a selection of many items, or by auto-removing ".." from a selection of many items. Or it could be unselectable by box selection in the first place. Why would you ever box select ".." ?! ;)

Well, you can still have keyboard shortcuts to go to the parent folder, even if we don't have '..' inside the list of files.

Well, you can still have keyboard shortcuts to go to the parent folder, even if we don't have '..' inside the list of files.

I bet many are using ".." a lot to click on it as well. I (personally) would really like to keep it.

I bet many are using ".." a lot to click on it as well. I (personally) would **really** like to keep it.

I bet many are using ".." a lot to click on it as well. I (personally) would really like to keep it.

Me, too. I believe the ".." parent directory convention has been in use since Mr. Babbage's original computer back in the 19th century.

> I bet many are using ".." a lot to click on it as well. I (personally) would really like to keep it. Me, too. I believe the ".." parent directory convention has been in use since Mr. Babbage's original computer back in the 19th century.
Member

Added subscriber: @LazyDodo

Added subscriber: @LazyDodo
Member

I also say we keep the ".." but if it's selected with other files we just pretend it was never selected?

I also say we keep the ".." but if it's selected with other files we just pretend it was never selected?

Afaik, both file browsers and open/save dialogs don't use a '..' any more, on both Mac, Linux and Windows, which are the main platforms we support and integrate with.

Afaik, both file browsers and open/save dialogs don't use a '..' any more, on both Mac, Linux and Windows, which are the main platforms we support and integrate with.

I also say we keep the ".." but if it's selected with other files we just pretend it was never selected?

Yeah, what he said.

> I also say we keep the ".." but if it's selected with other files we just pretend it was never selected? Yeah, what he said.
Member

Yeah sure they don't have it anymore, on the other hand you can easily navigate to any part including the parent folder of the path by clicking on it.

Yeah sure they don't have it anymore, on the other hand you can easily navigate to any part including the parent folder of the path by clicking on it.

In #63263#654844, @LazyDodo wrote:
[...] other hand you can easily navigate to any part including the parent folder of the path by clicking on it.

True. That's what I use most of the time. And I find the buttons for back, forward and up are somewhat harder to reach. MAYBE that would be better if the row of buttons would be left aligned with the file list (above the path). I.e. have flexible space between the "view" menu and the back button.

> In #63263#654844, @LazyDodo wrote: > [...] other hand you can easily navigate to any part including the parent folder of the path by clicking on it. True. That's what I use most of the time. And I find the buttons for back, forward and up are somewhat harder to reach. MAYBE that would be better if the row of buttons would be left aligned with the file list (above the path). I.e. have flexible space between the "view" menu and the back button.

Yes, the File Browser could have a layout more like this:

{F6886125, size=full}

image.png

Which would bring the 'Up' button closer to the list of files and folders.

Yes, the File Browser could have a layout more like this: {[F6886125](https://archive.blender.org/developer/F6886125/image.png), size=full} ![image.png](https://archive.blender.org/developer/F6886128/image.png) Which would bring the 'Up' button closer to the list of files and folders.
Member

I don't mind the windows way of doing things actually, they did away with the up button all together

by default the path bar is a bunch of buttons

image.png

and when it gets the focus, it turns into a text field you can edit

image.png

I don't mind the windows way of doing things actually, they did away with the up button all together by default the path bar is a bunch of buttons ![image.png](https://archive.blender.org/developer/F6911806/image.png) and when it gets the focus, it turns into a text field you can edit ![image.png](https://archive.blender.org/developer/F6911812/image.png)

Looks pretty nice, @WilliamReynish ! However, I'd prefer the filename and path both at the top. As well as the buttons. On large and high-res screens this is very far apart. Even with the current layout, the "Open" or "Cancel" etc. buttons are already far to the right.

Looks pretty nice, @WilliamReynish ! However, I'd prefer the filename and path both at the top. As well as the buttons. On large and high-res screens this is very far apart. Even with the current layout, the "Open" or "Cancel" etc. buttons are already far to the right.

@LazyDodo Yes it would be nice with a more inteligent breadcrumb system like that, if that's possible to do in Blender.

@LazyDodo Yes it would be nice with a more inteligent breadcrumb system like that, if that's possible to do in Blender.
Member

guess suggesting using the OS dialog is heresy?

guess suggesting using the OS dialog is heresy?

@MichaelHermann

That is how it is on all the platforms we support:

Windows
LoadSaveFam.gif

Linux
ZhBdRij.png

Mac
Screenshot 2019-04-04 at 18.46.16.png

@MichaelHermann That is how it is on all the platforms we support: Windows ![LoadSaveFam.gif](https://archive.blender.org/developer/F6912116/LoadSaveFam.gif) Linux ![ZhBdRij.png](https://archive.blender.org/developer/F6912035/ZhBdRij.png) Mac ![Screenshot 2019-04-04 at 18.46.16.png](https://archive.blender.org/developer/F6912051/Screenshot_2019-04-04_at_18.46.16.png)
Member

That's an XP screenshot, that's not what it looks like now days, and definitely not a supported os, here's a more recent win7 one

image.png

That's an XP screenshot, that's not what it looks like now days, and definitely not a supported os, here's a more recent win7 one ![image.png](https://archive.blender.org/developer/F6912061/image.png)

@LazyDodo I don't think it's heresy, but we probably won't throw out the custom file browser.

It's nice to be able to keep as an editor for scenarios where you want to drag files continuously into Blender:

Screenshot 2019-04-04 at 18.51.07.png

And will most likely be the basis of the asset browser.

@LazyDodo I don't think it's heresy, but we probably won't throw out the custom file browser. It's nice to be able to keep as an editor for scenarios where you want to drag files continuously into Blender: ![Screenshot 2019-04-04 at 18.51.07.png](https://archive.blender.org/developer/F6912065/Screenshot_2019-04-04_at_18.51.07.png) And will most likely be the basis of the asset browser.
Member

I'd like to retract the idea to use the OS dialog then, makes very little sense to maintain two codepaths. time better spend improving the one we have :)

I'd like to retract the idea to use the OS dialog then, makes very little sense to maintain two codepaths. time better spend improving the one we have :)
Member

Added subscriber: @Harley

Added subscriber: @Harley
Member

@LazyDodo: they did away with the up button all together

No, the current version has an up button...

OpenDialog.png

> @LazyDodo: they did away with the up button all together No, the current version has an up button... ![OpenDialog.png](https://archive.blender.org/developer/F6912139/OpenDialog.png)
Member

I stand corrected, nice touch by re-creating my insane directory structure :)

I stand corrected, nice touch by re-creating my insane directory structure :)

Added subscriber: @TheRedWaxPolice

Added subscriber: @TheRedWaxPolice

In #63263#654870, @LazyDodo wrote:
I'd like to retract the idea to use the OS dialog then, makes very little sense to maintain two codepaths. time better spend improving the one we have :)

Is there a way/option to make the file browser open in a floating window, instead of covering the entire app? I find this behavior very annoying...

> In #63263#654870, @LazyDodo wrote: > I'd like to retract the idea to use the OS dialog then, makes very little sense to maintain two codepaths. time better spend improving the one we have :) Is there a way/option to make the file browser open in a floating window, instead of covering the entire app? I find this behavior very annoying...

@TheRedWaxPolice not currently but I think there could be. We could merge it with the option to render in a new window and make it a general preference instead, to apply to all kinds of temporary window states. Even the Preferences itself, which by default opens in a new window.

@TheRedWaxPolice not currently but I think there could be. We could merge it with the option to render in a new window and make it a general preference instead, to apply to all kinds of temporary window states. Even the Preferences itself, which by default opens in a new window.
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Discussion about the general file browser design should go into #62971. A colleague and I are actually working on this so expect news soon.
I'd vote for removing the '..' entry. For some users it might be confusing, and there is a button and a shortcut for it ({nav P}). With the button moved close to the file path, as planned, I think that will become more discoverable.

Note on using the OS file browser: Another issue with that would be browsing inside .blend files for append/link. We'd somehow have to load our custom items into the OS file browser. Not sure if that's possible on any platform, not to speak about a cross platform solution.

Discussion about the general file browser design should go into #62971. A colleague and I are actually working on this so expect news soon. I'd vote for removing the '..' entry. For some users it might be confusing, and there is a button and a shortcut for it ({nav P}). With the button moved close to the file path, as planned, I think that will become more discoverable. Note on using the OS file browser: Another issue with that would be browsing inside .blend files for append/link. We'd somehow have to load our custom items into the OS file browser. Not sure if that's possible on any platform, not to speak about a cross platform solution.

@WilliamReynish Sounds good... ?

@WilliamReynish Sounds good... ?

Added subscriber: @filibis

Added subscriber: @filibis

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Emir Sinan Gürlek self-assigned this 2020-01-11 03:52:48 +01:00

I believe this is no longer an issue as the UI has been updated. So I'm closing this report. Reopen if necessary.

I believe this is no longer an issue as the UI has been updated. So I'm closing this report. Reopen if necessary.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
8 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#63263
No description provided.