Return from an offline sojourn

I was offline for a few days over the past fortnight, and found it really refreshing. Without the continual distraction of the internet I was able to concentrate on achieving a lot of things that had been niggling me for a while.

Amongst those was the addition of some long overdue 'luxury features' for TimeSnapper that I hope will make it more meaningful for a lot of users. (No doubt I'll bombard you with the details when we release the next upgrade).

With the internet out of the way, my 'at home' productivity went from its usually mid-40's mark to a whopping 98%.

There were a lot of blog entries I jotted down notes for, but now I'm just happy not to contribute too much to the hyper-noise of the internet for one more day ;-).

But here's an example of an 'awesome Atli tooltip' found deep inside the codebase for TimeSnapper.

        Me.Label4.Text = "Productive Applications:"
        Me.ToolTip1.SetToolTip(Me.Label4, "Productive Applications are those that relate to your work." & vbCrLf & _
                                          "Solitaire, for example, is NOT a productive application, " & vbCrLf & _
                                          "unless you are working on becoming the world champion of " & vbCrLf & _
                                          "solitaire.")

It's these kind of gems that help me enjoy work on this product more and more with every version.

Now, back to the usual un-productive fare:

If you too have been tricked into using twitter, you can follow me here.

(feeling like an idiot now)

atli tells me that the code above wasn't his, it was mine.

so i'm essentially laughing at my own code.

i need to get out more.

Consider it one of the benefits of having a poor memory :) It's even better when your boss asks you to implement a feature and then, when you go to look at the code, you realise that by some Nostradamian fluke you had already built it, not told anyone about it, then forgetten that you had done it. Job done dude!

@James Brett -- i was waiting for someone to say that.

Unless there are events handled for a control, i don't believe in renaming it.

'i was waiting for someone to say that'

So I'll throw in the other comment that you may have been expecting and ask why you aren't using either a StringBuilder or String.Format...?

;o)

C

@Carl:

StringBuilder for constructing static strings together? Format when there's no formatting occuring?

Both would be less efficient than the current code.

The "efficient" way to do it would be use String.Concat --

and the current code is probably statically compiled into a string.concat under the covers.

so it would be a false optimisation.

also -- this code occurs in the designer controlled part of the form, so i'm loathe to touch it generally.

the real question i was expecting was..... VB!?

You're right of course... I guess I was far too busy trying not to berate you for the choice of language...

I guess I really just don't like seeing those ugly vbCrLf things everywhere...

Return from an offline sojourn

NimbleText is a Powerful FREE Tool

Articles

Twitter, baby

Recommended Reading

Recommended blogs

Aggregated Links

Human Link Machines