# SPI Flash Analyzer and enhancements **URL:** \ **Category:** Extensions\ **Created:** [October 7, 2020, 6:32pm UTC](https://discuss.saleae.com/t/spi-flash-analyzer-and-enhancements/765 "2020-10-07T18:32:32Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![scott](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@scott](https://discuss.saleae.com/u/scott)\ **Post date:** [October 12, 2020, 6:05am UTC](https://discuss.saleae.com/t/spi-flash-analyzer-and-enhancements/765/3 "2020-10-12T06:05:04Z")
> [@markgarrison](#): > > You could fork one of these, or write your own. Ah! I’ve poked the low level API with the original Logic and didn’t realize it applied to V2 as well. I’ll take a look at modifying something next time I need it. 🙂 > [@markgarrison](#): > > Good catch. Any other types you would like to see? Not that I can think of at the moment. > [@markgarrison](#): > > This could probably just be built in. > In this case, would you prefer to have more features built into the NumberSetting class (e.g. float vs. integer, custom validator, etc)? My hope was that’d be automatic. I expect that I’d get a float if the number has a decimal, otherwise I’d get an int. Something like python’s `int()` parsing which handles prefixes like 0x iirc. > [@markgarrison](#): > > “format” is a [handlebars](https://handlebarsjs.com/guide/#simple-expressions) format string that’s passed the complete frame object that was returned by the decode function. Ok, awesome! That’s what I was wondering. > [@markgarrison](#): > > Thanks again for the feedback! I’m looking forward to making big improvements to this. No problem! I was really impressed with it overall. I thought the creation, testing and publishing was all really easy. Easy enough that I can see hacking together one-off analyzers as needed. 😃 --- _[View the full topic](https://discuss.saleae.com/t/spi-flash-analyzer-and-enhancements/765)._