Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
  You are not logged in 
The Multi Drawer V1.1   [1990]

The Multi Drawer V1.1 Released by :
Silver Dream !

Release Date :
January 1990

Type :
C64 Tool

User rating:awaiting 5 votes (5 left)

Credits :
Code .... Silver Dream ! of W.F.M.H.
Graphics .... Silver Dream ! of W.F.M.H.
Concept .... Silver Dream ! of W.F.M.H.

Download :
http://csdb.dk/getinternalfile.php/18135/Multi_Driver_v1.1_SILVER-DREAM.zip (downloads: 313)

Look for downloads on external sites:
 Pokefinder.org


Trivia Info
Submitted by Silver Dream ! on 3 December 2012
One day Polonus came to my place, while I was coding this tool. Or rather something that was eventually to become the tool we talk about. I showed him how fast I can draw basic shapes as well as my "innovative" function called "rays" and triangles and patterns, and zoom, and.. well it still crashed every here and there and of course froze somewhere during the demonstration. Of course he entered an unrecoverable state when moving the mouse much faster than I normally did, etc. but despite all those problems he was still drawing and erasing furiously various shapes on my screen, converting them back and forth.. After a few minutes of this, he rose from the chair and said "I go home". "Why? Why so fast?" I asked him. "Because I need to write something good too!" And so he went. And so "Voicetracker" was born...
Trivia Info
Submitted by Silver Dream ! on 3 December 2012
There is a zoom function, which allows easy pixel-by-pixel editing. When I wrote the first zoom routines I went proudly to show-off. I showed the new version to my artist who actually requested the zoom function, expecting a lot of applause and congratulations. What I got was: "What is that? How am I supposed to work with it when it is so damned slow? Should I go and make coffee, every time I click the magnifying glass function?" Well, it was (IMHO ;-) not /that/ bad and slow. I mean: it was slow (about six or seven seconds to redraw the whole screen) but it was there and worked! I thought I deserved at least some credit.. OK - I went optimising. In a day or two (don't remember now) I delivered the second, noticeably optimised version.. still too slow for the artist. I went optimising further, went through all the routines counting and shaving cycles wherever I could. The result was awesome optimisation: about 100% faster than the first approach. Guess what? Yes.. TOO SLOW!! This time I had enough! I went on strike and said "You don't know a s**t about programming so don't tell me to make it any faster. I went through and optimised everything. Those routines are as fast as it gets! It is twice as fast as the first one you received. We don't have enough memory available to unroll the loops.. what? Ah, you don't know what loops are... OK, never mind. just learn to work with what you have now because you won't get any faster version, period!"

Yeah... So much for any recognition for all my efforts and my "brilliant' zoom function... :-(

Then I went back home. In the evening I went to bed still thinking and reliving the injustice I experienced. I couldn't fall asleep and started to think about my zooming routines and how they can't be optimised any further.. about 02:30 am I smashed my forehead with open palm, jumped out of the bed, ran to the computer and within 15-20 minutes I had a completely rewritten zoom function, which used about half of the memory the original needed and.. and was some over three times faster than the most optimised and cycle counted version I had before! Miracle? Well... during the night contemplations I realised that I took completely unnecessarily a rather "suboptimal" approach. When zooming I analysed and zoomed every pixel in the zoom range. That meant bit fiddling to extract the pixels one by one from the screen bitmap. What for? Actually I was doing this because I simply didn't realise initially that I can easily zoom by full bitmap bytes rather than by one pixel at a time! Once I realised this, I cut out all the bit extracting operations, three fourths of the zooming and ended up with both smaller and much faster code that eventually earned me the praise from the artist ;-)
Trivia Info
Submitted by Silver Dream ! on 3 December 2012
I used all the memory up to the proverbial last bit (with some little exceptions in zero page ;-) and even had to start shortening the strings (text displayed on screen). Although today I'd say I still see some room to be gained by cutting out excessive - to my current taste - babbling ;-)
Search CSDb
Advanced
Navigate
Prev - Random - Next
Detailed Info
· Summaries
· User Comments (4)
· Production Notes (3)
Fun Stuff
· Goofs (1)
· Hidden Parts (2)
· Trivia (3)
Forum
· Discuss this release
Sponsored links
Support CSDb
Help keep CSDb running:



Funding status:




About this site:
CSDb (Commodore 64 Scene Database) is a website which goal is to gather as much information and material about the scene around the commodore 64 computer - the worlds most popular home computer throughout time. Here you can find almost anything which was ever made for the commodore 64, and more is being added every day. As this website is scene related, you can mostly find demos, music and graphics made by the people who made the scene (the sceners), but you can also find a lot of the old classic games here. Try out the search box in the top right corner, or check out the CSDb main page for the latest additions.
Home - Disclaimer
Copyright © No Name 2001-2019
Page generated in: 0.089 sec.