Skip to content
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

Add macOS Touch Bar Support #1905

Closed
Yona-Appletree opened this issue Jan 3, 2017 · 8 comments
Closed

Add macOS Touch Bar Support #1905

Yona-Appletree opened this issue Jan 3, 2017 · 8 comments

Comments

@Yona-Appletree
Copy link

Yona-Appletree commented Jan 3, 2017

I recently switched to a new Macbook Pro with Touch Bar, and it makes using OpenSCAD a bit of a pain. I would love to see the addition of basic Touch Bar support -- just Render, Refresh, Reset View would be awesome.

I may try and do the work myself, would folks be open to a pull request for that support?


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@kintel
Copy link
Member

kintel commented Jan 3, 2017

This sounds a bit like something which eventually should fit into Qt.
As that will likely take a while, a pull request is probably the way to go.
Admittedly, I haven't looked into what the touch bar really can do, but I would look into ways of making it work well with Qt, e.g. rendering Qt components into the touch bar and using the same action system as the rest of the OpenSCAD GUI.

@t-paul
Copy link
Member

t-paul commented Jan 3, 2017

Attaching external stuff to the actions should be easy. Some non-GUI based code is in the InputDriver branch. Maybe in combination with an action editor? That would be nice to have even without the TouchBar suppot :-).

@donbright
Copy link
Sponsor Member

donbright commented Jan 25, 2017

someone submitted qt bug report, maybe if enough mac users do the same and write to QT there will build a movement and some donations .

https://bugreports.qt.io/browse/QTBUG-56908

hopefully any patch will not impact linux/windows at all and not interfere with existing code.

input driver seems necessary long term because the future is Virtual Reality OpenSCAD where people rotate their creations using mindwaves or their feet or they talk to it, like saying "Alexa, rotate view horizontal 5 degrees per second. stop. zoom in. " Actually talk interface could be done now without the VR thing. but the point is future is not going to be clicking a mouse on a doodad on the screen.


for self reference... workaround maybe alt-d e alt-d r

but imo really what we need is to provide a good alternative to Function Keys because they are going extinct on personal computers.

every laptop system that i see, the Function Keys get smaller and more remote. On my machine you have to hit some tiny 'fn' button then you can hit the function key. Normally it is for volume control, brightness, etc.

so it is needed to pick new keyboard shortcuts for f5 and f6. it is a very tricky thing to get right.

it is necessary to pick some combo which wont conflict with a bunch of other stuff on the system. for example on ubuntu there is all sorts of weird stuff they use for their interface.

also it is necessary to keep in mind different human languages may have different shortcuts for menu items based on the letters in the words used for a menu item in that language.

it is also necessary to remember some people are used to editors like vi, vim, nano, wordstar, bank street writer, wordperfect, pages, google docs, even ms word, with various shortcuts they are used to using on different OSes and so you dont want to accidentally have f6 replaced by something they might accidentally hit out of habit (or that... you know... if you ever wanted to provide customizable editor keys like a lot of programs do).

@kintel
Copy link
Member

kintel commented Jan 25, 2017

I think I agree that a better solution would be to use non-function shortcuts for the actions which today use function keys, and let users assign their own additional shortcuts. The same probably goes for toolbar actions.

@deckar01
Copy link
Contributor

deckar01 commented Jul 20, 2020

I tested out https://github.com/KDAB/KDMacTouchBar. The existing icons scale poorly and there aren't any styling options yet, but the basic buttons and labels are functional.

Demo

openscad_touchbar_demo

I am working on cleaning this up and sharing it. I had to manually build and copy the KDMacTouchBar framework to the app contents, and I'm not sure how this is supposed to be done. Would it need to be a prerequisite installed in the system library? make installing it didn't put it in a place where OpenSCAD was looking at runtime.

@t-paul
Copy link
Member

t-paul commented Jul 20, 2020

The make install target is pretty much Linux only. The MacOS App Bundle is created via scripts/release-common.sh which in turn uses macdeployqt.

@deckar01
Copy link
Contributor

deckar01 commented Jul 21, 2020

Sorry for the confusion, I meant KDMacTouchBar's make install doesn't put it's framework in a place that OpenSCAD looks for frameworks. I though it was putting it in /Library/Frameworks, but it wasn't. OpenSCAD did find it when I moved it there.

I see the OBJECTIVE_SOURCES, but I'm not sure how I would setup an ObjectiveC framework build and get the output to target the app content's framework directory. All of the other frameworks seem to be setup as system prerequisites, so maybe that's how I should leave it for now.

@kintel
Copy link
Member

kintel commented Jan 2, 2022

I'll close this, as Apple has (finally) discontinued the touch bar, so I feel it's probably not worth spending resource chasing this any longer.

@kintel kintel closed this as completed Jan 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants