Jump to content

requinix

Administrators
  • Posts

    15,290
  • Joined

  • Last visited

  • Days Won

    436

Everything posted by requinix

  1. Okay. So where are you getting "www.test.local" from? Also, forget the hostname and just use localhost.
  2. Exactly what happens when you try a regular CREATE TABLE? Look carefully. And opinion: if you need IF NOT EXISTS then that means you don't know what is happening to your database. You should always know whether the table exists or not.
  3. Where are you getting "www.test.local" from? Just use localhost.
  4. Not quite, no. It was a matter of the elements being visible or not. Or I guess for consistency's sake I should say it was about them being visible or not. If the modal is hidden then the prices are not visible, right? And if you tell jQuery that you want to remove the visible prices then that's not going to do anything. So you have to take out that part of the selector. But if you do that then you'll target every div.price on the page, which may or may not be acceptable. I assumed not. Which means that to avoid removing things you don't want to remove, you have to tell jQuery exactly what you did want to remove: the price inputs inside the modal. Thus your final code should/could be $('div#add-edit-product div.price:not(:first)').remove();
  5. Sure it does. You just said it was working, didn't you? Also, $(selector).find(selector) is wasteful. Just do one $(selector selector).
  6. Are you sure they're visible? You can see them on the page? Your selector is finding every single visible div.price on the page. I'm saying, find the div.price inside the modal so that way you don't even have to care whether they're visible.
  7. Riddle me this: at the moment that code is running, what visible "price" inputs are there? If you want to remove prices from the modal then remove prices from the modal. As in literally, find the prices in the modal's markup and remove them.
  8. There are three things about this thread that bother me: 1. You still haven't asked a specific question. As in, written a sentence that ends in a question mark. You've said things about algorithms and papers and Euclidean this and Euclidean that, but never asked a question. 2. "Euclidean distance" is a highly Google-able phrase that leads to a very simple (you probably already know what it is, even if you aren't aware of it yet) equation. 3. You're reading through a paper that involves... well, it's not that it has a lot of math in it, but that it's not casual reading material. Honestly, a lot of it is quite obvious if you give it a minute - what's "new" is the concept of using multiple measurements as a way of reducing errors. It's basically statistical regression. So how about you do everyone a favor and ask a specific question that demonstrates either (a) you do not have the necessary background information about how the math is supposed to work, and are looking for an explanation of it, or (b) you do have the necessary background information and are having a hard time with one or more specific aspects of translating that information into code. Above all, I want to see a sentence with a question mark. Bonus points for stating what Euclidean distance is, and more bonus points for posting the code you've written so far.
  9. Not sure how the QR code is supposed to help, but if you want to determine approximate location based on signal strengths, convert those signal strengths into distances from the AP (it's not enough to know -67 dBm but you have to know where that measurement happened), then apply standard triangulation math (which also requires knowing the location of the APs themselves). In other words, get some real world numbers, do the math on paper until you get the right answers, then translate that math into code.
  10. The Euclidean distance formula is simple, but with logarithmic scales it'll be weird. What you haven't done yet is give a description of what you want to do. Saying "I have these numbers and I want to use the 'Euclidean Distance Algorithm' with them" doesn't actually say anything. What are you trying to get out of this? Why are you calculating a "distance" with field strength measurements?
  11. And what's the question?
  12. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort
  13. If the goal is simply to support *s then fnmatch can do that.
  14. Has anyone run into an issue where they created the same dropdowns as you did, have them pop up a modal like you did, and stop working like yours did? Maybe. Post your code.
  15. "Removing" a time is another way of saying you don't want to show the time. How are you showing available reservation times to the user?
  16. If %s work for some reason then maybe your first attempt didn't work because you were looking for "FA" in [PART NUMBER] instead of [CATALOGUE_NUMBER_BOM]?
  17. You have an asterisk, yes, but what about second asterisk?
  18. I don't know what's going on. But I do know <input type="hidden" id="hidetext" value="{php:function( 'SobiPro::Txt', 'CATEGORIES_HIDE' )}"/> that won't work.
  19. Does the XSLT include xmlns:php="http://php.net/xsl" or does it use a namespace-alias?
  20. You agree that... you're looking at the wrong code? Not to your original problem, but you should fix it anyways.
  21. "function function not found" suggests XSLT that looks like select="php:function('function', ...)" Are you sure you are looking at the right code?
  22. You are doing a redirect. You cannot use $_POST after a redirect. That's the rule. Remove the redirect and do whatever logically follows from that.
  23. I don't understand what your post is supposed to mean. Isn't that the same code as before? My reply is the same: you can't use $_POST after a redirect so put the message on the same page instead of redirecting.
  24. The $_POST data is only good for the page where it was submitted to. Any page you redirect to after that will not be able to see it. If you want to output a message then do it on the page the form submitted to. Don't use a redirect for it.
  25. Don't lie on your next job application and you won't have this problem again.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.