"once you'd gotten used to creating your presentations in PowerPoint, you wouldn't want to go back to not using it."
I know plenty of people who, even after learning how to use a better tool go back to the first one because it;s how they think. For example, someone in my home still uses a computer like it were running DOS. That is, I want ot open a word document, I first open Word. Same for Excel, open the app first as opposed to using the file system where you go to file you want and let the app open.
As for me, I still do most of my graphics with Windows Paint. When I need better drawing, I use the draw program that comes with OpenOffice.
I'd probably still use the OpenOffice draw program. It tracks yourmouse position and thus you can get quite accurate and repeatable drawings. I used it to design shelving in my house and to make room diagrams for placing furniture. You just ahd the translet thedistances on the drawing sinto physical distances but once I kniw the relationship, the rest was easy. It beat making paper mkodels of rooms and furniture, although that worked too.
@ Doug, Max - Yeah, I know, I was surprised too, but that's the way he's always done it...
I still remember doing prelim PCB floorplans by cutting out post-it notes to the same size as ICs and circuit block estimates, them arranging them on a paper until I got all the interconnections as short as possible. Don't laugh - it got the job done :>}
Sometimes, moving into the future drives you backwards. With many of the newer Microsoft Office applications, if you open a file directly, it is read-only and cannot be modified or saved. It is necessary to open Word / Excel first and then open the file. "Progress."
@MeasurementBlues - "As for me, I still do most of my graphics with Windows Paint. "
I thought I was the only one still using it! I'm glad I am in such illustrious company. MS Paint is, for most things, so easy to use. It's horses for courses, for example MS Paint cannot (as far as I know, correct me if I am wrong) do graduated fills, but for most diagrams it can do pretty well anything you need. I have a file of schematic symbols and have it open so I can copy and paste when I am doing schematics - for a small schematic it is very quick. MS Paint is also great for putting (eg) a quick red circle on a photo to indicate the bit you're describing, or to annotate photos with text. Simple it may be, but it's a great little program and I wouldn't be without it.
@David - I'm glad I am in such illustrious company.
From 2088 to 2011, I was the EDN Design Ideas editor (three of the longest years of my life). One prolific contributor in Eastern Europe would hand draw his schematics and scan them. It drove me crazy because they were hard to edit. I asked him about getting some kind of schematic drawing program, but no way. Finally I asked if you could use PowerPoint and the did. So, I make up a library of circuit symbols in PowerPoint and sent it to him. After that, his scematics were easier to read and consistent. He probably still uses it. Michael Dunn should thank me for that.
At that time, EDN was still in print and until 2010, we had someoen who did a beautiful job drawing schematics for the magazine. She you take anyting and turn it into EDN's style. We lost her when EDN was sold to Canon but she came back part time for a while under UBM.
@MB - resizing - I still have XP (yeah, I know, I'm a luddite :-) and you can resize in that with the Image \ Stretch and Skew. You just stretch by the same amount vertically and horizontally. Otherwise you get some very weird effects.....
For cropping I prefer MS Office picture manager - it's very easy, also for adjusting colour / brightness / contrast.
illustrious - adjective 1. well known, respected, and admired for past achievements.
Yes the tool seems to be very useful for software engineers who spend hours altogether finding the bug. SOmething like this will save them lot of time. Imagine the times when you got to work on a code written and by someone else and there is no documentation explaining the code.
"Memory leakage" and variables being written into unintended locations are common causes of programming problems. A debugging technique that I developed years ago was to surround my variables with some "0" buffer space. Viewing the memory on a display, I could see when data started to intrude into the white "snow" and attack my programming bug. It sounds like the Micriµm µC/Probe would be a powerful tool to monitor memory and provide an alert when variables overwrite program space or other variables.
I like printf(). As long as you have a fast compiler+linker and a fast way to download a new image to your prototype hardware, printf() can be very effective. For one thing, you can customize printfs to the specific problem at hand -- you are not limited to what the debug vendor has imagined that you might need. The printfs tell you what the program is doing and the program "practically debugs itself" :-)
You can use conditional compilation to "comment them out", so that when [sic] the bug comes back three revisions later, just enable your printfs and "Bob's your uncle".
Here's the rule I've heard (and try to apply): All time spent writing debug and diagnostic code pays for itself -- it's never wasted.
What a great rule. I need to make a bronze plaque and put that above my workbench. So many times I dive into debugging without really thinking of the data I need to really figure things out. probably need to get a deerstalker hat to wear while debugging too come to think of it...
LOL, I actually have a deerstalker! [For those who aren't familiar with the term, it's the type of hat worn by Sherlock Holmes.] If I have a particularly nasty problem that requires detective work, putting on the deerstalker puts me in the right frame of mind. OTOH, some problems require exploration. For those, I have a pith helmet.