Gregor Adams

> Hi, > > Do you have a `use client` directive in the `page.tsx` file you're loading the studio? We are using the pages directory (no app router) Everything was...

@stipsan for the sake of complete testing I added a second reproduction where I used the app-router: https://github.com/pixelass/sanity-check-2 The process was as follows: 1. Go to terminal 2. enter `npx...

I needed something similar. 1. elements need to be draggable 2. elements need to be resizable in width 3. elements need to work in scaled context (i.e. `transform: scale(0.5)` on...

@CodyBontecou Sure, I need to extract it first though. Right now it's still entangled with business logic. But I'll post a sandbox when I cleaned my room 😉

Pretty mauch hardcoded into a custom component using joy-ui (MUI successor) I'm not sure if or how much this helps. We have 2 custom hooks for keyboard and mouse/touch/pointer handling....

looks like you're missing touch and keyboard listeners, but nice start. :)

@diegonogaretti pretty much hardcoded using Jotai for global state. (BTW we use Joy UI) This should be made into a reusable component as it currently only allows a single instance....

The same counts for the keyboardhandlers: Very hardcoded. It aims to mimic dnd-kit's sensor behavior ```tsx import { useAtom } from "jotai"; import type { KeyboardEvent as ReactKeyboardEvent, MutableRefObject }...

@KuzonFyre My implementation was a quick MVP which only requires resizing on the x axis. Please don't see my code as a reusable or recommended approach. My main focus was...

> So should the recommended approach be to use re-resizable? I chose to not use it because of its missing a11y support (no-keyboard interaction). Besides that it it seems to...