From 0b448f350984bf7a5f492ab4234ea3b88377680a Mon Sep 17 00:00:00 2001 From: KSP-TaxiService Date: Mon, 16 Apr 2018 21:56:13 +0800 Subject: [PATCH] Bump release version to 1.2.0 --- appveyor.yml | 8 ++--- .../Properties/AssemblyInfo.cs | 6 ++-- v1.1-points.txt | 30 ------------------- 3 files changed, 7 insertions(+), 37 deletions(-) delete mode 100644 v1.1-points.txt diff --git a/appveyor.yml b/appveyor.yml index 65eae40..b7b05c0 100644 --- a/appveyor.yml +++ b/appveyor.yml @@ -13,7 +13,7 @@ #---------------------------------# # version format (you need to bump it when changing version) - version: 1.1.3 + version: 1.2.0 # branches branches: @@ -64,7 +64,7 @@ - cmd: set GAMEDATA_FOLDER=%APPVEYOR_BUILD_FOLDER%\GameData - cmd: set ASSEMBLY_FOLDER=%GAMEDATA_FOLDER%\CommNetConstellation\Plugins # download required KSP DLLs - - cmd: curl -fsS -o%DOWNLOAD_FOLDER%\dlls.7z https://d237kiopfuf7h0.cloudfront.net/download/KSPDLL_1_3_1.zip + - cmd: curl -fsS -o%DOWNLOAD_FOLDER%\dlls.7z https://d237kiopfuf7h0.cloudfront.net/download/KSPDLL_1_4_2.zip # extract them - cmd: cd %DOWNLOAD_FOLDER% & dir - cmd: 7z.exe e -p%DLL_ARCH_PASS% -o%ASSEMBLY_FOLDER% %DOWNLOAD_FOLDER%\dlls.7z @@ -212,7 +212,7 @@ #---------------------------------# # version format (you need to bump it when changing version) - version: 1.1.3-{build}-{branch} + version: 1.2.0-{build}-{branch} # branches branches: @@ -263,7 +263,7 @@ - cmd: set GAMEDATA_FOLDER=%APPVEYOR_BUILD_FOLDER%\GameData - cmd: set ASSEMBLY_FOLDER=%GAMEDATA_FOLDER%\CommNetConstellation\Plugins # download required KSP DLLs - - cmd: curl -fsS -o%DOWNLOAD_FOLDER%\dlls.7z https://d237kiopfuf7h0.cloudfront.net/download/KSPDLL_1_3_1.zip + - cmd: curl -fsS -o%DOWNLOAD_FOLDER%\dlls.7z https://d237kiopfuf7h0.cloudfront.net/download/KSPDLL_1_4_2.zip # extract them - cmd: cd %DOWNLOAD_FOLDER% & dir - cmd: 7z.exe e -p%DLL_ARCH_PASS% -o%ASSEMBLY_FOLDER% %DOWNLOAD_FOLDER%\dlls.7z diff --git a/src/CommNetConstellation/Properties/AssemblyInfo.cs b/src/CommNetConstellation/Properties/AssemblyInfo.cs index 994d7ee..92ca2d4 100644 --- a/src/CommNetConstellation/Properties/AssemblyInfo.cs +++ b/src/CommNetConstellation/Properties/AssemblyInfo.cs @@ -36,10 +36,10 @@ // Don't include the patch revision in the AssemblyVersion - as this will break any dependent // DLLs any time it changes. Breaking on a minor revision is probably acceptable - it's // unlikely that there wouldn't be other breaking changes on a minor version change. -[assembly: AssemblyVersion("1.1")] -[assembly: AssemblyFileVersion("1.1.3")] +[assembly: AssemblyVersion("1.2")] +[assembly: AssemblyFileVersion("1.2.0")] // Use KSPAssembly to allow other DLLs to make this DLL a dependency in a // non-hacky way in KSP. Format is (AssemblyProduct, major, minor), and it // does not appear to have a hard requirement to match the assembly version. -[assembly: KSPAssembly("CommNetConstellation", 1, 1)] +[assembly: KSPAssembly("CommNetConstellation", 1, 2)] diff --git a/v1.1-points.txt b/v1.1-points.txt deleted file mode 100644 index 0ef0845..0000000 --- a/v1.1-points.txt +++ /dev/null @@ -1,30 +0,0 @@ - -As you may be aware of, there is certainly a lot of room for improvements over the initial single-frequency interaction (it is too simple as you pointed out). I propose these major changes below. - -1) Antennas of a host vessel - -Assignment of one frequency to each antenna -A custom name to distinguish from other identical antennas on the host vessel -Can only key in one of the existing frequencies with a few exceptions (when an existing constellation is deleted, only update vessel's frequency list) -Stock Comm Power of the antenna will be preserved -By default, the frequency will be the public one (0) -The stock antenna combination will be preserved though it is applicable to the same frequency. - -2) Probe core/manned pod parts of a host vessel - -Each part stores a list of frequencies persistently. In the scenario of a multi-staging vessel (mothership and landers), newly-staged vessels rebuild their lists from their own antennas -By default, the list of unique frequencies is constructed from all the antennas -A button in the Part-Action menu to bring up an user interface to manage the said list - -3) Management interface of a host vessel - -The obsolete "Talk to members only" option will be removed since desired frequencies can be explicitly assigned to the vessel -Display a stored list of frequencies (Active Frequency List) -Optional functions on the list -- Activate/de-activate some antenna-frequencies in the list (the whitelist/blacklist) -- ??? - -4) Connection between two nodes based on their Active Frequency Lists - -Since the antennas of a vessel can be configured independently, the connection will be the strongest link of the antennas' matching frequency, instead of juggling multiple matching frequencies. -For example, Vessel A has Antenna X of Freq 1 and Comm Power 50k and Antenna Y of Freq 2 and Comm Power 10k. Vessel B has Antenna Z of Freq 1 and Comm Power 20k and Antenna Y of Freq 2 and Comm Power 30k. Then, the connection between Vessels A and B is the link of Antenna X and Z since this link is stronger than the link of Antenna Y's. \ No newline at end of file