Prometheus vs Rad.
In Rad I was able to use
ClientScript.RegisterStartupScript(cstype, "", " AjaxNS.AR('ctl00$ContentPlaceHolder1$Buttonx', '', 'ctl00_ContentPlaceHolder1_RadAjaxPanel1', event); ", true);
to Submit my page back to itself. I am creating some images for the user and want to show the loading panel while the work is being done. When the image finish creating the "Loading" would disapear.
With Prometheus I can get the page to submit back to itself, but the loading panel does not appear.
I have tried:
ClientScript.RegisterStartupScript(cstype, "", " 'ctl00_ContentPlaceHolder1_Buttox.click(); ", true);
ScriptManager.RegisterStartupScript(Buttonx, cstype, "", " 'ctl00_ContentPlaceHolder1_Buttox.click(); ", true);
If I disable the start up script and just click the button the loading panel does appear.
I can tell that is it is not firing the OnRequestStart event of the loading panel.
What I am trying to accomplish is that the page loads - then automaticly post back to it self showing the loading panel. Generate some user images in the code behind of the button click. show the images - then hide the loading panel.
Any help would be appreciated.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
My colour picker works great. But if I am to leave this line out it ruins the spacing for the colour picker. I have tried adjusting every setting eg: width etc but have no luck.
I need to exclude the DOCTYPE line from my code as my CSS file is a .aspx (so it builds the css values from a database) and does not work in FIREFOX if I enclude that line.
Does anyone know how I can adjust the spacing for the colour picker?
Just clear up what I am getting:
[] = a colour square
[] [] [] [] [] [] [] [] [] [] [] [] []
[] []
[] [] [] [] [] [] [] [] [] [] [] [] []
[] []
[] [] [] [] [] [] [] [] [] [] [] [] []
[] []
[] [] [] [] [] [] [] [] [] [] [] [] []
[] []
[] [] [] [] [] [] [] [] [] [] [] [] []
[] []
[] [] [] [] [] [] [] [] [] [] [] [] []
Thanks
Response.Redirect(
"somepage")
in the AppointmentCreate-event or the nserted event of the Scheduler, aajaxMgr.Redirect(
"create_schedule.aspx");
But it also appears sometimes with that approach.The radconfirm function has the following function signature according to the documentation:
radconfirm(text, callBackFn, oWidth, oHeight, callerObj, oTitle)
And the callback function that's passed as parameter callBackFn in the above signature has a function signature of:
confirmCallBackFn(arg)
The Arg parameter is described as being True if the user clicks OK and False if the user clicks Cancel (should actually be true and false -- little "T" and little "F", but I digress).
My main question: what happens to callerObj parameter defined in the radconfirm function signature? Shouldn't it be passed into the confirmCallBackFn as a parameter (e.g. the function signature should change to be confirmCallBackFn(arg, callerObj))? This would be very convenient as I could then abstract away the calling of the confirmation dialog somewhere else and pass into my convenience function the function that should run on confirmation. E.g.:
function doConfirm(message, title, functionToCallOnConfirm) { radconfirm(message, onConfirmCallback, null, null, funtionToCallOnConfirm, title); }; function onConfirmCallback(arg, callerObj) { if (arg) callerObj(); }
Then, where I need the confirmation dialog in my client app, I can simply do:
function somethingThatRequiresConfirmation() { doConfirm("message", "title", doSomething); } function doSomething() { // Code to do something }
This is nice because every developer on the team doesn't have to concern themselves with how the confirmation dialog works. They just call the doConfirm function with their text, pass their worker function and they're done.
Secondary, and very minor question: Isn't there a better way than completely overriding the dialog template to change the text on the buttons? The documentation indicates the text is "Yes" and "No," however, in practice (at least with the "WebBlue" skin) the text is actually "OK" and "Cancel" mimicking the undesirable behavior of the default javascript confirm function.