Age | Commit message (Collapse) | Author |
|
Fixes michzimny/aktywator#43
|
|
|
|
|
|
|
|
* initializing BWS settings with randomized PIN
* checking PIN against predictable PINs (with explicit warning on settings save)
* generating randomized PIN easily
|
|
|
|
uploaded to sections
Fixes #42
|
|
|
|
|
|
to Bws()
|
|
Fixes #24
|
|
|
|
Fixes #3
|
|
|
|
|
|
|
|
|
|
Fixes #2
|
|
|
|
|
|
|
|
|
|
to disabled option, too.
|
|
Pary did not generate it)
|
|
|
|
|
|
|
|
|
|
|
|
flood in case wrong tournament is selected
|
|
|
|
list items
|
|
|
|
|
|
configurable
|
|
Fixes #15
|
|
Conflicts:
Aktywator.txt
Aktywator/MainForm.Designer.cs
Aktywator/MainForm.cs
|
|
|
|
integer type used in BWS)
|
|
|
|
|
|
|
|
properly if user chose not to continue syncing on first warning.
Also, the same choice (Continue? Yes/No) is offered on any other MySQL error
|
|
switching warning to Continue? Yes/No
|
|
|
|
|
|
operations
|
|
|
|
to previously hard-coded value
|
|
|