DSP Robotics Support

tulamide wrote:The properties were not correct, though. Maybe it was on purpose,

Yeh it was..when i loaded i didn't get result...so mucked around about till i did.
Will remove that fsm to avoid any confusion with your original work..
I'll just up the final bitmap when done..
thanks for correcting fsm

Awesome, billv! Thank you very, very much for your work!

tulamide wrote:Thank you very, very much for your work!

Forget it!..

tulamide wrote: (A-Z, a-z, 0-9, the most used special signs, and if possible the german umlauts äÄöÖüÜ).

A-Z is done, a-z, 0-9 and "most used special signs" is do-able.
german umlauts äÄöÖüÜ....havn't looked at this one yet...

Note: Clickteam released a FREE edition of Fusion a while back.
So if I cant finish the german stage, it makes sense that someone else could download
a free edition, and continue the bitmap...
http://www.clickteam.com/clickteam-fusi ... ee-edition

Un-fortunately, i didn't get far...definatly not a "pixel" artist...
My lower case and special char look crap so pointless to continue..
A simple a..z in Capitols is all i could do...may it be usefull somewhere.. 1x26 A..Z

Thanks for trying to help, billv!

I think I'm gonna take a font from font squirrel and convert it somehow to monospaced bitmaps. It might delay the next version of SFE a bit, but that could actually be a good thing, as it offers me to ask around here if someone knows a solution to this:

Who would have thought that something as easy as deleting a bitmap turns out to be the biggest issue I've ever had? It seems you can't delete a bitmap in green (if I didn't miss something). Once loaded it stays in memory until exiting the app/vst. In Ruby I can easily delete a bitmap, but on the other hand I can't get it to store the bitmap. Would need to use green therefore which brings me back to point 1

In order to make the module chainable, I need to delete bitmaps from memory, when chaining is active. Else it doesn't make sense to chain, if all modules additionally keep their once assigned bitmaps. Any thoughts? I could do 2 seperate modules, but that would also mean double the amount of work maintaining and updating the underlying Ruby code. So I would like to avoid that.

tulamide wrote: can't get it to store the bitmap

.remember 3.06 Pebble brought us ....
"New Bitmaps are now stored at Ruby component inputs
and bitmaps stored at outputs are now saved with the schematic"

got to be some sort of trick you can employ to take advantage of this new autosave feature..

New version!

Sprite Font Engine r2

changelog:

• new: line spacing (adds to/subtracts from the minimum line height, in pixels)
  new: interpolation mode "default", the mode that is used by Ruby for scaled drawings (bilinear)
  new: transparency, 0-255, sets the font to somewhere between fully transparent (0) and opaque (255)
  new: added module description
  new: kerning list (currently implemented as an offset from the chars' left position including transparent border), this list needs to have at least as many comma seperated values as there are chars in the font!
  changed: rearranged properties for a better value management
  changed: "interpolation mode" renamed to "interpolation"
  changed: interpolation mode "soft" renamed to "smooth"
  changed: button "load sprite font sheet" renamed to "import"
  changed: "whitespace kerning" renamed to "whitespace"

Download from first post. Remember to report issues and make feature requests.

billv wrote:

tulamide wrote: can't get it to store the bitmap

.remember 3.06 Pebble brought us ....
"New Bitmaps are now stored at Ruby component inputs
and bitmaps stored at outputs are now saved with the schematic"

got to be some sort of trick you can employ to take advantage of this new autosave feature..

I will remember this. Thank you for the reminder. For now, chaining is postponed.

A sneak preview of what's coming next...

Soon...

sneak_preview_2.png

tulamide wrote:Soon...

sneak_preview_2.png

Very nice