|
I created a couple sticky messages in my personal member forum. In one I extended an offer to help with coding and the other was to serve as a way people can post code (in reply messages). However, when I tried replying to one of my messages, I was told that I couldn't because it was sticky.
My recommendation is that you make this a distinct option. So people can select sticky messages and disallow replies using two different checkboxes. Or if you can't do that for some reason, make it more obvious earlier on that replies will not be allowed. For example, but changing the checkbox to say "Make Sticky and Disallow Replies". Another example would be to show "you can't reply to this message because it's sticky" when I first click "reply" rather than waiting until after I've spent all the time to compose a message only to find that I can't post it.
|
|
|
|
|
I agree, however making them sticky would leave your messages exactly where they are now. For now.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
I will remove the 'reply' button for sticky messages.
The reason we do not allow replies to stickies is because not doing so would mean every time you loaded the page you would have to wade through the same thread each time.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Chris, I suggest you have a coffee, then read this thread again.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
"So people can select sticky messages and disallow replies using two different checkboxes. Or if you can't do that for some reason, make it more obvious earlier on that replies will not be allowed."
I'm choosing option #2 because of the explanation I gave. I ended up not removing the reply button, but simply dimming it.
Which bit didn't I understand?
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
you said "I will remove the 'reply' button for sticky messages." however there currently is no reply button for them, that is exactly what the OP wants you to add, for the personal forum, and at his discretion.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Actually, the "reply" button did exist. I think he already took it away. That was the less preferred option, but it was one I gave (that prevents me from composing a message only to find out I can't post it).
In addition to that, I'd like to have the ability to create sticky threads that allow for replies, if I want (and also keep the ability to make sticky threads that don't allow for replies).
|
|
|
|
|
I'm getting even more confused now. There wasn't a reply widget 11 hours ago, when I first replied (and well before Chris did, so if he had changed things, he would/should have said so). So I think I understood your suggestion perfectly and it looked to me Chris did not. And I'm still with you, whether a reply widget gets shown should be independent of whether a message is "sticky".
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
I think I see where the confusion is coming from. When I create a sticky message in my personal forum, I see a reply button. However, the sticky message currently in the Lounge does not have a reply button. Seems there are different implementations for different forums.
|
|
|
|
|
Well spotted. So all was fine from the start??? I still would prefer separate checkboxes for sticky and accepts-replies...
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Luc Pattyn wrote: So all was fine from the start?
Nope, my beef has been with the personal forum the entire time, and nothing about that has changed. I want to be able to make stickies with replies. Or, if I can't have that, then get rid of the reply button for stickies.
Luc Pattyn wrote: I still would prefer separate checkboxes for sticky and accepts-replies.
That would be ideal.
|
|
|
|
|
I have seen the finer details of your beef now.
Offering features (e.g. a reply widget) that end with "I can't do that" does not make sense to me.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
AspDotNetDev wrote: Seems there are different implementations for different forums.
No just different implementations for different people.
If Chris (aka 'the master of the hamsters') posts a sticky, the hamsters naturally assume that there can be no improvement or comment on the message and so there is no need for a reply button.
But when we (the flawed people (in the eye's of the hamsters) post one there is room for improvement and comments so there is a reply button.
The whole 'you can not post a reply to a sticky message' thingy is just the hamsters way of having fun at our expense. They just enjoy seeing us clicking the 'post message' button franticly and getting frustrated.
|
|
|
|
|
You see the Reply button because you are an admin on that forum. To make Luc happy I should make the reply button visible, but disabled, with a tooltip explaining why, for everyone.
To make you both happy I should add the ability to have Sticky Threads. I'm sure the peanut gallery can make their own comments on that. Then, to round it off, I should have the ability to close threads so no one can reply, giving me the ability to create pinned messages at the tops of forums that don't cause irritation for general users.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Chris Maunder wrote: To make you both happy I should add the ability to have Sticky Threads.
Assuming "thread" implies replies to the original message, then that about sums it up.
|
|
|
|
|
Chris Maunder wrote: The reason we do not allow replies to stickies is because not doing so would mean every time you loaded the page you would have to wade through the same thread each time.
What's wrong with that? Why not make it user-configurable so each user can decide if they want to allow replies to their sticky threads?
Personally, if one of my two sticky threads got too long, I'd just make it unsticky and create a new sticky thread to replace it (and perhaps link to the old thread from the new one).
|
|
|
|
|
Why can't you allow replies for stickies without showing them and add a link to view replies?
|
|
|
|
|
|
IE 6.0 is old and should be upgraded to either FireFox or IE 8 or 9. I had problems with IE 6.0 and they went away (mostly) when I started using the latest version of FF.
[Edit]
Any current version of most browsers should alleviate most problems with this site.
HTH
|
|
|
|
|
IE6 may be displaying a dialog that a script is running slow, but it still runs slow on other browsers. Go to latest articles and give it a try. Pegs my CPU for 5-10 seconds (IE8).
|
|
|
|
|
I'm flying in this site and have no prob with the articles opening and blistering fast speeds. FF 4.0
|
|
|
|
|
Sorry but, just like Microsoft, CodeProject too does not support IE6 anymore.
I would suggest you to upgrade to latest versions of IE for your own good. IE6 has lots of issues (including security holes!)
|
|
|
|
|
The IE6 javascript engine is about a zillion times slower than any other browser available. That it chugs on stuff that everything else finishes almost immediately is to be expected.
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
Just to clarify that this isn't just an IE6 problem...
When I go to latest articles, one of my processors jumps to 100% for 5 to 10 seconds. This seems to happen every time I go to the page. Seems a bit excessive for such a simple page.
It may be related to the fact that there is nearly 7,000 lines of HTML when I view the source of the page. That also seems excessive.
|
|
|
|
|
That page isn't exactly a Javascript powerhouse. There's some extraneous viewstate (that I'm currently ridding the world of) but not a ton of javascript.
Do you have any add-ins installed that might be playing silly buggers?
[Edit] I can replicate on IE6-8, but not IE9, which leads me to think it's definitely javascript. Still hunting.]
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
modified on Thursday, April 7, 2011 11:02 PM
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Jig | [Dance]](https://www.codeproject.com/script/Forums/Images/jig.gif)
INDIA Cricket WC 2011 Champions!