Yes they are valuable things to add to the plugin. I’ll add them to my todo list.

I found a mistake on select date and time with buttons – http://rettica.com/calentim/docs/readme.html#showing-dropdown-apply-cancel-buttons

If I select a date and then scroll the time over 24 hours then the selected date will be ignored and he add one day on it

the input will change when i click the apply button but it is confusing if the input field don’t have the selected date

That’s the main logic to have the apply changes button. That’s by design.

I know that it is the standard logic but it is confusing when you select the 15.10.2019 and then scrolls 2x over 0 clock to get to the desired time and then click on submit and he inserts 17.10.2019 06:30:00 though you had selected the 15th.

Maybe an option you can set false that he should not count X days higher, no matter how much you turn?

Yes that makes sense. I can do it as an option whether the day selection should also be updated when the time overflows to the next/previous day or the time overflow doesn’t happen at all. Thanks for pointing that out!

I’ve removed the date change via timepickers feature, it’ll be released within the next version (1.3.4).

Works fine thanks for Update

Up and down swiping is not supported only left and right to switch months if that’s what you’re asking. And in the init method you can set instance.globals.isMobile to true when the browser user agent belongs to an iPad.

Left and right swipe not working on my ipad air 2

I have add instance.globals.isMobile = true; and log is as true but with my ipad air 2 but the calendar view will not open on click

Set enableKeyboard to true and try switching with tab key.

It’s not planned for calentim but I might think adding it to caleran because of the time pickers. Multiple dates are OK but multiple times seem hard.

Hello, ı forgot to add it into the documentation. But here’s an example to how to use it:

And here’s another advanced one:

Thanks bro!

But there’s a bug I fixed but not pushed yet in the hotel booking, but you can safely use it, you won’t need to change anything when the new version is released.

What exactly is the difference when using isHotelBooking ?

The disabled ranges’ start and end date becomes half selectable. Like a day is someone’s check-out date while someone’s check-in date.

Ok, understood. On the disabled var in the example, I see ‘2019-08-01‘ What is the trailing :21 represent?

Hello kveldscholten, can you prepare me a demo? I couldn’t reproduce it. Maybe it’s something related to my last commits to the plugin, it may be fixed.

Can you add this block to your initializer:

oninit: function(instance){
       var currentDate = instance.config.startDate.clone();
       while(instance.isDisabled(currentDate) == true) currentDate.add(1, "days");
       instance.setStart(currentDate);
       instance.validateDates();
},

oh yes this works. thx

You’re welcome

sry one problem have it with this code. Now date is 20.08.2019 16:30 but your code set always 20.08.2019 12:00

console.log(currentDate) say 20.08.2019 16:30 but instance.setStart(currentDate) set always 20.08.2019 12:00

Modify the time of the moment instance as you wish when setting the current date.

There was a bug in isDisabled method, I fixed it and will release shortly. Thanks for pointing that out.

Thx for Update

Did it fix the issue of yours?

yes

but when i click in the input field the default date is empty (not selected) instead the first available date

edit: oh okay all saturdays can’t selected

Is it working? Do you expect something from me?

Can you specify the format parameter? as “DD.MM.YYYY HH:mm”? The script may not parse the date you’ve given with the “L LT” format.

Hello, in the image you’ve sent me seems like a CSS issue or something. It can’t be related to hideOutOfRange option as I checked the source code. If you can prepare a live demo, I can see the problem clearly.

Sorry, I am wrong. Problem occure when I set rangeOrientation: “vertical” parameter.

can you try this css:

.calentim-input-vertical-range .calentim-left {
    flex: 1;
}

and also

.calentim-input-vertical-range .calentim-range {
    flex: 0 1 auto;
}

This css fix help, but the text in the ranges is not correct:

.calentim-input-vertical-range .calentim-left { flex: 1 !important; }

This is not working: .calentim-input-vertical-range .calentim-range { flex: 0 1 auto; }

Maybe you need to add a line-height: normal to the calentim range style above. I don’t know what’s causing that.

Hi webstream-solutions,

Thanks for buying and using my plugin first, and second, yes thats a good idea, but the arrow keys are moving the calendar days, maybe I can write a tab switch between calendars and time picker parts. I’ll try and let you know.

Hello tagsechs,

Thanks for buying and using my plugin.

1. startEmpty was intended to start with an empty calendar, I didn’t think of using it inside the time pickers, because if I wanted to start with an empty time selection, I would use 12:00 – 12:00 or 00:00 – 00:00 with a starting point. It’s equal to setting startDate and endDate with a predefined hour.I can think of one problem occuring when doing that, the input would be prefilled with that date. If you can give me some details about how the time pickers should act when starting empty, I can try to implement it into the core, or if a configuration doing this externally is possible, I can inform you.

2. try moment timezone plugin, it allows you to set momentjs’s timezone globally. https://momentjs.com/timezone/docs/#/using-timezones/default-timezone/

Hey. Thank’s for the answer.

You’re right. Start empty can be 00:00 or 12:00. My question was more about the input field which is combined with the timepicker. With startEmpty I expected that the input field was empty, not the timepicker itself.

The timezone tip was very helpful, thank you!

Now I have a third question. Do you plan to erase jQuery from this lib?

Yes, I have that plan but I guess not soon. But that’ll be a good challenge for me. Maybe I should do it sooner. I’ll check which jQuery features I’m using and try to replace one by one.

Would be nice. While you’re at it… maybe a change to https://moment.github.io/luxon/ makes sense. Apart from everything, thank you very much for this lib! With that you saved me a lot of trouble.

Hello, yes there’s an `instance.destroy()` feature available.I’ll add an example and let you know.

Thank you so much, I’ll be waiting!

Hi Skyll,

Did you read the documentation? You need to include moment.min.js and caleran.min.js to the <head></head>, then you can use $(”#picker-input”).caleran({options}) to initialize the input. Refer to the documentation for the details of options.

Hi, thank you, I send you (in private) the url where it’s integrated… and with moment.min.js and calentim.js (that’s what included in package), it don’t work at all. if i want it work, i must put in in the bottom of the page (under bootstrap and jquery) but if i do… calentim work, but i always loose the page header ?