| Age | Commit message (Collapse) | Author |
|---|
|
Adding new french translation
|
|
|
|
Bump electron from 22.3.24 to 22.3.25
|
|
|
|
Bumps [electron](https://github.com/electron/electron) from 22.3.24 to 22.3.25.
- [Release notes](https://github.com/electron/electron/releases)
- [Changelog](https://github.com/electron/electron/blob/main/docs/breaking-changes.md)
- [Commits](https://github.com/electron/electron/compare/v22.3.24...v22.3.25)
---
updated-dependencies:
- dependency-name: electron
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
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.
|
|
|
|
Bump electron from 22.3.21 to 22.3.24
|
|
Bumps [electron](https://github.com/electron/electron) from 22.3.21 to 22.3.24.
- [Release notes](https://github.com/electron/electron/releases)
- [Changelog](https://github.com/electron/electron/blob/main/docs/breaking-changes.md)
- [Commits](https://github.com/electron/electron/compare/v22.3.21...v22.3.24)
---
updated-dependencies:
- dependency-name: electron
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
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.
|
|
|
|
We now show an alert if the gamepath is detected to be missing
read/write perms, both when selecting the gamepath initially, when it
gets auto detected, but also after it's selected, passively.
|
|
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.
|
|
|
|
|
|
This is quite counter intuitive, as, if it's invalid, how do we
re-validate it, if we can't even save it again.
This existed here because the idea was for the re-validation to occur
somewhere else, and to make sure incorrectly formatted data wasn't being
given to this function. Now the function simply resets the config, a
restart may be required to add missing settings, in case the parsed
`conf` doesn't have all keys.
|
|
|
|
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)
|
|
|
|
Bump electron from 22.0.0 to 22.3.21
|
|
Bumps [electron](https://github.com/electron/electron) from 22.0.0 to 22.3.21.
- [Release notes](https://github.com/electron/electron/releases)
- [Changelog](https://github.com/electron/electron/blob/main/docs/breaking-changes.md)
- [Commits](https://github.com/electron/electron/compare/v22.0.0...v22.3.21)
---
updated-dependencies:
- dependency-name: electron
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
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.
|
|
Oopsie woopsie, my badddd, so sowwieeee, i wwwont doww it agaainnn!
|
|
|
|
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.
|
|
|
|
|
|
More changes may come down the line, but this is more or less complete,
I think?? You never know..
|
|
This generally is fine, as the folder is created on startup... IF
Northstar is installed! And so, if you start Viper for the first time or
Viper as only just extracted/created the R2Northstar folder, then the
folder wont exist, but it'll simply assume as such.
Now we actually handle this correctly.
|
|
|
|
|
|
This shouldn't have any adverse effects on anything? With very minimal
testing, everything seems completely fine, but I'll conduct a more
thorough testing to ensure nothing broke with this.
|
|
|
|
Now they simply have the red color instead.
|
|
|
|
|
|
This messed with how Northstar searches for packages, as it doesn't
conform to it's standard.
|
|
|
|
|
