Skip to main content

How to disable a calendar button....

When you disable a Datepicker field, you can still click the matching image next to that field and doing so will popup the calendar window.

You can easily get this functionality using jQuery:

$(function(){
$('td.datepicker input:text').each(function(){
var i=this.id;
$('#'+i+'_IMG').click(function()
{return (!document.getElementById(i).disabled);});
});
});

This function adds a click event to the Calendar image that will only return true - and therefore do something - if the date field is enabled. You can see how this works on apex.oracle.com.

Why doesn't APEX handle this by itself? I really don't know. Maybe they'll copy this solution (or similar) in the next version....

Comments

Anonymous said…
Roel,

Setting the field with a read only condition will not only make the field into a display only field but also removes the datepicker icon as well. So the functionality is already in APEX.

This also works for the JQuery datepicker that I have implemented thanks to your input.

Regards,

Jon
kavitha said…
HI Roels,
I am working for apex development,
2nd point, Add a click event to each datepicker image.
Could u please explain me more detail like where to add it????
Roel said…
Kavitha,

The function itself adds a click event to the image. You don't have to do anything. Just copy and paste the code in your Page HTML Header (and incorporate jQuery of course).

Roel
kavitha said…
Hi Roels,
Thanks for your reply.
Please tell me how to incorporate jQuery??.

Thanks
Roel said…
Hi Kavitha,

See this post
kavitha said…
Hi Roels,
Thanks for the link..
the same code, with little change,
$(function(){
$('td.lov input:text').each(function(){
var i=this.id;
$('#'+i+'_IMG').click(function(){return (!document.getElementById(i).disabled);});
});
});

i use for disabling the popup lov but it was not comming.
Please, am i doing anything wrong ?

kavitha
Roel said…
Kavitha,

Check in your "each" function if the right items are selected.
So does i have a (correct) value? And does the IMG item (i+'_IMG') actually exists?
Wolfgang said…
Hi Roels,

do you have a solution that works with APEX 4.0 (4.0.2) too?

Regards,
Wolfgang
Roel said…
Hi Wolfgang,

The example runs on apex.oracle.com. And that's running apex 4.0.2. So it is working in the latest version of apex.
But in the latest version you probably would use Dynamic Actions to get the same result (without any coding). See the updated example:
Created a (Standard) Dynamic Action on the radio group; if the value = 'Y' (Disable) then Disable the date otherwise enable.
So that's the way you should do it nowadays!

Roel

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function