Scalable GUI
unfa opened this issue · 3 comments
unfa commented
The current graphical user interface for Sequencer64 has the same problem that the Seq24 GUI had - it doesn't scale well.
Are there any plans to make the UI utilize a all the pixels the users can throw at it?
I guess in some live situations this could be very handy (to see the UI clearly in bad lighting, smoke, screen not very close to you etc.).
unfa commented
Oh. I've just built and run the qseq64 version - it's scalable and looks amazing!
Why isn't this the default interface?!
ahlstromcj commented
The GtkMM GUI can be scaled at startup time using --option scale=x.y
Check out the man page on it.
…-------- unfa 16:58 Mon 25 Nov --------
The current graphical user interface for Sequencer64 has the same problem
that the Seq24 GUI had - it doesn't scale well.
Are there any plans to make the UI utilize a all the pixels the users can
throw at it?
I guess in some live situations this could be very handy (to see the UI
clearly in bad lighting, smoke, screen not very close to you etc.).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [1]view it on GitHub, or [2]unsubscribe.
References
Visible links
1. #186?email_source=notifications&email_token=AB45LKA5736K5MFXU5MP5DDQVRYERA5CNFSM4JRQ2L5KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H37DIEQ
2. https://github.com/notifications/unsubscribe-auth/AB45LKD2E3EQPXDJRVCBU5DQVRYERANCNFSM4JRQ2L5A
--
Good news from afar can bring you a welcome visitor.
ahlstromcj commented
The original Seq24 was Gtkmm so that's what I went with, and I added a
metric ton (way too many) features to it.
Then I wanted to do a port to Windows, and did not want to use that hoary
old Gtkmm 2.4. But Gtkmm 3 changed quite a few things, and I wasn't sure
that it would keep tracking with Windows. Then I noticed Kepler34, another
fork of Seq24, and it used a Qt GUI, so I used that as a base and went with
Qt 5, as that seems to more reliably track with OSX, Linux, and Windows.
However, I did not port some of the more "esoteric" features, and so that
GUI lags behind. I think it is also more CPU-intensive.
I am in the middle of refactoring Sequencer64 into the much leaner and more
modern (C++-wise) Seq66. The project works pretty well, though I am still
slogging through issues, using the "optimizing" branch. It uses only the Qt
GUI and my rtmidi library fork, plus my portmidi library fork to support
Windows and OSX (I have no way to test the latter). The configuration files
are also more sophisticated, though somewhat compatible with the old stuff.
…-------- unfa 17:10 Mon 25 Nov --------
Oh. I've just built and run the qseq64 version - it's scalable and looks
amazing!
Why isn't this the default interface?!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [1]view it on GitHub, or [2]unsubscribe.
References
Visible links
1. #186?email_source=notifications&email_token=AB45LKAQIUY3NYP5Q74KCT3QVRZQ3A5CNFSM4JRQ2L5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFELITQ#issuecomment-558412878
2. https://github.com/notifications/unsubscribe-auth/AB45LKAGUWOJDEPOXCGZJELQVRZQ3ANCNFSM4JRQ2L5A
--
Q: How much does it cost to ride the Unibus?
A: 2 bits.