See inspector without a mouse

[jannis-baum]

The inspector is great to keep us from using a mouse... but we need a mouse to see it??🙈 Maybe you could show it for the currently selected target while command or something is held down

[godbout]

the irony.

i liked the idea that you have to use the mouse once so that you don't use it afterwards. so that reminds you that you have to be grateful for Wooshy 😂️😂️😂️

but yeah. need something better.

[jannis-baum]

Hahahah I like the idea😁

I only have a super old Apple mouse whose batteries ran out a few weeks ago and I refuse to buy new ones😂 So now it's 100% Wooshy with no compromises because using a mouse means I have to grab and open my laptop

[godbout]

what about pressing a key combination? i'm thinking something like command ? to toggle The Inspector on and off. i like the idea of just pressing a key modifier to show The Inspector while pressing but that requires another way to handle keyboard events ☹️

[jannis-baum]

Yes that works as well!

[godbout]

still in the plans to allow people to set their own custom mappings tho.

also have you seen this for Wooshy: https://github.com/godbout/Wooshy.docs/issues any thoughts? i'm curious 😁️

[jannis-baum]

also have you seen this for Wooshy: https://github.com/godbout/Wooshy.docs/issues any thoughts? i'm curious 😁️

Which issue exactly?🙈

[godbout]

🤦‍♂️️ that one 🤣️ : https://github.com/godbout/Wooshy.docs/issues/151

[godbout]

also i'm starting experimenting with that one: https://github.com/godbout/Scrolla.docs/issues/16

if you have anything to add and/or new, i'll be glad to read!

[roelvangils]

also have you seen this for Wooshy any thoughts? i'm curious 😁️

Oh, I think that's a very nice idea. The person who came up with it is a genius!

[godbout]

Oh, I think that's a very nice idea. The person who came up with it is a genius!

that guy is not even a subscriber 🤣️🤣️🤣️

[roelvangils]

Really? I thought my monthly subscription was ending on the 27th of August 😁 After that, I'll pay for one year ahead. Yes, I'm looking forward to it! Take my money, mister!

[godbout]

Really? I thought my monthly subscription was ending on the 27th of August 😁 After that, I'll pay for one year ahead. Yes, I'm looking forward to it! Take my money, mister!

as far as Paddle is concerned you have canceled your subscription so even if you still have access to it for now you are now part of the bad guys. but of course they don't know Roel like i do hehehehehehehehehe ❤️🤣️

[roelvangils]

Yeah, look at us! ❤️

[godbout]

@jannis-baum working on this now. trying different workflows. once The Inspector 🕵️‍♂️️ shows up, what would you like to happen when/if you move Target:

1. The Inspector stays on the Target that you call him on
2. The Inspector disappears
3. The Inspector follows you to the new Target

see:

https://github.com/user-attachments/assets/38072a7d-1506-4489-a56f-399b1c46845d

i'm sure there's gonna be more questions later, but that's the first batch.

[jannis-baum]

I would say either 2. or 3. because 1. looks a bit like a it's bug and the inspector will never disappear again🙈

Between those two it's a bit hard to decide but I think I'd go for 3. because that not only serves the purpose of finding the name for one target but also allows you to "explore" more easily

[godbout]

https://github.com/user-attachments/assets/1e41b1ee-aace-4670-bfce-3c3ddd4802a4

hehe

[godbout]

i had another question then but now i forgot

[godbout]

oh yeah. does it make sense to keep The Inspector for the mouse then? less code is better code.

[godbout]

(also in some other news, working hard on the Scrolla and Wooshy custom key mapping. still far from the end solution but been spending weeks on that and making good progress! (means made a thousand discoveries and choices that get me closer to a proper solution))

[jannis-baum]

oh yeah. does it make sense to keep The Inspector for the mouse then? less code is better code.

Hm. How does the whole thing work right now, as in how do you trigger the inspector to show up with the keyboard?

I would actually probably argue keeping the mouse way as well still makes sense. Because people already know that and it's also intuitive (as long as you don't think about it too hard lol)

[godbout]

Hm. How does the whole thing work right now, as in how do you trigger the inspector to show up with the keyboard?

you mean code-wise? it's a total new thing. it's implemented in my Wooshy Engine while the mouse thing is implemented in an event tap. in the Wooshy Engine it's really clean while in the event tap unfortunately to get things smooth checking which UI Element is under the cursor is quite hardcore in terms of CPU cycles lol

if you're asking about the end user tho, command h or command i or shift command / hehe.

I would actually probably argue keeping the mouse way as well still makes sense. Because people already know that and it's also intuitive (as long as you don't think about it too hard lol)

yeah. hasn't killed any Mac yet anyways.

[jannis-baum]

Oki yeah makes sense. I think from a pure UX perspective I'd leave the mouse option but if it was my code I'd probably favor the clean code over the UX and get rid of it haha. Probably fine if you write it in the top of the release notes