This is a band-aid on an underlying problem: there is no save directory
to put blobs like images in before the user saves the game. The way
forward is probably to have an in-memory (no disk, Colab privacy (thats
kind of an oxymoron)) folder or something. I want to expand the data
storage functionality into an api in the future so devs can seamlessly
do something like:
Data.get_file_contents("image/blahblah.png")
and they won't have to actually worry about stuff like this
- make the button thingeys look more button-ey
- enter now saves the focused tag and focuses the placeholder tag
- reduced code duplication for primary vs secondary and normal vs
placeholder tags
- cleaned up ui a bit
- disallow setting empty password (user could press the hotkey by
mistake and be confused), giving the user a notification if they try
to.
- gives the login attempter a message if the password is incorrect, as
well as screaming in the logs
- obscures story name in page title
- adds callback support to `enabledOn` in context menu items
- adds `supported_gen_modes` variable for frontend to check if a gen
mode is supported
- adds `get_supported_gen_modes` to `InferenceModel` to get supported
gen modes
- takes advantage of cool enum features for less enum-handling code
I think this would be cool!
Ideas:
- disable/grey when model doesnt support stopping criteria
- shortcuts (maybe, this would def be a power user thing)
- option to generate until EOS token
- option to generate forever until user manually stops
- (not super related but pixels away) make retry while generation is
ongoing cancel generation and retry. same with undo.
5px was a bit excessive
TODO: studied the context menu in my browser for a bit and noticed that
if it was going to be too close to the bottom, the browser changes the
vertical direction the context menu goes. sounds neat!
woohooooo back to css
- fixes margins to look better
- moves contents of context menu items 1px down
- fixes context menus near edge wrapping their inner text (ew)