LEADTOOLS Support
General
General Questions
LeadTool ocx as a part within our ocx which in its turn will be resident in a html-page.
This topic and its replies were posted before the current version of LEADTOOLS was released and may no longer be applicable.
#1
Posted
:
Tuesday, May 23, 2006 2:30:58 AM(UTC)
Groups: Registered
Posts: 1
In a project coming up we intend to use the LeadTool ocx as a part within our ocx which in its turn will be resident in a html-page.
We have encountered a problem when we use “your” ocx within our ocx. When “your” ocx is used directly in a html-page it works as intended. When “your” ocx is used within our ocx the ocx is not loaded.
We suspect that the licence is involved in some way. When the html-page is opened on a computer with a licence for “your” ocx everything works well, but otherwise we do not get it to function.
We kindly ask for your advice and a program example to solve this problem.
#2
Posted
:
Thursday, May 25, 2006 12:41:24 AM(UTC)
Groups: Guests
Posts: 3,022
Was thanked: 2 time(s) in 2 post(s)
Yes, the license file is is involved in this issue. When you wrap
our OCX in your OCX, the license string is not read from the license
file and passed to our control. This is why you need to have the
license file on each client accessing the Web page, which is not
permitted. The OCX does not provide any means to pass the license
string though code. I suggest that you switch to using our COM
objects instead. The COM objects include the LEADRasterFactory
which you can use to pass the license string though code.
LEADTOOLS Support
General
General Questions
LeadTool ocx as a part within our ocx which in its turn will be resident in a html-page.
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.