Does anyone have a solution to this?
Solved
GetPublishedParamNames function return garbled code when the param name is Chinese or other unicode character
+1- Contributor
- 1 reply
Best answer by hkingsbury
It’s probably worth also opening up a support case with Safe and linking this thread
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+53- Influencer
- 386 replies
sorry there is not enough context here to debug your problem. Here is how to place good support requests
there is an attachment icon on these windows
- Contributor
- 1 reply
FME Workspace file: test.zip, we created a published parameter named “测试”.
#include <isession.h>
#include <iworkspacerunner.h>
int main()
{
IFMESession* session;
FME_MsgNum err = FME_createSession(session);
if (err)
{
return 0;
}
err = session->init(NULL);
IFMEWorkspaceRunner* runner = session->createWorkspaceRunner();
IFMEStringArray* array = session->createStringArray();
IFMEString* str = session->createString();
*str = "test.fmw";
runner->getPublishedParamNames(*str, *array);
for (size_t i = 0; i < array->entries(); i++)
{
std::string item = (*array)(i);
printf("%s\n", item.c_str());
}
session->destroyString(str);
session->destroyStringArray(array);
}
After resolving the workspace file, the parameter’s name will be “????”.
+63- Celebrity
- 1625 replies
- Best Answer
It’s probably worth also opening up a support case with Safe and linking this thread