javascript - JQuery .show() is only working in first page of a table with JQuery datatable -


मेरे पास & lt; select & gt; एक इस तरह एक DataTable की: 

  & lt; td & gt; & lt; चुनें class = "cambioEstado" & gt; & Lt; विकल्प शैली = "प्रदर्शन: कोई नहीं;" मान = "14" वर्ग = "ऑप्शन 4" & gt; एल 4 & lt; / विकल्प & gt; & Lt; विकल्प शैली = "प्रदर्शन: कोई नहीं;" मान = "15" वर्ग = "ऑप्शन 5" & gt; एल 5 & lt; / विकल्प & gt; & Lt; / चयन & gt; & lt; / टीडी & gt;

जब मैं कोई बटन दबाता हूं, तो मैं .show () के साथ विकल्प प्रदर्शित करता हूं: 

  $ ("। Btn4")। Live ("click पर क्लिक करें ", फ़ंक्शन () {$ ("। Opcion4 ")। शो ();});

लेकिन यह पहला पेज के लिए ठीक काम करता है, जब मैं दूसरा पेज जाता हूं, बटन को "ऑस्पियन 4" दिखाने के लिए फिर से दबाया जाना चाहिए।

अंत में मैंने प्रत्येक विकल्प की स्थिति को बचाने के लिए एक सरणी का उपयोग करने की समस्या का समाधान किया, और fnDrawCallback फ़ंक्शन का उपयोग करके स्थिति को पुनर्स्थापित किया डेटासेट का

fnDrawCallback निकाल दिया जाता है। 

  var estadoListados = new Array (); $ ("। बीटीएन 4")। लाइव ("क्लिक करें", फ़ंक्शन () {$ ("। Opcion4")। शो (); एस्टाडो लिस्टाडोस [4] = "एबियंटो";}); Var optionDT = {"एएएसर्टिंग": [[0, "एसीसी"]], "एफएनडीआरओ कॉलबैक": फ़ंक्शन () {के लिए (एक्स = 0; एक्स & लेफ्टिनेंट; एस्टाडो लिस्टाडो. लैंघ; एक्स ++) {यदि (एस्टाडो लिस्टाडोस [x] === "Abierto") {$ ("। Opcion" + x) .show (); } अगर (एस्टाडोलास्टाडोस [x] === "सेरराडो") {$ ("। ऑस्पियन" + x) .hide (); }}}, "SPaginationType": "पूर्ण_संख्या", "iDisplayLength": 25, "ओलान्यूजेज": {"sUrl": "../js/bootstrap/datatables/media/language/dataTables.spanish.txt"}}; $ (दस्तावेज़) .ready (फ़ंक्शन () {oTable = $ ("। डेटाटेबल")। डाटाटेबल (optionDT);});

Comments

Post a Comment

Popular posts from this blog

c# - Reactive Extensions ControlScheduler -

Well, I'm using Reactive Extension Event Handler to handle my app events, I run the headlines on the Yuri thread. I also use ControlSubular for However, recently I am getting cross thread exception despite using control scheduler and I do not know what the problem is. Code: Observable.FromEventPattern & Lt; String & gt; (CC, "UiAlertMessage", New Control Session ()) Subscribe (_ = & gt; {Alert Control. (Show this language, title, _.EventArgs.UppercaseFirst ());}); The new control scheduler (this) is not to run the code on the UI control thread, so I do not get cross threading exceptions? you should do Observable.FromEventPattern & lt; String & gt; (CC, "UiAlertMessage"). AboveOption (this). Subscribe (_ = & gt; {Alert Control. (Show this language, Titles, _.EventArgs.UppercaseFirst ());}); This is the standard way of sending a scheduler related to specific controls. Passing control scheduler as you have got subsc...
Read more

scala - Play Framework - how to bind form to a session field -

Is there any way, I can get some parameters from the header, cookies (log in userId in my case) , And then apply it in a form which I know who will deposit the ticket? SupportForm supportForm: form [supportTicket] = form (mapping ("question" -> text, "priority" -> text) (apply support ticket. (HelpText.update) What are the good practices here? What is the call to apply the request, when I can use it (and also a good practice?) Edit An issue, absolutely deceiving anyone if I were to create a hidden area with this value. It could Ript, but the issue may be re-used in any way to verify and return the form, it can not be sure how it ....
Read more

Firefox reacting to JQuery setTimeout that doesn't apply -

& lt; - Only note the first image. I think some jquery is not working in Firefox, where there seems to be a problem ... but there is IE (I know, I know) var hover = $ ('# par1'), box = $ ('.sq1'); Hover.hover (function () {box.toggleClass ('index2');}); and var linkloc = $ ('# par1'), link = $ ('# frnt1'); Linkloc.on ('mouseenter', function () {function linkadd () {link.html ("& lt; a target = _blank href = http: //www.google.co.uk> & lt; img src = small1 .JPG / & gt; & lt; / a & gt; ");} Set Timeout (linkAD, 1500)}); Linkloc.on ('mouseleave', function () {link.html ("& lt; img src = small1.JPG />");}); I appreciate that the code can be a bit messy, but I'm still learning as I go. The problem now is that the top slice of the code is reacting down to the setout. (It revolves around time with setTimeout repeatedly) even though the name of the function is c...
Read more