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

Removing extra tiles? #28

Open
rpodcast opened this issue May 12, 2017 · 7 comments
Open

Removing extra tiles? #28

rpodcast opened this issue May 12, 2017 · 7 comments

Comments

@rpodcast
Copy link

Just tried out the newest version and loving the new features! For my podcast I likely won't have more than 6 audio files I would play in a given episode, so would it be possible to remove the extra tiles I don't plan on using for a particular tab?

@covarianttensor
Copy link
Collaborator

I'll see what I can do. But it's gonna be a while before I get to this. I'm currently working on a major feature (Open Sound Control).

@rpodcast
Copy link
Author

Definitely no rush and thanks to the new capability of changing colors of tiles I can at least make them stand out from the unused tiles.

@rikai
Copy link

rikai commented May 19, 2017

I would actually like the opposite, the current setup doesn't use all of the available keyboard keys and it would be nice if we could assign more

@covarianttensor
Copy link
Collaborator

I'm gonna have to find a way to combine all three features, productions modes, like mentioned in #38 , ability to remove tiles, and ability to use more per board. About how many tiles do you need on those boards @rikai ?

@rikai
Copy link

rikai commented May 22, 2017

I feel like the maximum should mirror the amount of available keys, maybe a 10x4 grid would work the best?

Or we could move away from the grid idea completely and just allow an arbitrary number per row and an arbitrary number of rows, with assignable hotkeys, that way people could decide how many they want, defaulting to something similar to the current setup on a fresh tab... But i imagine that'd require a significant rework of how the UI works, so maybe it could a more 'long term' goal, if it's deemed a good idea? It'd definitely be the most flexible solution.

@pcs3rd
Copy link

pcs3rd commented Mar 27, 2019

Poke?

@covarianttensor
Copy link
Collaborator

covarianttensor commented Apr 6, 2019

Poke?

Working on it, no ETA. Working on another project at the moment.

See this issue

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

4 participants