init

2025-08-18 09:22:24 +08:00
commit cef5623ab0
1333 changed files with 305844 additions and 0 deletions
@@ -0,0 +1,9 @@
+fileFormatVersion: 2
+guid: 6791580bb5da52c4f8ad8e62548b0792
+folderAsset: yes
+timeCreated: 1542050069
+licenseType: Store
+DefaultImporter:
+  userData: 
+  assetBundleName: 
+  assetBundleVariant: 
@@ -0,0 +1,8 @@
+fileFormatVersion: 2
+guid: 3887e9a653188c741bfbf85729a9ae28
+timeCreated: 1542741010
+licenseType: Store
+DefaultImporter:
+  userData: 
+  assetBundleName: 
+  assetBundleVariant: 
@@ -0,0 +1,38 @@
+File updated on 11.03.2020
+Check the latest version at https://forbiddenbyte.com/unityassetstore/optimizedscrollviewadapter/playmaker/README.txt
+
+
+Playmaker support only works with Unity 2017.1.0f3 and up + Playmaker 1.9.0 an up
+
+Instructions:
+
+1.   Back up your project!
+
+2.   Make sure the original Playmaker asset is imported/installed (it's not included, obviously. Here's their asset link: https://assetstore.unity.com/packages/tools/visual-scripting/playmaker-368)
+	 It should be AT LEAST version 1.9.0
+
+3.   (Optional, if you want to use XML) Import their DataMaker add-on (https://hutonggames.fogbugz.com/default.asp?W1133). It doesn't work on Windows Phone!
+
+4.   Extract the PlaymakerSupport.zip somewhere OUTSIDE the project. In some unity versions, the packages inside won't be double-clickable, so you need to import them through drag'n'drop or toolbar
+
+5.   This step should be done for OSA 4.3 and up, since the utilities and demos were separated in their own package. Import Utilities and then Demos packages (in this order) found under "/Extra"
+
+6.   Import the PMSupport-Unity2017-1-f3.unitypackage
+
+7.   For Unity 2017.3 and up, you'll probably get an error because OSA can't see the Playmaker code. This is normal.
+	 A. If you don't want to use ASMDEFs or just prefer a quicker set up, delete all *.asmdef files from OSA's folder.
+	 B. If you know how to set up ASMDEFs (https://docs.unity3d.com/2017.4/Documentation/Manual/ScriptCompilationAssemblyDefinitionFiles.html), 
+	    Open /Scripts/OSA.asmdef and add a reference to the Playmaker's asmdef file(s). Note that (at the moment of writing, 11.03.2020) Playmaker doesn't use .asmdef files
+	    by default (probably for compatibility reasons), so you'd have to manage it yourself.
+
+8.   Wait for scripts to compile. A compile directive will be added automatically as OSA_PLAYMAKER
+
+9.   (Optional, if #3 was also done) Import the DataMakerXMLTemplates-Unity2017-1-f3.unitypackage. Wait for scripts to compile.
+
+10.  Right-click on an UI element in the scene and choose UI->OSA. Follow the instructions in the wizard to set up some basic examples to get you started.
+
+11.  See the youtube tutorial linked in the manual (See "Playmaker support video" at the beginning of the doc under "External links"): https://docs.google.com/document/d/1exc3hz9cER9fKx2m0rXxTG0-vMxEGdFrd1NYdDJuATk
+
+12.  See what you can do with OSA through Playmaker: https://docs.google.com/document/d/1exc3hz9cER9fKx2m0rXxTG0-vMxEGdFrd1NYdDJuATk/view#bookmark=id.d2r5nao1bj3j
+
+
@@ -0,0 +1,8 @@
+fileFormatVersion: 2
+guid: 22cdfadf90754974eac79b3d005d6b44
+timeCreated: 1542052622
+licenseType: Store
+TextScriptImporter:
+  userData: 
+  assetBundleName: 
+  assetBundleVariant: 
@@ -0,0 +1,9 @@
+fileFormatVersion: 2
+guid: 29a12870007112842909c61e4ed1481a
+folderAsset: yes
+timeCreated: 1563652017
+licenseType: Store
+DefaultImporter:
+  userData: 
+  assetBundleName: 
+  assetBundleVariant: 
@@ -0,0 +1,38 @@
+(!) Important: No special setup is needed to use TMPro with OSA. This file only refers to using TMPro with InputFieldInScrollRectFixerTMPro.cs or TableView
+
+
+I. InputFieldInScrollRectFixerTMPro.cs 
+	- Depends on InputFieldInScrollRectFixerBase.cs from the Utilities.unitypackage
+
+This script contains code for using a TMPro InputField inside a ScrollRect (or OSA, of course). 
+Although you can attach this script when TMPro is not imported, it'll throw an exception at runtime. Make sure TMPro is imported before using it.
+Check the file for more info.
+This was initially needed for the TableView, but was included in the utils as a general extension of the original InputFieldInScrollRectFixer script
+
+
+II. TMPro in TableView
+	- Depends on TableView.unitypackage
+
+TableView's cells can work both with UnitEngine.UI.Text and TMPro.TextMeshProUGUI components. 
+Using it with TMPro requires you to import TableViewTMProSupport.unitypackage from /Extra/PluginSupport/TMPro.
+(!) But this shouldn't be the first thing you do. This is important, otherwise the OSA's TMPro will probably get corrupted and you'll need to delete your 
+Library folder to restore them, as even re-importing them from the package doesn't seem to work.
+Here are the steps:
+
+	1. Make sure you use version TMPro 1.0.56.0b1 or above, as that version was used to create the OSA's TMPro-specific prefabs.
+	2. (If not already done) Import TableView.unitypackage from /Extra.
+	3. Add OSA_TV_TMPRO to Scripting define symbols in Player settings. 
+	4. If you don't get any error, it means you're using a Unity+TMPro combo that allows TMPro to be seen by any code in your project. You can skip this step.
+	   Otherwise, depending on which Unity and TMPro version you're using, you'll need to do one of the following:
+	   a) Select OSA.Utilities.asmdef and add a reference to the TMPro assembly in its inspector (for ex., you may see "Unity.TextMeshPro" in the options). 
+	   If you don't see the TMPro assembly, but can create a TMPro Text object the scene, see b). If you cannot create a TMPro Text in the scene, it means 
+	   you didn't import TMPRo. Do it now and read the steps again.
+	   b) On some Unity+TMPro combos TMPro doesn't appear as an option in the "Assembly Definition References" section of OSA.Utilities.asmdef, nor in its 
+	   "Assembly references" section (i.e. your Unity version doesn't support that). In this case, not only OSA, but other plugins that use asmdefs 
+	   won't be able to see TMPro, and the only solution is to delete the asmdefs of that plugin. So this means deleting all OSA's '.asmdef' files.
+	   Final note: It's higly recommended to update your TMPro version and/or Unity version so that you can use option a) and have an easier upgrade 
+	   path to future OSA versions. If that's not possible, just keep in mind to repeat this step each time you update OSA, if you won't also update
+	   Unity and/or TMPro to use option a).
+	5. Now import the TableViewTMProSupport.unitypackage.
+	6. Restart Unity. This is needed because the TMPro prefabs on some Unity versions are incorrectly imported (Unknown cause).
+	7. Now when you create a TableView via OSA Wizard (right click on an UI element in hierarchy -> "UI/Optimized TableView (OSA)"), the TMPro prefabs will be used.
@@ -0,0 +1,8 @@
+fileFormatVersion: 2
+guid: 028e2ef88a4b1a6409172e68ccc66730
+timeCreated: 1563652017
+licenseType: Store
+TextScriptImporter:
+  userData: 
+  assetBundleName: 
+  assetBundleVariant: 
@@ -0,0 +1,8 @@
+fileFormatVersion: 2
+guid: 6bc73531a4ad29444a3348e1a0b66211
+timeCreated: 1563738640
+licenseType: Store
+DefaultImporter:
+  userData: 
+  assetBundleName: 
+  assetBundleVariant: