This happens because when you call $this.datepicker() it only initializes the date picker without ever showing it up.

So if you click it again, that will be the time that the date picker will show itself since it was already initialized.

What you can do to show the date picker right away on first click is to call it like this:

That should do it.

When I tried using the Datatable feature of JQuery together with Angular JS, it was smooth sailing. After all, the data used was static, meaning I created the objects upon initialization.

When it was time to use real data from the database, the JQuery Datatable shows the “No data available” even though there are some data in it.

The cause for this is that the data retrieved was asynchronous, so once the object that the Datatable used has contents, it will populate those objects within it. However, the “No data available” message still appears.

That, and the Datatable was created before any data was populated with it contributed to this behavior.

I came across a solution from a user in the StackOverflow forum named tasseKATT.

What he did was to add a directive to the app and using the timeout after the DOM has rendered to then create the Datatable while also adding an ng-if expression where the table creation takes place such that if the object used contains more than 1 entry, then that will be the time that the table DOM will be created and such, the Datatable creation will also be called.

Pretty sweet.

Overall I can sum it up to bugs and lag. I was surpised this happened. Google did not bother QA’ing the new Android operating system codenamed Lollipop in older Nexus devices?

This is one big blunder. And it has affected so many users. Worse, it greatly affected my game because it uses Thread.sleep in some cases and it now moves like a roller instead of smooth movements.

So here are some things that I noticed with Lollipop which I think is not advisable to be upgraded until Google provides a lightning quick fix.

WIFI – I noticed it takes some time to connect to WIFI hotspots. I also get cut off sometimes.

System lag – when I go to apps, I noticed slowdown and lagtime during transitions. I feel like my Nexus 7 2013 feels like a 2005 version. Hell, my card game might get bad reviews from ignorant users who think the animation in my app is slow is due to the developer when in fact, Lollipop is to blame

New apps – while this may not be a bad thing, I find no use for apps like Sheets and Slides so why are they sync enabled in the Google account by default?!?!

UI – come on! User interface overhaul? Sure, some are good but seriously, a little consistency at least. Plus the WIFI icon looks fugly. Keyboard is meh but I guess I can live with it.

Chrome loading icon – it looks funny but when you have a slow connection and you opened up a lot of tabs to load webpages, you may notice one of the tabs’ circle progress loading icon move itself in and out of the tab area.

These are the few things that git me peeved with Lollipop and even though this is a new version, I wish there is an easy way to revert back to Kitkat.

And no, I do not want to reset my tablet just to see if thinga will be different. So this blunder is really on Google.

Related Posts Plugin for WordPress, Blogger...