You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was hoping that each component could attempt to process, and if nothing handles the object type, then throw the Drag&Drop event to their parent. Each component would do this, with the final parent being MainWindow or App. This top level could handle or discard if nothing has processed it at this point.
I don't know how feasible it is, but something I'll look into.
That's what's supposed to happen, but unfortunately some controls swallow the event and don't let it bubble up to the window. I never got around to trying to fix it control bt control.
But ultimately even adding it on every component within AppSummaryPage either breaks the theming on the internal drag&drop mod sorting, or threw away the mod install event.
I recommend leaving this issue open if anyone else wants to take a crack at it and has more experience with drag&drop and WPF.
What
The current Drag & Drop install mod feature has very little area where you can drop a mod. Leading to some users thinking the feature is broken.
A user would intuitively try to drop the mod within the list of Mods in Configure Mods window.
Drag-N-Drop-Current.mp4
Proposal
The text was updated successfully, but these errors were encountered: