jquery - inconsistency between `.live()` and `.autocomplete()` -

-

निम्न कोड में, .live () काम नहीं करते, लेकिन । स्वतः पूर्ण () करता है क्यूं कर? (देखें) <पूर्व> var इनपुट = []; input.push ($ ( 'इनपुट')); $ (इनपुट) .live ('keydown', फ़ंक्शन (इवेंट) {console.log ('आपने एक कुंजी दबाई है!');}); $ (इनपुट)। Autocomplete ({source: ['test1', 'test2']});

.live () क्वेरी ऑब्जेक्ट विधि संचालित मौलिक चयनकर्ताओं के प्रश्नों पर $ ([$ ('input')]) एक चयनकर्ता क्वेरी नहीं है, यह एक चयनकर्ता क्वेरी युक्त एक सरणी पर एक क्वेरी है।

से:

... .live () विधि को हमेशा एक चयनकर्ता के बाद सीधे कहा जाना चाहिए ...

से कॉपी किया गया मेरी टिप्पणी नीचे दी गई है:

.autocomplete () काम करता है क्योंकि यह अन्य jQuery फ़ंक्शंस के साथ अधिक कार्य करता है, जो क्वेरी द्वारा दिए गए ऑब्जेक्ट की गणना करता है और उन पर कार्य करता है हाथोंहाथ। .live () नहीं गणना , लेकिन बाद में क्वेरी का निरीक्षण करता है - जब भी कोई ईवेंट निकाल दिया जाता है चूंकि क्वेरी उस रूप में नहीं है जिसकी अपेक्षा की जाती है, यह केवल इसे अनदेखा करता है।

Comments

Post a Comment

Popular posts from this blog

php - Creating canonical URLs with custom route-classes -

-
I am trying to implement the canonical url and to combine with custom route classes. URL-SACAME is something like this: / category-x / article / 123 / category-y / article / 123 I am creating a custom route - the expansion of the class Zend_Controller_Router_Route_Regex and checks that the article is 123 and the correct category-name is included in the URL. If the article is in 123 square-X and the user is reaching square-y, then I want to redirect to the correct URL. But there is no clear possibility to do this directly to the roads. What is the best practice approach here? I often do this in my action controller like something ... // Get / Category-Y / Article / 123 $ $ article- & gt; URL is generated, and it contains / category-x / article / 123 if (this-> --request-> getRequestUri ()! = $ Article-> URL) {return $ this- & gt; ; _helper-> Redirector-> GoToUrl ($ paragraph-> url); } In this example, $ article-> The url will need ...
Read more

Mysql Local server hardware -

-
In anticipation of a live scenario, I am creating my entire site, which has a 500 MHz processor with 256 MB A very large 100 MHz RAM I have loaded my database with 200k + rows of garbage data, trying to test my queries. I have seen - obviously because of this, a large display hit all my FAQ using the index, although some 15+ to join (using all indexes) using MySQL To enable 16MB cache, which brings down the query times to nothing but what results? With a dynamic website, I can not see how the cache can help completely when I allow unique queries such as a search feature. I am also using the eaccelerator for PHP. When I use the COUNT (*) total with multiple code JOIN and WHERE , then 10 + There are other queries. Other queries that only get the same line or two do at the same level when I had only a few lines I also noticed that almost 99% of the CPU in CPU CPU stress during a query Comes. Basically I do not know whether the software is on the fault or too much of the h...
Read more

mysql - Formatting problem with PHP DateTime Difference when used as part of an equation -

-
I am trying to write a simple invoicing system. I want to use the Datetime Diff to calculate the cost of each invoice. I have so far: / * In this example $ dayLength and $ ratePerSec is not really the case, but now we use the hypotethical values ​​of 8.0 and 0.0054 Will * / $ date1 = new date time ("Time 1 Form Database", [DateTimeJonof Chase]); $ Date2 = new date time ("Time 2 Form Database", [Datetime Joneof Choice]); $ Diff = $ date2- & gt; Diff ($ date1); $ LenInSec = $ diff- & gt; Format ("% y") * 365 * $ dayLength * 3600 + $ diff- & gt; Format ("% d") * $ dayLength * 3600 + $ diff- & gt; Format ("% H") * 3600 + $ diff- & gt; Format ("% i") * 60 + $ diff- & gt; Format ("% s"); $ Cost = $ lenInSec * $ rate per second; When I try to output cost using $ lenInSec generated from the Deltaime Diff, I actually get weird results. Occasionally, in 1 and 3 out of 1 to 3 times, I get the...
Read more