|
In forums ther is date and time of the post. But there shoud be also setting for TimeZone you are in. And you could know when it was posted on your local tinme.
ps: i hope somebody understanded...:
|
|
|
|
|
|
Somebody's got malformed HTML in his/her signature
|
|
|
|
|
Is there a list of the award winning coding articles? Any way to list?
|
|
|
|
|
|
This article won't load in my browser:
http://www.codeproject.com/csharp/ADS.asp
|
|
|
|
|
waveangle wrote: http://www.codeproject.com/csharp/ADS.asp
Loads here in both IE and FF.
|
|
|
|
|
Oh sorry, duh... It's the "ADS" string in the url. My ad filter was blocking it.
|
|
|
|
|
waveangle wrote: This article won't load in my browser:
http://www.codeproject.com/csharp/ADS.asp
Hope you got to see it. It's a quality article... :->
Sean
|
|
|
|
|
Just tried to search for "list box" with only MFC\C++ box ticked and got hell lot of C# replies.
--------------------------------
Human stupidity is infinite.
|
|
|
|
|
I'd like to see the pages redesigned so the article text is never cut off on the right. Same goes for printing. I was just about to print a 63 page article when I noticed most of the lines were cut off.
The table layout can be tweaked to prevent this, or you could drop the tables entirely.
|
|
|
|
|
Did you try the printer-friendly version?
|
|
|
|
|
What printer friendly version? I can't find a button for that.
I find that if I change the line in the page source from
to something like
the page looks better in print preview.
The problem shows up in print preview, not on the screen page actually. I haven't printed anything yet.
|
|
|
|
|
waveangle wrote: What printer friendly version? I can't find a button for that.
It's on the left-hand side of the article, under the heading "Toolbox".
|
|
|
|
|
Ok thanks I didn't see that. I still get one char or so cutoff in the printer version. Just setting that same div width to 95% or so would fix this.
|
|
|
|
|
Also
<div style="padding: 1em;">
seems to work.
|
|
|
|
|
I just posted a reply in which I wanted to show a screen shot (a GIF), but couldn't make it work. It would be nice to be able to do this.
Thanks,
Royce
|
|
|
|
|
Check out image hosting services like PhotoBucket or Flickr. These provide easy ways to upload images and link to them from other sites (such as CP).
|
|
|
|
|
i have use Who's Who at the Code Project
when i search i typed saksida. I have noticed that has found 251769 pages. And only i am on the list. But when i click next buttion. i got the same data, but a diffrent search position.
|
|
|
|
|
1.
It would be nice to have the entire thread available on the reply page.
When creating a reply i often need to look back at more than just the previous message to grab quotes, check facts, ...
2.
I understand you need to display ads, no problem.
However, i miss having the main page section listings on the left (when not on the main page).
I'd rather not have to go back to the main page to select 'Tree Controls' for example.
This is somewhat related to the 1st suggestion, in that; when creating a reply i will often want to find a relevant article and get it's link.
Currently i open other instances of CP to handle the above.
Neither are urgent, just might want to mull over the usage pattern and think about ways to streamline things.
...cmk
Save the whales - collect the whole set
|
|
|
|
|
I've hung around CP for a couple of years, now, lurking in the silent shadows of anonymity. Recently, though, I've started contributing back to the community since I've recently written Win32/.NET applications and feel comfortable with the accurary and precision of my answers.
In my answers and article (with more articles to come; I want that platinum status, folks!), I've found an irritant that causes me to cringe everytime I see it: PRE tags that extend beyond the border of the message/article. Of course, it does not do that in MSIE. I accept that. Since I exclusively use FF to view CP, though, I see it on almost every page.
The problem occurs because of the higlighted line in the following snippet from the CSS file /styles/global.css:
PRE
{
background-color: #FBEDBB;
padding: 7pt;
background-image: url(/images/codebg.gif);
font: 9pt "Courier New", Courier, mono;
white-space: pre;
<span style="background-color:#9999cc;">width: 100%;</span>
} If that width: 100%; gets removed from the global.css file, then the PRE tags behave the same on both MSIE 5.5/6.0 and FF 0.X/1.X. This behaves as it should, with the PRE tag's block display extending to the boundaries of its parent HTML block display element. [I don't know about other broswers because I don't have them installed. Sorry. If I did, I'd test them for you.]
If anyone does not have any objections, can we remove that width: 100%; from the CSS file? And, if there's anything I can do to help with this change (or no change, as that's okay, too), please, do not hesitate to ask.
Sorry about the complaint. Just thought I'd ask. Never hurts, right?
"we must lose precision to make significant statements about complex systems."
-deKorvin on uncertainty
|
|
|
|
|
Better yet, if both width and overflow are set to automatic:
width: auto;
overflow: auto;
then extra-long lines in pre blocks no longer increase the width of the entire page...
|
|
|
|
|
...if you're using GreaseMonkey+CPHog - stick this in your CPHog user script:
for(var i=0;i<document.styleSheets.length;i++)
{
if(document.styleSheets[i].href.toLowerCase().indexOf("styles/global.css")!=-1)
{
var styleSheet=document.styleSheets[i];
for(var j=0;j<styleSheet.cssRules.length;j++)
{
if(styleSheet.cssRules[j].selectorText=="pre")
{
styleSheet.cssRules[j].style.width="auto";
styleSheet.cssRules[j].style.overflow="auto";
break;
}
}
break;
}
}
|
|
|
|
|
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Hmm... it seems that overflow:auto doesn't work when a post starts out expanded at page load - I guess the layout isn't re-calculated correctly when the script changes the overflow property. I think I recall having this problem before with a lookup control I did - I will have to see what I did there to fix it.
|
|
|
|
|