Re: [OT} UI design - Daily WTF

On 26 April 2010 15:04, Ian Thomas wrote: > Something for a holiday Monday. > > I was just referred to an article on an old Daily WTF post, “Enter the > Matrix ” – I think > I’ve seen it before, but I had to chuckle again at the UI design. R

[OT} UI design - Daily WTF

Something for a holiday Monday. I was just referred to an article on an old Daily WTF post, "Enter the Matrix " - I think I've seen it before, but I had to chuckle again at the UI design. Reading the post, it came from elsewhere, in 2004.

RE: Designer crash cause found

I reckon I make that property case mistake about 2-3 times per year, but you normally get an immediate stack overflow and you find the error within a minute. This time I was word blind looking the code and the designer found the problem for me, then it helpfully fatally crashed, leading me astray.

RE: Designer crash cause found

Or coding in VB.Net (ducks and hides) Cheers, Cam From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Mitch Wheat Sent: Monday, 26 April 2010 1:47 PM To: 'ozDotNet' Subject: RE: Designer crash cause found looks like a case in f

RE: Designer crash cause found

looks like a case in favour of adding underscores to private variables! Cheers, Mitch From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Monday, 26 April 2010 11:39 AM To: 'ozDotNet' Subject: RE: Designer crash cause found Looks lik

RE: Designer crash cause found

Looks like it might be a case issue causing an infinite loop get { return UniqueId; } Should it actually be get { return uniqueId; } You mean I had an infinite loop, and it took 3 hours to find out (well, actually I didn't find out at all, until you pointed it out). I

RE: Designer crash cause found

well spotted, Cam! From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Cameron Booth Sent: Monday, 26 April 2010 11:14 AM To: 'ozDotNet' Subject: RE: Designer crash cause found Hi Greg, Looks like it might be a case issue causing an infinite loop

RE: Designer crash cause found

Hi Greg, Looks like it might be a case issue causing an infinite loop get { return UniqueId; } Should it actually be get { return uniqueId; } Cheers, Cam From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf

Designer crash cause found

I thought this would take hours, but after walking around the back yard to feed the birds and calm down, I returned and started a new process of elimination and eventually found the cause of the designer crash was something surprising and incomprehensible. For debugging display purposes the low

Visual Studio Form designer crashes

I started work this morning on a Forms utility project that I've been working on for several weeks. There are a dozen controls derived from a simple "base UserControl" full of helper methods. I have found that every control derived directly or indirectly from the base control cannot be opened in th