I LOVE regions. If I really think about it though, it's more a side-effect of the regions than the regions themselves. I usually have a few main regions in my classes: private members, properties, constructors, methods, static methods etc. This has the wonderful direct effect of when I open one of my classes and I want to find property blah, I can pop open the properties region and it's there (I know I can use the drop-downs at the top of the code window but that's no fun!). It also has the, arguably, more useful side-effect of keeping all like-things together, so that when new people look at the code, it's much harder for them to put new properties at the bottom of the file instead of with the other properties. My logic here is, let's face it, most of us coders are "OCD" in the sense that we like order and symmetry and things like that, so putting a property outside of the properties region that's already defined makes you feel 'icky' and you want to move it. That's my 37 cents anyway...

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

Sounds like a good enough solution to me. You could either set the visibility of the picture box control to show/hide it, or replace the image with a "blank" one you already have - it all depends on the aesthetic you're going for. I would suggest pre-loading all the images (including the blank one) at startup and keeping them in memory (remembering to free them on close, GC may handle this for you, can't quite remember with images...). If you have a reasonable number of images, then this should be fine. Remember you'll only need one in-memory copy of the blank one although it may be used for all tiles. Another solution would be simply to draw something over the top of the images in order to hide them, for example a black rectangle or another image. This may be another solution worth looking into. Seems like you're on the right track though. Good luck!

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

modified on Wednesday, July 27, 2011 6:55 AM

_Maxxx_ wrote:

Most 7-8 year olds can spell Bum, Poo and Wee

Most 5-90 year olds still laugh at bum, poo and wee

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

Adopting a programmer's mindset, no sentence is complete without the word "should" :)

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

Small disposable cameras would be awesome fun, especially once the liquor began to flow. The last wedding I attended they did a similar thing and also had a chalkboard for guests to write a message on, then they would take a photo of them with the message then wipe the board. The happy couple didn't get a lot of the messages until their honeymoon when the photo album was ready, photos ordered chronologically... they started with messages like "We always knew!" and "Just married!" and ended with... well... nothing that needs to be repeated :) But very, very enjoyable for everyone.

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

And if I was Vishnu[^] I'd get more work done - 2 arms for work, 2 arms for CP...

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

It was probably our fault... I was standing on a 17 soapbox high soaptower

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

Mark Wallace wrote:

perhaps because I want to do it automatically

Well that's a given, I meant why would you do a full binary comparison when you can just check a flag instead?

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

Four - spectacles, testicles, wallet and watch. :)

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

I thought that this is what the archived attribute is for... can't you get the same effect with like a -M (or whatever) with xcopy? Why would you want to do full comparisons of files to see if they've changed when you can just look at the modified date or archived attributes?

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

See here[^].

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

5!

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

There are 4 people including myself who use my name at my workplace, in the same office. Each one is in a different department (I am a developer, one's an account manager, one's in F&A and another in sales and marketing). I will often get calls for the others, which can be interesting. "Aw mate, you coming for golf today?" --- "sorry, who is this?" "I've got Jane Doe from Bob's Legal Firm on the line, she wants to know why the products she ordered haven't arrived yet." --- "Ah... wrong person." "I AM NOT PAYING THIS??! WHERE DO YOU GET OFF ON CHARGING THAT MUCH, FOR A [PRODUCT]?? THIS OTHER COMPANY DOES IT FOR HALF THAT?! I WANT TO SPEAK TO YOUR PRICING MANAGER!" --- "Sure thing, I'll put you through..." (seriously, this call happened... paraphrased of course) Keeps my day interesting :) Calls for me are "I need report X from 2 days ago" and "production is down, fix it" and "I have this urgent item, due three days ago, can you do it four days ago???", you know, the usual...

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

A man of much wisdom, I believe he also said (in his capacity as a marriage counselor) "foolish man give wife grand piano; wise man give wife upright organ".

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

I think you were approaching this from a philosophical perspective, don't worry, I get you. Check this out[^], it's actually a big unanswered question in Western philosophy. It's a question of whether the colour (i.e. what we see in our own personal vision) is a product directly of the wavelength, or more of the mind assigning that wavelength a visual interpretation. Either way, you can still teach someone what the colour "blue" is, because all "blues" have the same wavelength. Trippy, isn't it?? Confucius say "red is only a colour, but green is a way of life" :)

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

Heisenburg?

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

I wonder if he knows Mrs. Palmer?

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

That's why you always double-check your spelling! 'Tattos' are permanent you know!

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

I think everyone has had this at some point :) What's worse, IMHO, is when your boss IS technical but still fails to give you all the details from the client... until the last minute when he magically remembers...

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty

I'm sitting beside one, which is very frustrating given he has a degree and 3 years commercial experience in ASP.NET and we are all but exclusively a web development team. 4 days it's taken him to add a form tag around some HTML given to us by the design team and hook it up to post to Monorail with its DataBinder. Can't wait until I tell him it has to have Javascript (ooooohhh! what's that??) for some simple validation... Actually, what's worse do you think? Programmers who don't know HTML or BA's that think they do?

Typical n-tiered architecture: DB <-> Junk(0) <-> ... <-> Junk(n-1) <-> Pretty