Jump to content

nILS

Frequent Writer
  • Posts

    4,314
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by nILS

  1. nILS

    *whack*

    Nope, its use got reduced by means of some bullshit language reform. Since "ß" is necessary to distinguish some words they couldn't completely drop it. For instance in a CAD drawing it could say "Masse der Zeichnung entnehmen" (= "take measurements/masses from the drawing") :D Bastards. They're trying to ruin german.
  2. nILS

    *whack*

    there's no real equivalent to "likey". But you could go with "Ich mag bable-fish".
  3. nILS

    *whack*

    Wow. This actually correct. Even the case is chosen correctly. I'm amazed. Um, this is not quite as correct. The word "like" didn't translate as the verb "to like" but as "jimp is like bugfight"
  4. "They are not pulls" is correct. "Pulls" is the plural of the noun "pull". See: http://www.askoxford.com/concise_oed/pull?view=uk
  5. nILS

    Midibox LC

    Musst Du nicht, scheint aber sinnvoll. ;-)
  6. xarolium: Don't be offended by me stating my point of view. I'm not attacking you in any, I'm just saying I don't really like that type of behaviour. If you were to introduce a new idea in the programming section and I'd say I don't like the approach you wouldn't be offended either, would you? EDIT: Besides: Selling the samples on ebay violates the terms and conditions of microchip and is hence illegal.
  7. Hooray! Email sent :D
  8. I don't care *who* paid for the parts, as long as someone did... ;-) I just don't like the overall concept of sampling parts and then trading (=selling) them.
  9. Not trying to imply anything here, but that kinda sounds like "I sampled a bunch of stuff and would like other things that would actually cost me money for it"
  10. [OT-mode]1111 posts :D Hooray for Wilba![/OT-mode]
  11. Selling parts is usually not a big deal ;-) Especially if you sell them for what you paid for.
  12. Nope, bugfight's source does not take care of that. It simply and elegantly toggles though the Banksticks. I'd probably leave the generic solution with bankstick detection to some coding guru and go with a simple solution that works "just" for you :D
  13. another problem - the way you're going about it, checking the number of banksticks wouldn't help since there could only be banksticks 1,3 and 8 in the system. But honestly, I don't see the point in chaning banksticks on the fly. 8 should be enoughm don't you think?
  14. Um, well that doesn't change anything about what I've written...
  15. You need to store the actually selected bankstick number somewhere. If the up button is pressed check if the number equals [numberOfBanksticks]. If so set it to 0 else add 1 to it. Call NotifyBankChange. If the down button is pressed check if the selected one is 0. If so set it to [numberOfBanksticks-1] else subtract 1 from it. Call NotifyBankChange. Done. :D
  16. The button matrix has *nothing* to do with the DOUTs. I assume you got lost as the diodes were mentioned. You need a diode (not LED) on every button to make allow for the matrix to work. I wouldn't worry about the programming just yet - if sending the events and keeping the LEDs lit until the sample is done is all your application needs to do, it's not a big deal. TK provided us with an excellent skeleton application for that =)
  17. nILS

    thanks TwinX

    chat's up. It's a Java IRC client. Can be found at: irc.everywherechat.com (6667)
  18. seppo was just incredibly happy and flooded the channel with smileys ;-)
  19. nILS

    thanks TwinX

    A big "thank you" from my side as well!
  20. nILS

    *whack*

    stryd_one: That's the topic: *whack*. As in "*whack* Dammit, I touched a live wire". Any more questions? ;-)
  21. Welcome aboard glennv! Yes ;-) You can actually have (almost) any number of layers you wish to have. You do not have to give up buttons for that matter. Your buttons will be connected to DIN modules. A single DIN4x module can handle 32 individual inputs - if you go with a button matrix, your 8x8 buttons will need 16 inputs leaving you with 16 open inputs. I don't know a lot about the Midibox64 source code, but a simple "send data when a button is pressed" app isn't much work when you start with the skeleton application, which already does most of what you need. I don't think you'll need to worry about banksticks unless you wish to have some buttons active in different layers at the same time. Personal opinion: What do you need the 8x8 LEDs for? I'd go with your 8x8 button matrix and add an "up" and a "down" button or a rotary encoder to switch through the different layers. And of course a 7-segment LED display (or some LEDs) to display the actually selected layer. (kinda like in the attachment). Cheerio, nILS
  22. nILS

    *whack*

    Germany: 60V DC
  23. Most of the answer is already given in the thread you posted ;-) You want to add the additional buttons in cs_menu_io_tables.inc and program the functionality in cs_menu_buttons.inc.
  24. A full CS is awesome though ;-)
  25. Man you should have seen seppo in the chat after TK posted this :D Awesome work, seppo!
×
×
  • Create New...