"copy files", specialfolderpath("resources") and missing files = SHOWSTOPPER

[Klaus major-k]

Maybe noone got the point of my posting?

The point is, that I add files and folder to the standalone via the "Copy files" tab
in the "Standalone Application Settings", however some of these files are missing 
in the final runtime. However instead they can be found in -> specialfolderpath("engine")

What is happening here and why does LC not copy everything to the RESOURCES folder?

> Am 09.08.2019 um 15:22 schrieb Klaus major-k via use-livecode <use-livecode at lists.runrev.com>:
> 
> Hi friends,
> 
> I am currently making an existing app "64Bit safe" for a customer with LC 9.5 
> on macOS 10.14.6.
> 
> In this app there are some "compiled shell scripts" (? I guess, have no infor about this)
> which changes the keyboard layout (chinese and back) to german depending of the target 
> fields in LC.
> 
> Structure (three files and two folders):
> ## File
> extSetInputMethod
> 
> ## Folders
> x86-64/extSetInputMethod
> x86-32/extSetInputMethod
> 
> I guess the first one checks the current architecture and then calls the correct version for this.
> Whatever, this works fine in the customers older apps.
> 
> So I added all this via the "Copy files" tab in the "Standalone Application Settings"
> However these files were NOT in specialfolderpath("resources") in the runtime?
> 
> In the runtime I find this:
> the_actual_app.app
> -> /Resources
> -> /Resources/Externals ## empty, no externals used in app
> -> /Resources/x86-64 ## EMPTY!?
> -> /Resources/x86-32 ## EMPTY!?
> 
> File -> extSetInputMethod = missing and the two latter folders are EMPTY!?
> Where on earth are the contents of the other folders?
> 
> But I find this in:
> the_actual_app
> -> /MacOS
> -> /MacOS/extInputMethod ## the missing file! see above
> -> /MacOS/x86-64/extInputMethod  ## the missing file
> -> /MacOS/x86-32/extInputMethod  ## the missing file
> ...
> 
> So calling the shell apps in -> specialfolderpath("resources") does of course not work!?
> If I copy them manually to the correct folder in the runtime, they stop working.
> So all in all this is a real showstopper! :-/
> 
> Am I overlooking something?
> Is this correct behaviour of LC?
> What can I do?

--
Klaus Major
https://www.major-k.de
klaus at major-k.de