CSPro Users Forum

Android security restrictions prevent you accessing from data in most folders, but you can access files in the Downloads directory. See more here:

https://www.csprousers.org/help/CSPro/a ... tions.html

That feature was added in November 2018. Maybe we need to do a better job highlighting new features...

It sounds like you want to use the feature "Initialize as Dictionary Label" that is part of Question Text Macros:

https://www.csprousers.org/help/CSPro/q ... acros.html

There is no way, using CSDeploy, to specify that you want the application deployed to a specific subdirectory. Why do you need this specific path? You can always: 1) Use CSDeploy to deploy to a "Local folder." 2) Upload the files from this folder (using syncfile) to a specific location on ...

Sorry for the delayed response. CSPro sometimes has bugs related to using multiply-occurring items on multiply-occurring records. At some point we intend to revisit the code related to this, which is now several decades old, but for now we generally advise against these multiple levels of repetition...

None of us were able to replicate this behavior. Your screenshot definitely suggests that it is an error, but without being able to reproduce it, it is hard for us to provide guidance.

You might consider upgrading to CSPro 8.0 ... hopefully your application will work in that newer version.

With the current Android security settings, you won't be able to do much with execsystem. Take a look at page describing ways to interact with other applications: https://www.csprousers.org/help/CSPro/android_interacting_with_other_applications.html You'll likely have to ask Esri, but your best opti...

FYI...this will be fixed in CSPro 8.1.

Binding function parameters via lambda expressions could result in the the lazy evaluation that Josh mentions. For instance in C++: int GetArgument() { return 1; } void func1(int x) { } void func2(std::function<int()> get_x) { } func1(GetArgument()); func2([] { return GetArgument(); }); With func2, ...

Wow, that is a quirk! Without even looking at the C++ code, I know that it's true that if a function has no body, that the arguments aren't evaluated. I'll change that for CSPro 8.1.