Jump to content
Flirc Forums

jason

Administrators
  • Posts

    3,757
  • Joined

  • Last visited

  • Days Won

    231

Posts posted by jason

  1. Unfortunately, no. I may figure out a way to store the uncompressed versions somewhere, but think of my method right now as a one way compression. It wasn't done to protect anything, just merely a way to get the data and store it on the device's 'eeprom' which you are actually dumping when you save and load your configuration. I will have something to make that file human readable in a future release.

  2. Hey Mick -

    Got your mail and will reply shortly.

    Yes, postage kills me. In order for me to do anything cheaper, it requires a lot of filling out forms by hand, which I can't do. I already spend the majority of my free time filling orders, I literally have zero time for development right now. The beauty of the postage box I chose, is what you mentioned, I can stick about 10 in there and the cost stays exactly the same whereas another method will rise with weight.

    All this being said, I have found another option which is first class, it will be $3-5. I couldn't explore this previously because of all the work I had to do by hand, however, I found a module for the e-commerce store I use (lemonstand), called shipstation. They support batch printing first class labels, I expect to have this on the store within a couple weeks. However, shipping times will probably be 8 weeks and it's not ideal. As you mentioned in your mail, distribution will be the best method for customers.

    Thanks for posting this.

  3. Hey Amnesiac -

    I actually don't use the traditional method, so unfortunately any database we build in the flirc community wont be consistent with anyone else's.

    That's not because I wanted to be proprietary, and a jerk, it's because I came up with a way to ignore protocols and compress the long datastream. Which is also why you can store buttons on the device, and it doesn't require a large memory chip.

    Does that make sense?

  4. Hey, I'm so sorry for my delay.

    The windows key is a modifier key. I never imagined on anyone wanting to hit modifier keys by themselves. If you want to do this, you can do this with the commandline. In windows, the commandline is located in the Flirc installation directory. You'll have to open up the commandline utility.

    Here is the command that you want:

    flirc record_api 8 0

    • Like 1
  5. I've realized I've become one of those dreaded developers that keeps promising and doesn't deliver. I'm apologizing for dropping the ball. I've spent most of my time trying to get in more inventory and better the process at which orders get managed, fulfilled, and units are tested. I spend 90% of my free time in stupid logistics right now, not giving me any time for development. We have done work, but not nearly at an acceptable level.

    I'm going to be getting back to this, please give me about 3-4 weeks.

    Again, I'm so sorry guys. As much help as I get from the other people involved, it really is just only me.

  6. This is on my list of things to do, it's going to require a bit of a firmware overhaul, but I want to fix this scrolling. I understand what you are saying, and I agree, I'm not happy with the current implementation as it's a general purpose model that may not be that great for every remote.

  7. Yeah, we're going to fix that. GUI development has been a bit slow, but we're definitely working on it. We're working out a way to highlight the buttons when you press keys to help show if you've programmed them, but here is what is done so far:

    * tooltips on mouseover

    * 'go' button will only be visible on minimalist

    * Go back/home buttons fixed

    * removed outline for eject key

    We'll definitely have more in the next release.

    It's not a lot, but

×
×
  • Create New...