StandaloneFileBrowser can't be found: mudanças entre as edições

De TriLib
Ir para navegação Ir para pesquisar
(Criou página com 'TriLib comes with a custom version of StandaloneFileBrowser (the original can be found here: https://github.com/gkngkc/UnityStandaloneFileBrowser) It is an optional package,...')
 
Sem resumo de edição
Linha 1: Linha 1:
TriLib comes with a custom version of StandaloneFileBrowser (the original can be found here: https://github.com/gkngkc/UnityStandaloneFileBrowser)
TriLib comes with a custom version of '''StandaloneFileBrowser''' (the original can be found here: https://github.com/gkngkc/UnityStandaloneFileBrowser)
 
It is an optional package, and if you don't want to use it, you can import only the "'''TriLibCore'''" (and the folder from your rendering pipeline, in case you're using anything other than the Standard rendering pipeline) folder from the TriLib package.
 
Sometimes when building/running your application, you may get a message saying "StandaloneFileBrowse can't be found" or something similar.


It is an optional package, and if you don't want to use it, you can import only the "TriLibCore" (and the folder from your rendering pipeline, if you're using anything other than the Standard rendering pipeline) folder from the TriLib package.


Sometimes when building/running your application, you may get a message saying "StandaloneFileBrowser" can't be found or something similar.
Generally, this happens because the appropriate StandaloneFileBrowser plugin hasn't been included in your build project.
Generally, this happens because the appropriate StandaloneFileBrowser plugin hasn't been included in your build project.


To make sure StandaloneFileBrowser is included in your build project, head to the "Assets/TriLib/TriLibStandaloneFileBrowser/Plugins" directory and look for the plugin file according to the platform you will deploy to.
You can fix these issues by doing the following:
In this case, I'm selecting the "x64" StandaloneFileBrowser plugin inside the "Windows" folder, as I will deploy my application to Windows x64 devices:
 
[[Arquivo:Step1.png|commoldura|To make sure StandaloneFileBrowser is included in your build project, head to the '''"Assets/TriLib/TriLibStandaloneFileBrowser/Plugins"''' directory and look for the plugin file according to the platform you will deploy to.
 
 
In this case, I'm selecting the '''"x64"''' StandaloneFileBrowser plugin inside the '''"Windows"''' folder, as I will deploy my application to Windows x64 devices.]]




You can then select the appropriate architecture you want the selected plugin to be used:


This should fix the "StandaloneFileBrowser can't be found" type of issue.
[[Arquivo:Step2.png|commoldura|You can then select the appropriate architecture you want the selected plugin to be used, then click '''"Apply"'''.]]

Edição das 13h32min de 10 de fevereiro de 2022

TriLib comes with a custom version of StandaloneFileBrowser (the original can be found here: https://github.com/gkngkc/UnityStandaloneFileBrowser)

It is an optional package, and if you don't want to use it, you can import only the "TriLibCore" (and the folder from your rendering pipeline, in case you're using anything other than the Standard rendering pipeline) folder from the TriLib package.

Sometimes when building/running your application, you may get a message saying "StandaloneFileBrowse can't be found" or something similar.


Generally, this happens because the appropriate StandaloneFileBrowser plugin hasn't been included in your build project.

You can fix these issues by doing the following:

To make sure StandaloneFileBrowser is included in your build project, head to the "Assets/TriLib/TriLibStandaloneFileBrowser/Plugins" directory and look for the plugin file according to the platform you will deploy to. In this case, I'm selecting the "x64" StandaloneFileBrowser plugin inside the "Windows" folder, as I will deploy my application to Windows x64 devices.


You can then select the appropriate architecture you want the selected plugin to be used, then click "Apply".