.appveyor.yml

@@ -2,7 +2,7 @@
 image: Visual Studio 2022
 environment:
     matrix:
-        - PYTHON: "C:\\Python313"
+        - PYTHON: "C:\\Python312"
 # Shamelessly taken from https://github.com/plicease/Dist-Zilla-PluginBundle-Author-Plicease/blob/master/.appveyor.yml
 # Thanks!
 install:

.github/workflows/macos-package.yml

@@ -7,7 +7,7 @@ on:
 
 jobs:
   build:
-    runs-on: macos-14
+    runs-on: macos-12
 
     steps:
     - uses: actions/checkout@v2

NEWS.asciidoc

@@ -1,11 +1,5 @@
 [[news]]
 === News
-* _11 January, 2025:_ There is a new stable release
-https://sourceforge.net/projects/pysolfc/files/PySolFC/PySolFC-3.2.0/[PySolFC
-v3.2.0]. New in this release:
-** New fullscreen mode, accessible by pressing F11.
-** Easy option to clear advanced search options.
-** Lots of bugfixes and enhancements.
 * _19 October, 2024:_ There is a new stable release
 https://sourceforge.net/projects/pysolfc/files/PySolFC/PySolFC-3.1.0/[PySolFC
 v3.1.0]. New in this release:

buildozer/aversion

@@ -9,7 +9,7 @@ else
 fi
 
 # current android version mumber.
-version="3.2.0"
+version="3.1.0"
 sversion=$(echo $version  | sed -E "s:(.*)\..*:\1:")
 tuple=$(echo $version | sed -E "s:(.*)\.(.*)\.(.*):(\1, \2, \3):")
 

buildozer/buildozer.run

@@ -7,14 +7,6 @@ export GRADLE_OPTS="-Xms1724m -Xmx5048m -Dorg.gradle.jvmargs='-Xms1724m -Xmx5048
 
 echo '### run buildozer'
 
-
-if [ "$1" == "test" ]
-then
-	echo '### ... release.test'
-  buildozer --profile test android release
-  exit 0
-fi
-
 if [ "$1" ]
 then
 	echo '### ... release'

buildozer/buildozer.spec

@@ -103,7 +103,7 @@ android.permissions = WRITE_EXTERNAL_STORAGE, MANAGE_EXTERNAL_STORAGE
 #android.features = android.hardware.usb.host
 
 # (int) Target Android API, should be as high as possible.
-android.api = 34
+android.api = 33
 
 # (int) Minimum API your APK / AAB will support.
 #android.minapi = 21
@@ -441,7 +441,3 @@ warn_on_root = 1
 #    Then, invoke the command line with the "demo" profile:
 #
 #buildozer --profile demo android debug
-
-[app@test]
-title = PySolFC.test
-package.name = pysolfc.test

buildozer/fdroid.init

@@ -6,7 +6,7 @@ then
   exit 1
 fi
 
-python3 -m venv FINIT
+virtualenv FINIT
 source FINIT/bin/activate
 
 pip3 install attrs
@@ -43,7 +43,7 @@ sed -r "s:#? ?source\.exclude_patterns =.*:source.exclude_patterns = README.*,AU
 sed -r "s:#? ?android\.skip_update =.*:android.skip_update = True:" -i buildozer.spec
 sed -r "s:#? ?android\.accept_sdk_license =.*:android.accept_sdk_license = False:" -i buildozer.spec
 sed -r "s:#? ?log_level =.*:log_level = 2:" -i buildozer.spec
-sed -r "s:#? ?warn_on_root =.*:warn_on_root = 0:" -i buildozer.spec
+
 
 echo '### end init'
 

buildozer/pubspec.json

@@ -11,8 +11,8 @@
       "type": "SINGLE",
       "filters": [],
       "attributes": [],
-      "versionCode": 102130200,
+      "versionCode": 102130100,
-      "versionName": "3.2.0",
+      "versionName": "3.1.0",
       "outputFile": "pysolfc-release.apk"
     }
   ],

contrib/customize_cardset.asciidoc

@@ -3,20 +3,6 @@ Cardset Customization Tutorial
 :Author: Eric Rausch
 :Email: <neelix570@gmail.com>
 
-Setting up a Cardset
---------------------
-The easiest way to create a cardset would be to copy an existing cardset folder of the same type in your cardsets directory.  All cardsets need a number of files to work.
-
-* An image for each card - these images should be the same format and the same size, as defined in the config.txt file (described below).  These files should be named something like 01s.png for the ace of spades.  The first two (or more) digits represent the rank, and the letter after represents the suit.  The suits are labeled hcds in French decks or decks that use French suits (i.e. Hex A or Tarock decks), and the suits are alphabetical for other decks.  The suit letter z is used for jokers or trumps.
-* A shade file - shade.png, for example.
-* At least one back image, as defined in the config.txt file below.
-* A config.txt file, the format described below.
-* A copyright file, containing copyright info.
-
-The following optional files may also be added, but are only used under certain circumstances.
-
-* Bottom images.  A number of images for the bottoms of stacks.  These are not used unless your PySol install does not support generating stack bottoms, or you enable them manually (currently only possible through editing the options.cfg file).  Which bottoms are used depend on the cardset type.  Each bottom has a version with a suffix of -n, indicating the negative bottom that gets used if the appropriate option is enabled.
-* Shadow images.  These will only be used if your PySol install does not support auto-generated shadows.
 
 config.txt template
 -------------------