Windows 7, Paint, and the Snipping Tool

[amused]

Alt & Printscr

then flip to paint.

then ctrl & V (which is the same as clicking paste).

This pops the image onto the paint screen, ready for you to manipulate.

I've always used this and it still works for me in Windows 7. The ability to accurately capture just the active window with a simple key command is very useful - and if you need to do any further cropping, paint is good for that.

I guess what confuzzled it a bit is that on this new laptop they combined the 'Insert' and 'PrtScr' functions into one button, so you have to press the (new to me) Fn button instead of Alt. I see now that the entire top row of buttons have two functions, one above the other, so this is their way of creating a distinct way to access the bottom function.

[Gawdzilla Sama]

That's new for the 1998 model year.

[amused]

The last time I was using just a laptop with the smaller keyboard, it was a 484 processor.

[klr]

The last time I was using just a laptop with the smaller keyboard, it was a 484 processor.

The little-known cut-down version of the 486.

[amused]

The last time I was using just a laptop with the smaller keyboard, it was a 484 processor.

The little-known cut-down version of the 486.

Oh yeah, I knew it was a number in there somewhere.

[rasetsu]

I use the cut & paste method because I do my editing in photoshop. Alas, the clipboard routines in my old PS6 are bonked, so I have to save an intermediary. It's got to end up in shop anyway, though.


Speaking of which, the keyboard on this Asus EEE is less than was on the Acer Aspire. Though with 10 hours battery life instead of 3, I won't end up at a lecture with dead batteries as likely as I used to do.

I can't remember whether I threw out the last of my 486 systems last year or not. I think so. Lowest I go now are I've got some slot 1 beasts left, including a dual P3-500 I may reintroduce to service.

[klr]

Agh! I'm having flashbacks to the days of the twin floppy machines.

And even further back to PCs with cassette drives FFS.

Cutting and pasting with those was quite a different matter.

[amused]

I use the cut & paste method because I do my editing in photoshop. Alas, the clipboard routines in my old PS6 are bonked, so I have to save an intermediary. It's got to end up in shop anyway, though.

Speaking of which, the keyboard on this Asus EEE is less than was on the Acer Aspire. Though with 10 hours battery life instead of 3, I won't end up at a lecture with dead batteries as likely as I used to do.

I can't remember whether I threw out the last of my 486 systems last year or not. I think so. Lowest I go now are I've got some slot 1 beasts left, including a dual P3-500 I may reintroduce to service.

Yeah, now that I have Photoshop and the snipping tool, I'm getting used to that more than Paint. I need to know Photoshop for the work I'm chasing so it's good practice to use it and to try to do new things in it each time.

Agh! I'm having flashbacks to the days of the twin floppy machines.

And even further back to PCs with cassette drives FFS.

Cutting and pasting with those was quite a different matter.

My very first computer was an Osborne 2, with two 5 1/4" floppy drives. One disk could hold about six pages of text.

[rasetsu]

The year was 1984. One of the first PC Clones. And for $4,000, it came with one, single-sided floppy, 128 KB of memory, MS-DOS 1.0 or 1.1, and a zooming 4.77 Mhz Intel 8088 microprocessor.

I bought Turbo Pascal 1.0 and the DeSmet C compiler package to round out the options.

[Gawdzilla Sama]

Without that spreadsheet program they might still be in the University basements.

[rasetsu]

Without that spreadsheet program they might still be in the University basements.

Actually, I think games and the Apple II, and event driven programming are just as important.

Games, much like porn for VHS tapes, sell hardware. And the Apple II was the first true home computer, thanks to the elegant and cheap engineering of Woz.
(Though not much more; things like the p-system for programmers required expensive memory card add-ons.)

And while the IBM PC's interface was clumsy and computationally inelegant and resource unfriendly, the MacIntosh was user and programmer friendly.


That all changed with the MacIntosh which was event driven and had a graphical user interface.

Event driven programming allows for the development of complex, graphical interface programs relatively simply and quickly, as opposed to traditional polling or interrupt trapping. I have one of the last (had) toolkits for doing windowed development on the IBM PC when DOS was still the standard, and it was a royal clusterfuck. IBM PC didn't see comparable interface design until Windows 3.1 in 1992 (which, IIRC, added true type fonts over 3.0 and networking in 3.11 Wfwg) and Windows NT 3.51 an 4.0 in 1995/1996.

Wikipedia states that the MacIntosh was not a descendant of the Apple Lisa, which was a similar graphical interface product. This is not strictly true. The Lisa's operating system was coded almost completely in Pascal (this was the time for Wirth's 15 minutes of fame), and the MacIntosh project borrowed heavily on the code from the Lisa project, taking what high level code it could use, and taking the most common routines and recoding them in 68000 assembler. It was likely this latter effort which meant the most for the success of the MacIntosh, as while the Motorola 68000 is and was a powerful microprocessor for the time, the rather inefficient high level code of the Lisa meant that the interface was not as snappy, nor as powerful for the programmer as that of the MacIntosh. (I considered buying a Lisa and I adored the machine. Unfortunately they wanted $8,000 for it and I couldn't get them to shave a penny off it.)

(Minor story and a favorite bit of lore. When I started BBSing in '86, there were still plenty of Apple II's still in service, and most didn't do lower case. So for Citadel, my primary BBS software, there was a filter which would recognize all caps and convert it to proper capitalization. I don't know how it got the name, but it stuck: it was the bunny filter. I imagine the code is still around and could be adapted to atheist forums for reformatting the angry posts of Theists and Creationists.)

[rasetsu]

Question: When you drag and drop something, where does the collection of objects or references go during the transfer, to the clipboard without displacing the current contents, or some other data structure?

[klr]

Question: When you drag and drop something, where does the collection of objects or references go during the transfer, to the clipboard without displacing the current contents, or some other data structure?

There's only one way to find out.

Be right back.

[klr]

Test in Windows XP SP3:

Copy some text, placing it into the clipboard
Test pasting it into a text editor: works
Drag and drop a file in Windows Explorer
Repeat above paste: still works

Now, cut and paste a file, as opposed to a straight drag and drop
Repeat above paste: no longer works

Interesting

[pErvinalia]

you can get clipboard apps where you can store multiple things in the clipboard if you need.