Quote:
Originally Posted by schferk
Hello Mark and quant.
(The "boy" was for your "scherk", but exchange of serious arguments is possible anytime, so 
Yes, I hijacked this thread, but you did the opposite: You created a new thread for a problem that had been treated in another thread - you didn't add up to that one but authored a new one. I might be considered quite intrusive by many people, but then, if there's a thread to which I can add my additional details, I prefer people NOT having to read those "as they were all new" - might considered paradoxical within an overall view of my various contributions. |
schferk,
I can assure you that calling you 'scherk' instead of 'schferk' was an accident and not intended as an insult. If I had actually intended to be insulting it would have been something more like 'schjerk', but since nothing intentionally insulting like that was done hopefully you can see it was a typo.
I'm sorry if you have read the kinook forum so much that people's suggestions in the forum category set aside for suggestions are becoming repetitive.
I would guess in a perfect forum world there would be an organizational system so efficient that all postings which might possibly be related to the RICHED32.DLL would all go under a single thread titled something like "
Please post your reason here why Microsoft's riched32.dll should be left for Microsoft apps to use and not reused as a free rich text editor in this application". I suppose that thread might contain a lot of different reasons, but it could also be that people would be afraid to post in that thread because they might have mistakenly organized their posting incorrectly, and then the whole organizational system would just break down.
Anyway, I did not see a thread describing the same problem and asking about a future resolution to the problem. If there does happen to be one, I missed it. But one thing is absolutely certain - this thread has been so derailed that it really might as well not have existed in the first place. So much for organization.
Thanks,
Mark.