| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Far from done, but this pretty much splits everything inside
`src/app/main.js` into separate files.
|
|
|
|
|
|
Ew! Bad! No! Bad! Bad!
|
|
|
|
This time it's inside the GUI and not just random output.
|
|
This means if you dont have any internet, but there's a cached requests,
it'll use that, even if it was cached a very long time ago. This just
attempts to eliminate errors.
This can still be turned off for things where you dont want this to
happen, notably the masterserver status.
|
|
|
|
Due to this button (specifically the "button"/link below the "Launch"
button) serving multiple functions, it incorrectly gets disabled when
the game is running. Now its enabled!
How did I miss this? I assume it crept up after implementing the force
quit button, and not during, but maybe not, was I stupid? Mayhaps.
|
|
This isn't present in the current release and is a bug that crept up
with the upcoming release, however of course, it's been fixed now.
|
|
Scrollbar is globally different, the release notes and mods page now
look more alike, having adjusted some padding, added some backgrounds
and a few other things.
|
|
When checking for an update whilst the latest release is already cached,
it'll resolve near instantaneously, not even letting the user know what
action they just performed, now however, a check for updates will
visually take at least 500ms.
|
|
|
|
|
|
|
|
|
|
When closing a category and then re-opening the setting popup, the
categories shouldn't remain closed!
|
|
|
|
If you're not clicking inside the `#browser` popup, then the preview and
filter popups would stay open, until you do so, or something else causes
them to close.
This fixes that.
|
|
Its now been split into 2, requests.js and releases.js, the latter
simply gets relevant info from GitHub release pages. The prior however
gives simple functions for doing `GET` requests, and caching the result,
and then transparently it'll use that cache when you request it next
time. On top of this, some requests made by the renderer will now also
use this, and this in turn ends up making loading the mod browser much
faster. As instead of having to request the list of packages from
Thunderstore, we can simply load the result of an old request.
The current lifetime of the cache is 5 minutes, however this can also
easily be adjusted.
This also moves the cached requests away from
<cache_folder>/viper-requests.json, and over to
<cache_folder>/Viper/cached-requests.json
|
|
|
|
If the settings popup was opened or closed through other means than
clicking the settings button itself, "Save" button or "Discord"
button, then the cog wouldn't update/rotate accordingly.
|
|
|
|
This makes opening and closing popups a little bit easier, on top of it,
it also fixes a bug where you could open the settings popup on top of
the browser popup or other popups, and it'd hide the background blur,
but still show both popups.
|
|
|
|
Ideally this has no side effects, however, I've not actually tested if
the launching does properly use the launch arguments, due to not having
a Windows device on hand. This will be tested later...
We still attempt to load launch arguments from `ns_startup_args.txt` if
none is set in the settings. However, this may be removed in the future.
|
|
This takes a bit of code from #220 to implement percentage progress on
the download, then with the new pseudo element on the Launch button, we
can have a slight progress bar inside the button, along with
percentages, and it all works handy dandy.
This may not be finished, but it's definitely far there.
|
|
|
|
|
|
If the gamepath is lost or similar then it'll disable many buttons,
notably the install/launch buttons and other similar buttons, however
for obvious reasons we shouldn't be stopping the user from changing
their gamepath in this scenario. This is still useful when installing a
mod or updating NS, so it's just this scenario.
|
|
Very useful stuff!
|
|
This only occurred if there was one continous piece of text, that is, no
spaces in between the characters, this only happened in the detailed
error messages, but it's quite important to see the whole message!
|
|
|
|
The amount of times I've broken something with `backdrop-filter` is far
too many, but what can you expect.
|
|
|
|
I will likely add more buttons in the future, but for now this is most
of the ones a user could need to repair problems.
|
|
|
|
Most of these are from back when Viper was originally started, I also
removed a few keys as they were no longer in use, but were forgotten
about, most of these are from pre-v1.0.0 aka, the old smaller UI
|
|
The `lang()` function doesn't change whatsoever, as the lang files are
flattened and are therefore identical to the before this commit.
I also cleaned up the files, and all the lang files should now all look
far more similar in order.
|
|
|
|
From my testing this works without problems, but further testing will be
requested in #211
|
|
If the main process has changes to the settings, said settings will now
also be sent to the renderer, making them synchronized.
|
|
This would mean if the gamepath cant be found automatically you'll be
asked to set your gamepath every time Viper starts, instead of it
remembering it, and if it can find it automatically, then you'd never
have known this was a problem (hence why this was even a problem)
|
|
|
|
The mod browser before this pre-maturely thought it had loaded all the
available packages, when in fact, it'd barely started. Now this is
fixed, and you can scroll for quite some time before actually reaching
the real end of the package list.
|
|
This doesn't break the old way of detecting things, for various reasons,
but notably it'd cause more harm than good. As we still need to be able
to detect packages that haven't been converted into the new location.
|
|
|
|
|
