Moosems
Moosems
One idea is to, in compilation, take the code inside the libraries and compile them as mojo code (because eventually all normal python will be valid mojo) going layer by...
Maybe a big long line number PR?
Out of curiosity, can events be forwarded without using event_generate on the other widget?
I got that issue as well. I run `sudo apt-get install -y gcc g++ zlib1g-dev libtinfo-dev` to install the dependencies that it has
It's very static. You want me to make a simple program that uses `sv_ttk` and submit it?
So make it use every possible state?
Welp, time to sit down with the manual. (I will probably do this over the weekend as I have three programming obligations this week (friends program, DIP, Tklinenums, and chlorophyll))
> Preferably each widget type separated in its own notebook tab (entry-like input stuff in one tab, button-stuff in another, blablabla) If you made a special notebook widget as detailed...
It has a lot of issues on Mac that likely will never get fixed and I need to make a new widget to address them.