raynbow
Junior Member
Posts: 2
Registered: 6/23/2003
Member Is Offline
|
| posted on 6/23/2003 at 04:18 PM |
|
|
Error calling the calendar: no target control specified
Trying to add Calendar to JSP page with Struts but get "Error calling the calendar: no target control specified" when page is loaded.
Any help would be appreciated.
Thanks
|
|
|
nik
Posts:
Registered: 1/1/1970
Member Is Offline
|
| posted on 6/24/2003 at 09:53 AM |
|
|
Please, look at the following code fragment:
var cal1 = new calendar1(document.forms['tstest'].elements['input1']);
The problem you've described happens if input1 element of tstest form doesn't exist.
|
|
|
raynbow
Junior Member
Posts: 2
Registered: 6/23/2003
Member Is Offline
|
| posted on 6/24/2003 at 11:26 PM |
|
|
Actually I looked at the construction of the calendar2 method and noticed that it had 2 parameters; page and target.
So, I changed
var cal1 = new calendar1(document.forms['tstest'].elements['input1']);
for
var cal1 = new calendar1("calendar.html", document.forms['tstest'].elements['input1']);
Obviously, if you pass only one parameter it will be used by page and target will be null and the check a little further down in the code will
complain and exit.
Maybe I have an older version of the calendar2 js file, becuae your examples only show passing the target parameter.
|
|
|
nik
Posts:
Registered: 1/1/1970
Member Is Offline
|
| posted on 6/25/2003 at 08:10 AM |
|
|
In the latest Tigra Calendar version which is available on our site you should specify only target parameter.
|
|
|
netdocs
Junior Member
Posts: 2
Registered: 11/20/2003
Location: Leicester
Member Is Offline
|
| posted on 11/20/2003 at 12:45 PM |
|
|
asp.net - Error calling the Ctrl : no target specified
I get this error when the page runs. I've read previously that this means that the input control specified does not exist.
I have a textbox within a form and the script under the form calls the textbox as this:
var cal1 = new calendar1(document.all.Textbox10.text);
Although this doesn't seem to work. I thought it might be due to a form name being required, so I tried this but it gave the same error.
Anyone with any ideas?
Does the Pro version solve these problems?
Thanks,
Graham.
|
|
|