Login Page - Create Account

Support Board


Date/Time: Sun, 26 May 2024 16:10:58 +0000



V1273 - Add custom study - not detecting existing Custom DLLs

View Count: 1622

[2015-07-21 03:45:27]
ejtrader - Posts: 688
SC Team - As of 1269 - Was able to select and add custom studies by selecting add Custom study - which used to list the existing custom dlls from which I could select the studies.

I have upgraded to V1273 - and no longer the existing custom dlls are listed(doesn't list any of the custom DLLs to select from). Interestingly the chartbooks that are built with custom studies work fine as expected but unable to add any any new custom studies. I tried to compile new dlls as well but is of no use.

I am using QT/g++ if it matters(was working fine until v1269). I have then tested with Visual studio and I can select the custom dlls in v2073.

Wondering if there are any changes done between SC version 1269 vs 1273 that could be contributing to this problem ( don't recall ever facing this issue in the past ).

Thanks
Date Time Of Last Edit: 2015-07-21 04:41:38
[2015-07-21 04:34:39]
Sierra Chart Engineering - Posts: 104368
So you are saying that a DLL built with QT/g++ does not have itself listed in the Add Custom Study window but if it is built with Visual C++ it does?

If so, then post one of the problem DLLs here so we can examine it.

Or if you can open the DLL file in a binary editor and post a portion of the the exported function table here so we can understand its format.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
[2015-07-21 04:43:01]
ejtrader - Posts: 688
SC team - you are correct about your assessment.

So you are saying that a DLL built with QT/g++ does not have itself listed in the Add Custom Study window but if it is built with Visual C++ it does?

I would try to build one very simple one and would post the dll.

Thanks
Date Time Of Last Edit: 2015-07-21 04:43:43
[2015-07-21 04:57:11]
ejtrader - Posts: 688
I tried with one simple one - which just consists of a single cpp file and it worked with qt/g++ combination ( which is somewhat good news).

Unfortunately my custom dll's have multiple cpp/library combinations. These used to work fine until 1269.

Would dig through further and see if I can isolate. If not - would try to create a sample one that doesn't work and would post the dll.

Thanks
[2015-07-21 05:15:37]
Sierra Chart Engineering - Posts: 104368
Yes, we need one that does not work and we will look at it and see what the problem is.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
[2015-07-26 03:38:43]
ejtrader - Posts: 688
SC team,

I have checked further on this. There were 2 issues actually ( it certainly was not a problem as of v1269 , qt/g++ combo.. I haven't tested 1270/71/72 - and jumped to 1273 and the issue got introduced. Even further to isolate the issue (whether there are any other changes at the system level) - I have reverted back to v1269 and the same code works fine. By using the following work arounds - I am able to proceed further with the latest version of SC v1276.

issue 1 - using a template function in one of the header files was causing the issue. Instead of template function I have moved it to regular function.
issue 2 - One of the statements using macro __FUNCTION__ is causing the issue when used in SC study(SCSFExport). If I use it in a function and call from SC study there are no issues. However unable to reproduce the issue with an isolated cpp file. As this is not critical I could proceed by commenting this macro for now.
ltext.Format("%s -->", __FUNCTION__);

I would experiment further on this as my time permits.

I am good for now though it is very strange( certainly a relief to isolate the issue ).

Thanks
Date Time Of Last Edit: 2015-07-26 03:54:03
[2015-07-26 06:11:30]
ejtrader - Posts: 688
SC Team - Confirmed that the macro - __FUNCTION__ in the main SC study can't be used directly any longer.

This can be used in functions which are called by SC studies but not in the main study itself(SCSFExport). I had this used in many places and was somewhat of an effort to get rid of this in many places. However back on track and can use the latest version of SC.


SCSFExport scsf_test()
{
callfunction1(1, __FUNCTION__); // this would cause issues - Mainly unable to parse the macro and pass to the function
callfunction2(1); // This would work
}

thanks
Date Time Of Last Edit: 2015-07-26 06:16:37
[2015-07-26 06:43:02]
Sierra Chart Engineering - Posts: 104368
Thank you for the information. This helped us determine the problem and it will be solved in the next release.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
[2015-07-26 14:26:28]
ejtrader - Posts: 688
On the same note - Sometimes(even with 1269 or earlier) I have noticed the study names (when tried to insert custom study) - It would appear as "scsf_Name" or sometimes just "Name". As there were no functional issues, didn't bother to report this issue.

One more issue is when multiple cpp files are combined, on occasions(reproducible) - with some weird combination - same study name appears when tried to insert the study. Only partial list of studies in the dll are visible rather than full list. I used some or other work around to overcome this issue ( either removing the cpp or moving the order or combining cpp files or something ). Don't remember from which version this problem was introduced though.

screencast.com/t/AULShbZ5

Hopeful that whatever the fix you are planning to have related to the original problem - it might address this repeating name issue as well ;)

thanks
Date Time Of Last Edit: 2015-07-26 14:43:22
[2015-07-26 22:15:42]
Sierra Chart Engineering - Posts: 104368
"scsf_Name" or sometimes just "Name".
This is because you did not set sc.GraphName or the sc.GraphName was set to "Name".

Only partial list of studies in the dll are visible rather than full list.
This should definitely be fixed in latest prerelease.

In the latest prerelease released at this time, if you still see a study name repeating, let us know.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
Date Time Of Last Edit: 2015-07-26 22:17:37
[2015-07-27 00:06:30]
ejtrader - Posts: 688
SC Team - Are you referring to v1277 as the latest version these issues are supposed to be fixed?

If so - I have downloaded this just a minute ago and following are my observations.

issue 1: missing dll issue - This issue is partially resolved. Now I can see dll being listed but only one of the studies is visible rather than multiple studies that I expected to see under this dll. If I take out the __FUNCTION__ based calls, I do see full list of studies.

issue 2: duplicate study issue - It didn't resolve the duplicate study issue. If I take out one of the cpp files, it works fine for the rest of the studies. There is no issue with individual cpp though. Don't know what could be contributing to this issue.

issue 3: study name sometimes appear as scsf_Name and sometimes just Name - I have defined GraphName to "Name" but it still appears as "scsf_Name" in drop down studies list ( for few of them appears correctly - so don't really know what the root cause for this to appear differently for few of the studies). This is not a show stopper issue though. Probably after issues 1 & 2 are resolved - I would try to isolate what could be contributing to this issue though.

screencast.com/t/fSM6FudQf

I do have the following Graphname defined under sc.SetDefaults section.


if (sc.SetDefaults) {
sc.GraphName = "CustomVWAP";
sc.StudyDescription = "CustomVWAP";
sc.GraphRegion = 0;
sc.FreeDLL = 0;
sc.AutoLoop = 1;
}

thanks
Date Time Of Last Edit: 2015-07-27 01:49:15
[2015-07-27 01:02:24]
Sierra Chart Engineering - Posts: 104368
Update with Help >> Download Prerelease to get the latest revision of 1277 and then test.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
[2015-07-27 01:03:35]
ejtrader - Posts: 688
sc team - That's what I did few minutes back. testing again now.

thanks
Date Time Of Last Edit: 2015-07-27 01:04:41
[2015-07-27 01:15:20]
ejtrader - Posts: 688
SC team - results from post 11 are applicable even with latest pre-release(1277). As mentioned earlier - compared to very initial 1277 - latest 1277 did resolve the missing dlls issue partially. but lists only one of the several studies that are supposed to be available in this dll.

thanks
Date Time Of Last Edit: 2015-07-27 01:22:35
[2015-07-27 02:52:37]
Sierra Chart Engineering - Posts: 104368
OK, there is no way we are going to be able to solve this unless we get the DLL file from you.

Otherwise, we can do nothing further in this support request. And therefore please do not post anything further because the information is no longer useful to us.

We cannot be guessing about the source of the problem.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
Date Time Of Last Edit: 2015-07-27 02:52:53
[2015-07-27 02:59:11]
ejtrader - Posts: 688
SC team - I would get you a dll soon on this.
[2015-07-27 04:22:37]
ejtrader - Posts: 688
SC team - I have figured out the reason for Issue 3. You don't have to spend any time for this specific issue 3.

Attached is the DLL demonstrating the same.

It was due to the location of sc.IsUserAllowedForSCDLLName function where GraphName was NOT being set.

I would also upload the dll demonstrating the other 2 issues..

Thanks
Date Time Of Last Edit: 2015-07-27 04:24:48
Private File
Private File
[2015-07-27 05:00:10]
Sierra Chart Engineering - Posts: 104368
One note about this DLL, we were not able to load it because it has other dependent files and we are not sure what those are.

However, when we look to the export table we see nothing unusual about it that Sierra Chart cannot handle.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
[2015-07-27 05:02:14]
ejtrader - Posts: 688
Attached is the DLL describing issue 1 compiled with SC latest version 1277.

Thanks
Date Time Of Last Edit: 2015-07-27 05:10:34
Private File
Private File
[2015-07-27 05:46:33]
ejtrader - Posts: 688
For post 18 - dependent files are QT library files.

Anyway - please use the attached source file and see if you can compile it and see all of the studies being visible or not.

Thanks
Private File
[2015-07-27 14:38:48]
ejtrader - Posts: 688
Attached is the DLL for the same source(post 20) using VS2013. I have attached the same source with a comment - if we bypass a statement it would make all studies visible.

Issue 1 - applicable here as well (not all studies being visible). If you are unable to reproduce the issue, I can provide the full VS project files.

Thanks
Date Time Of Last Edit: 2015-07-27 17:50:58
Private File
Private File
[2015-07-28 05:56:58]
Sierra Chart Engineering - Posts: 104368
This will be solved in the next release.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
[2015-07-28 12:52:23]
ejtrader - Posts: 688
FYI - v1278 - didn't resolve issue 1.
[2015-07-28 18:04:56]
Sierra Chart Engineering - Posts: 104368
We have not yet released the solution.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
[2015-07-29 03:49:25]
Sierra Chart Engineering - Posts: 104368
Try the latest prerelease. The version number is the same but we have made changes which solves all of this.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account