Welcome to the Lounge

kmoorevs2-Jan-17 9:27

kmoorevs

2-Jan-17 9:27

My Dad and I were talking about this on my Christmas visit. Does anyone remember 'After Dark'? My wife doesn't get the 'bad dog!' reference. Laugh | :laugh:

"Go forth into the source" - Neal Morse

OriginalGriff2-Jan-17 10:05

2-Jan-17 10:05

Flying toasters! Control the "doneness" of the toast! Laugh | :laugh:

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

dandy722-Jan-17 11:01

dandy72

2-Jan-17 11:01

A buddy of mine had After Dark's Star Trek screen saver...I've probably wasted way too much time just watching it.

Mark_Wallace2-Jan-17 14:07

2-Jan-17 14:07

It annoys me, actually. I mean, I know that only CRTs needed "saving", but I enjoyed many of the SCRs that I've used, but when you're always working on laptops, "how much power have I got left" is the issue, rather than screen burn.

Strangely, the one I miss the most is ajscreensaver, which was just a clock (in whatever format I felt like seeing).

Simple things please simple minds, I suppose.

I wanna be a eunuchs developer! Pass me a bread knife!

Deepak Vasudevan2-Jan-17 20:20

Deepak Vasudevan

2-Jan-17 20:20

More simpler solution is Lock the screen (CTRL +ALT+ DELETE and Lock) and switch off the monitor.

AAC Tech3-Jan-17 10:57

AAC Tech

3-Jan-17 10:57

Just to set the record straight. All monitors can suffer "screen burn" given enough time. I have seen examples on both types of monitors with my own eyes. It is usually log in or data base entry screens.

Were they "old"? Yes. If you use the same monitor for many years it could happen.

I wouldn't overly worry about it. it is up to you.

Time warp

Jochen Arndt2-Jan-17 0:35

Jochen Arndt

2-Jan-17 0:35

Has anyone else noticed that the Latest News head lines on the CP start page are tagged with "Tue 3 Jan 2017"?

OriginalGriff2-Jan-17 0:51

2-Jan-17 0:51

Well, if it was "Sun 1 Jan 2017" it's be "Latest Olds" instead.

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

Mark_Wallace2-Jan-17 2:17

2-Jan-17 2:17

So tomorrow we can do it again[^]

I wanna be a eunuchs developer! Pass me a bread knife!

lopatir2-Jan-17 3:32

lopatir

2-Jan-17 3:32

Perfectly correct, depending where you live.
Europe's about 12 hours) behind the leaders.
USA are aumong the last to get there.

Sin tack ear lol
Pressing the any key may be continuate

MacSpudster2-Jan-17 3:45

MacSpudster

2-Jan-17 3:45

Ah, but the last shall be first!

Jochen Arndt2-Jan-17 4:14

Jochen Arndt

2-Jan-17 4:14

See my profile: Germany at UTC+1.
Posted at 12:30 local time = 11:30 UTC.
So it was only Tuesday then where time is +13 or +14 ahead like Christmas Island and Tonga Big Grin | :-D

lopatir2-Jan-17 5:30

lopatir

2-Jan-17 5:30

Or New Zealand and a few other nearby islands which is +12 and +1 for daylight saving.

Sin tack ear lol
Pressing the any key may be continuate

Dilbert OTD

OriginalGriff1-Jan-17 20:32

1-Jan-17 20:32

Programming Environment[^]
Been there, done that ... and I'm sure you all have as well! Laugh | :laugh:

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

pkfox1-Jan-17 20:43

pkfox

1-Jan-17 20:43

Aren't we arrogant ? Poke tongue | ;-P

We can’t stop here, this is bat country - Hunter S Thompson RIP

OriginalGriff1-Jan-17 21:36

1-Jan-17 21:36

Hah! Takes me a couple of hours to setup Paintshop Pro each time I upgrade... Laugh | :laugh:

Mind you, a lot of the blame there lies with Corel: They never consider where you had tool windows in the previous version. And when I think about it, Microsoft are just as arrogant with VS ... that takes far too long to get right as well. Mad | :mad:

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

Mark_Wallace1-Jan-17 22:12

1-Jan-17 22:12

OriginalGriff wrote:
Takes me a couple of hours to setup Paintshop Pro each time I upgrade

I know a trick for that, if you're happy with opening the registry.

What you do is:

0. Insert the corel upgrade-installation disc

1. Open the registry editor (winkey+R, "regedit")

2. Take the corel upgrade-installation disc out and bin it.

3. Close the registry editor.

Works perfectly for me, every time.

I wanna be a eunuchs developer! Pass me a bread knife!

OriginalGriff1-Jan-17 22:14

1-Jan-17 22:14

What is this "disc" thing of which you speak? Laugh | :laugh:

I joined the twenty-first century some years ago and download upgrades.

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

Mark_Wallace1-Jan-17 22:18

1-Jan-17 22:18

Ah, but that makes it more complicated, because in place of item 2, you have to:

2a. Locate and download a file shredder, which overwrites all bytes with zeros at least twice

2b. Install the file shredder

2c. Run the file shredder on all corel upgrade-installation files

Things were much simpler, in the old days.

I wanna be a eunuchs developer! Pass me a bread knife!

dandy722-Jan-17 2:36

dandy72

2-Jan-17 2:36

OriginalGriff wrote:
Microsoft are just as arrogant with VS ... that takes far too long to get right as well.

Just about every setting in VS is exportable to a file than can then be imported into another machine or into a newer version. I've been using such files since VS2008 and it's still saving me a lot of time getting my editor, code formatting, window layout preferences and such every time I set up a new development VM.

Better yet, you can export/import subsets of such settings - one file strictly for window layouts, another for code formatting settings, etc.

Or are you talking about something else altogether?

OriginalGriff2-Jan-17 2:46

2-Jan-17 2:46

No, exactly that - but I didn't know you could do that. And if you can, then why the elephant doesn't MS do exactly that automatically when you install a new version? That's actually more annoying than not having the facility at all!

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

Mark_Wallace2-Jan-17 3:11

2-Jan-17 3:11

The trouble with importing settings for any ms app is that they often decide that things have to work differently, so you end up with things freezing, giving unexpected results (which you may or may not notice), and shouting "Warning, Will Robinson! Warning! Warning!" for no apparent reason.

I wanna be a eunuchs developer! Pass me a bread knife!

OriginalGriff2-Jan-17 3:22

2-Jan-17 3:22

If Microsoft software did shout "Warning, Will Robinson! Warning! Warning!" at least we'd get some warning it was about to scramble your files and play a game of scrabble with the results... Sigh | :sigh:

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

dandy722-Jan-17 3:27

dandy72

2-Jan-17 3:27

YMMV then. All I know is that I first created 3 or 4 separate settings files to group them logically, and reused the same files in VS2008, 2010, 2012, 2013 and 2015. As far as I can tell, they never caused freezes or even warnings (and even if they did, the import process is a one-time operation).

I get far more problems using versions of VS that were upgraded in-place (something I've stopped doing altogether), than just bringing these exported settings files (which ultimately are just XML if I recall correctly) on new clean dev VMs whenever a new version of VS comes out.