Jump to content

crelf

Members
  • Posts

    5,759
  • Joined

  • Last visited

  • Days Won

    55

Everything posted by crelf

  1. :arrow: Flameware taken offline
  2. It's a forum - by definition your post is seen by many, so insisting that only one person is permitted to post replies to your post is a real quick way to piss people off.
  3. I certainly would appreciate any advice you can give. It's a team effort (we're running it as an internal project - just had the "customer" kick-off meeting a few weeks ago) and my part is (of course) the software. That said, any advice on all the components will be very-much apreciated. We're (sort of) following this guy's plans (but hopefully a little more professional since we have a fully-capable build shop on site ), but with a different control layout (probably this one - there's a populated photo here) and bigger screen (did you use CRT or LCD? how did you handle odd resolutions?) Yup - that's the plan, plus it'll display random messages about the ROMs that are installed, etc...
  4. Isn't that the same thing?
  5. That's a really important point - none of us here know everything, and too many of us are scared to post if we're not quite sure - knowledge comes through collective intelligence and constructive thinking - we a stronger united! Viva la revolution!
  6. crelf

    nEwbie intro

  7. This is truly AWESOME! I've been looking for menu software for MAME for a few weeks (we're building one here at work - another great incentive to join VI Engineering!) and had settled on MAMEwah or writing my own (actually, I'll still have to write some code as we've got a scrolling LED display that we're going to integrate to show high scores, etc), but GAMEX looks like the perfect alternative - much slicker than MAMEwah! Thanks Mike! :thumbup:
  8. I've gotta agree - there are plenty of half-arsed SQL abstractions out there, but unless you know some basic SQL then you're not going to get anywhere. In all seriousness, you only need to know a handfull of SQL statements to get up and running, and if your database admin uses stored proceedures then it's even easier! Check out this site - it gives you enough information to be dangerous
  9. Ah - I see. So I can script up a VI from a built exe, but I've got to do it through the LabVIEW developement environment. That's cool - for the "builder"-style applications I'm thinking of, I don't think I'd ever want to create a VI for someone unless they had LabVIEW installed anyway
  10. *sigh* I think it's time you got a hobby Stephen! So how does Vision Builder do it?
  11. We're not here to do it for you - we're here to help each other. If you've got an example of what you've already tried and what problems you're having, then we might be more inclined to help. Read this and this (most specifically, read this)
  12. There you go - you learn something new every day I had dreams of creating my own "thingy-builder"-style interface where my app (running as an exe) could be used to define a process, and then I could dynamically build the VIs required to do it - just like the old Vision Builder did... (or still does?)
  13. Really? I can't create, edit and save an external VI from a process in an exe?
  14. ...unless you script it Either way, I think a binary datalog file would be easier to impliment.
  15. That's just spooky!
  16. Hey Dan - my first response is "go binary!", but if you must stay ASCII, add a line to the end of the file that does some sort of checksum (I'm sure plenty of other LAVAites will suggest checksum algorithms) - then when your SW changes the file it can update the checksum, and whenever you read it you check the checksum and if it doesn't add up then display a "naughty naughty!" message to the user - something about the file being corrupt. You can go even further (depnding on the user smarts) and encrypt the checksum (I could go on and on and on)...
  17. That's just crazy enough to work!
  18. crelf

    Thanks!

    That's what we're here for Any chance on seeing the results of the survey so we could maybe flesh the comments out a little?
  19. That'd be a neat addition to the LAVA Code Repository!
  20. Don't forget to set the IRQ...
  21. Touch
  22. No offense intended, but the first "A" in "LAVA" stands for "Advanced" - you honestly will have better luck posting your question to the National Instruments Developer Zone Discussion Forums.
  23. Aussie Aussie Aussie!
  24. Who showed you my code?!?!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.