File Browser's File Drop features often fails when dragging items to the main region of the browser (macOS) #101033

Closed
opened 2022-09-13 15:17:54 +02:00 by Juan Gómez · 10 comments

System Information
Mac Pro 2010 (x86)
macOS 10.14.6 Mojave:
Graphics card: Radeon RX 560 4GB

Blender Version
Broken: 3.3 LTS.
Worked: all previous ones.

File Browser's File Drop feature fails (more often than not) if a file or directory is dropped onto its main region. It works consistently well if dropped onto any other region of the browser.

Exact steps for others to reproduce the error

  1. Open any File Browser (say, the Open a Blender File one or any of the importing ones.
  2. Drag and drop some folder or file from the Finder onto the main region. What I find that happens is:
  • That it fails.
  • That it works sometimes if I hold the item for a few seconds (four or more) and then drop it.
  • That it works sometimes if I drag and drop it closest to the main region's top edge.

If I drag and drop some folder or file from the Finder onto any other region. It works every time.

**System Information** Mac Pro 2010 (x86) macOS 10.14.6 Mojave: Graphics card: Radeon RX 560 4GB **Blender Version** Broken: 3.3 LTS. Worked: all previous ones. File Browser's File Drop feature fails (more often than not) if a file or directory is dropped onto its main region. It works consistently well if dropped onto any other region of the browser. **Exact steps for others to reproduce the error** 1. Open any File Browser (say, the Open a Blender File one or any of the importing ones. 2. Drag and drop some folder or file from the Finder onto the main region. What I find that happens is: * That it fails. * That it works sometimes if I hold the item for a few seconds (four or more) and then drop it. * That it works sometimes if I drag and drop it closest to the main region's top edge. If I drag and drop some folder or file from the Finder onto **any other region**. It works every time.
Author

Added subscriber: @UseTheFarce

Added subscriber: @UseTheFarce
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

We are getting similar reports on MacOS, so it might be related. #100899
Can you try dragging and dropping an image into the node shading editor and see if you can replicate the issue in the aforementioned report?

We are getting similar reports on MacOS, so it might be related. #100899 Can you try dragging and dropping an image into the node shading editor and see if you can replicate the issue in the aforementioned report?
Author

Dragging and dropping images to the Shader Editor works perfectly in my case, no matter the image type.

(This is on an old x86 Mac Pro tower. I'll update the system information of my opening post to reflect that)

Dragging and dropping images to the Shader Editor works perfectly in my case, no matter the image type. (This is on an old x86 Mac Pro tower. I'll update the system information of my opening post to reflect that)

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

This looks like it's the same issue as #100899. Please check if Blender's file browser window position makes difference on where dead areas are - if I resize window to half of a screen, dropping does not work if window is on right side, but works if window is on left side of screen.

This looks like it's the same issue as #100899. Please check if Blender's file browser window position makes difference on where dead areas are - if I resize window to half of a screen, dropping does not work if window is on right side, but works if window is on left side of screen.
Author

I can confirm that behavior. Using the freeware utility Rectangle to precisely position the file browser in each half of the screen and other positions and sizes, I see the following:

Full height, half width window, set at the left half of screen: always works.
Full height, half width window, set at the right half of screen: doesn't work.

Full height, half width window, set at the middle third of screen: doesn't work.

Half height, full width window, set at the top half of screen: doesn't work.
Half height, full width window, set at the bottom half of screen: always works.

This one is curious:
Half height, full width window, set at the middle third of the screen's height (leaving empty space above and below): if I drop items onto it, the dead area happens to be below the screen's middle height (instead of above it, as could maybe be expected from it fully working when it is at the bottom half).

I hope this helps.

I can confirm that behavior. Using the freeware utility Rectangle to precisely position the file browser in each half of the screen and other positions and sizes, I see the following: Full height, half width window, set at the left half of screen: always works. Full height, half width window, set at the right half of screen: doesn't work. Full height, half width window, set at the middle third of screen: doesn't work. Half height, full width window, set at the top half of screen: doesn't work. Half height, full width window, set at the bottom half of screen: always works. This one is curious: Half height, full width window, set at the middle third of the screen's height (leaving empty space above and below): if I drop items onto it, the dead area happens to be below the screen's middle height (instead of above it, as could maybe be expected from it fully working when it is at the bottom half). I hope this helps.

Thanks for checking. Since this seems to be same issue, so will merge reports.

Thanks for checking. Since this seems to be same issue, so will merge reports.

Closed as duplicate of #100899

Closed as duplicate of #100899
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
No Assignees
3 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#101033
No description provided.