-
Notifications
You must be signed in to change notification settings - Fork 30.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drag and Drop for Global Awareness #92299
Conversation
margin-bottom: -3px; | ||
} | ||
|
||
/* .monaco-workbench .activitybar > .content :not(.monaco-menu) > .monaco-action-bar .action-item.insertAfter { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove commented code
opacity: 0; | ||
top: 0; | ||
pointer-events: none; | ||
/* z-index: 1; */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove commented code
|
||
CompositeDragAndDropObserver.INSTANCE.registerTarget(this.element, { | ||
onDragStart: e => { | ||
// this.element.style.outline = `1px solid`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove commented code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did a brief look and overall the code structure makes sense to me.
Drafting out what it should look like and testing its application
I think the observer should support registering participants (elements that can be dragged and register a set of callbacks) and listeners (just a set of callbacks for listening to global drag start and end).
Participants may need to listen to both their drag start event and others', should they be separate callbacks or should the participant handle checking?
We can also probably group the view id and type logic into the observer so it is responsible for populating and unpopulating the LocalTransferData