Quote:
Originally Posted by Bluenoser
Absolutely agree with you, it should be handled properly. That's why I was saying this is being discussed in the other thread. Markus was already involved in that discussion, and if you build on it he's more likely to see what everyone is asking for. Keep it together so Markus doesn't have to trudge around the board looking for "all" the threads on the same topic instead of making it easy for him and keeping it in one. Seems to me since he's the guy who does the programming, keeping the information he needs in as few places as possible would make it easier for him to refer to once he starts working on it.
Edit - almost forgot - *shrug*
|
Spare me the lecture. I am quite aware of the information that developers need in order to address issues, and I am further aware that this needs to be addressed differently from that which is discussed in the thread you referenced. The other thread is talking about a new feature. I am talking about fixing a situation that's dang near broken before bothering to implement a new feature on top of a near-broken system. And so you don't have to fret about it, you can be assured that I made sure that Markus would be aware of the information posted here.