BS-JD-203 - Drag/drop material and texture application #18

New Issue

Rbanh · 2026-06-06T01:47:25-04:00

Rbanh commented

2026-06-06 01:47:25 -04:00

Summary

Make texture/material drag/drop work consistently for static mesh actors, primitive actors, and brush faces.

Why

The material workflow should use one predictable drop path across current meshes and future brush geometry.

Implementation notes

Normalize drop target detection for renderer slots, primitive actors, and brush faces.
Preview material/texture application before commit.
Route mutations through operator/history path.
Preserve inherited source defaults when explicit overrides are cleared.

Acceptance criteria

Dropping material or texture onto supported targets previews result.
Static mesh, primitive, and brush targets use consistent commit/cancel behavior.
Undo restores previous material state.
Unsupported targets explain why drop is unavailable.

Tests/docs

Material application tests across target kinds. Update README controls and docs/editor material workflow.

## Summary Make texture/material drag/drop work consistently for static mesh actors, primitive actors, and brush faces. ## Why The material workflow should use one predictable drop path across current meshes and future brush geometry. ## Implementation notes - Normalize drop target detection for renderer slots, primitive actors, and brush faces. - Preview material/texture application before commit. - Route mutations through operator/history path. - Preserve inherited source defaults when explicit overrides are cleared. ## Acceptance criteria - [ ] Dropping material or texture onto supported targets previews result. - [ ] Static mesh, primitive, and brush targets use consistent commit/cancel behavior. - [ ] Undo restores previous material state. - [ ] Unsupported targets explain why drop is unavailable. ## Tests/docs Material application tests across target kinds. Update README controls and docs/editor material workflow.

Rbanh added this to the M2 - Materials and asset pipeline milestone 2026-06-06 01:47:25 -04:00

Rbanh added the

labels 2026-06-06 01:47:25 -04:00

Rbanh referenced this issue

2026-06-06 01:49:27 -04:00

BS-JD-ROADMAP - Jackdaw-inspired editor production roadmap #1

Rbanh commented

2026-06-06 05:06:34 -04:00

Progress landed in cc6acb1 (Complete M0 editor asset workflow).

Completed M0-relevant portion:

Texture/material apply actions are routed through asset operators.
Actor Authoring Material texture refs are now Asset Browser-backed picker/drop fields with browse, locate, clear, hover/drop highlighting, compact rows, and thumbnail previews.
Full-row hit testing fixed so drag hover is stable across the slot.
JPEG loading enabled so .jpg textures can be assigned and previewed/loaded.

Closing this ticket for the M0 drag/drop material+texture application workflow. Follow-up work for comprehensive material browsing/cataloging remains in BS-JD-201, and PBR texture-set auto-detection remains in BS-JD-202.

Progress landed in `cc6acb1` (`Complete M0 editor asset workflow`). Completed M0-relevant portion: - Texture/material apply actions are routed through asset operators. - Actor `Authoring Material` texture refs are now Asset Browser-backed picker/drop fields with browse, locate, clear, hover/drop highlighting, compact rows, and thumbnail previews. - Full-row hit testing fixed so drag hover is stable across the slot. - JPEG loading enabled so `.jpg` textures can be assigned and previewed/loaded. Closing this ticket for the M0 drag/drop material+texture application workflow. Follow-up work for comprehensive material browsing/cataloging remains in BS-JD-201, and PBR texture-set auto-detection remains in BS-JD-202.

Rbanh closed this issue

2026-06-06 05:06:35 -04:00

Rbanh reopened this issue

2026-06-06 05:06:53 -04:00

Rbanh commented

2026-06-06 05:06:53 -04:00

Correction: reopening this because BS-JD-203 is assigned to M2 and still includes broader target-kind/preview acceptance criteria (primitive/brush faces and richer commit/cancel coverage) beyond the M0 work.

cc6acb1 should be treated as M0 progress for actor material/texture picker/drop and operator routing only. Remaining M2 scope stays open.

Correction: reopening this because BS-JD-203 is assigned to M2 and still includes broader target-kind/preview acceptance criteria (primitive/brush faces and richer commit/cancel coverage) beyond the M0 work. `cc6acb1` should be treated as M0 progress for actor material/texture picker/drop and operator routing only. Remaining M2 scope stays open.

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 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: Falling-Metal-Interactive/Blacksite#18