|
Hey Tom
<pre> tags do take spaces.
int main()
{
for(int i=0; i<10; i++)
x.Add(i);
return 0;
}
For <code>, you need to use
1<br />
2<br />
3<br />
|
|
|
|
|
 Are you seeing spaces in your main block?? I'm not. Everything is left-justified.
Cheers,
Tom Archer - Archer Consulting Group
"So look up ahead at times to come, despair is not for us. We have a world and more to see, while this remains behind." - James N. Rowe
|
|
|
|
|
what is your navigator ?
IE does display spaces,
firefox doesn't...
i didnot test with other however
TOXCCT >>> GEII power
[toxcct][VisualCalc]
|
|
|
|
|
Ok. I get it now. It works in IE and not FF. What's the deal with supporting FF. I thought I had read threads that CP now supported FF
Cheers,
Tom Archer - Archer Consulting Group
"So look up ahead at times to come, despair is not for us. We have a world and more to see, while this remains behind." - James N. Rowe
|
|
|
|
|
Tom Archer wrote:
It works in IE and not FF.
Yeah 
|
|
|
|
|
Since the point of "pre" is to turn off the "all consecutive spaces get collapsed into one" parsing rule, FF is seriously horked if it's eating the spaces in a <pre> block. Maybe the CSS styles are doing something funky that FF doesn't like.
--Mike--
Visual C++ MVP 
LINKS~! Ericahist | 1ClickPicGrabber | CP SearchBar v2.0.2 | C++ Forum FAQ
Strange things are afoot at the U+004B U+20DD
|
|
|
|
|
|
In netscape6.css, there's a rule that looks like this:
.messagecontent
{
white-space: normal;
}
Since <font class="messagecontent"> tags wrap the text inside <pre> tags, the correct behavior is lost.
Solutions:
1) Remove that rule.
2) Stop wrapping text within <pre> blocks in those crazy font tags.
But wait - why would #2 ever exist?
Well, it seems that the site designers weren't really so stupid as to throw in a tag having no purpose other than to ruin the default behavior of the pre tag. As downloaded, the source indicates the font tag is supposed to be outside of the pre tag (and the rest of the message). But, for some reason, it's never closed... and that's where things get a bit weird. Both IE and FF handle malformed HTML reasonably well. But they do so in rather different ways. FF, it seems, closes the tag immediately and then goes wild, duplicating the unclosed tag wherever it might have been meant to apply. So we get extra font tags scattered throughout the message text... including within the pre block. Thus the obvious solution is:
3) close the freakin' font tag! 
You must be careful in the forest
Broken glass and rusty nails
If you're to bring back something for us
I have bullets for sale...
|
|
|
|
|
Yep. As in preserve formatting. Looks like shog figured it out. Should be easy enough for the CP folks to fix.
Cheers,
Tom Archer - Archer Consulting Group
"So look up ahead at times to come, despair is not for us. We have a world and more to see, while this remains behind." - James N. Rowe
|
|
|
|
|
The few times (three, to be precise) that I have posted a query in the "mini-forum" that is at the foot of each Article on this site, I have been presented with a "Page cannot be found" error - the posting does get through, but still...
cheers
Phil
|
|
|
|
|
Many times there are very interesting questions in the forum which would be interesting to know the answer. In these cases I usually keep going back to those questions to see if anyone answered them. I think it would be beneficial to add capability to be copied on the response of specific messages posts.
|
|
|
|
|
I agree with Rudy there should be an option like this...
|
|
|
|
|
Does the DDE functions in matlab work for every programs? I asked this since the examples i found in the internet are mostly about using DDE to connect matlab only with excel or winword
Thanks in advance
|
|
|
|
|
General Discussions, or a language sepcific forum would be the correct place for this question, but I 'll give an answer anyway. DDE was an early version of cross process communication based on windows messages. It saw it's peak in popularity with windows 3.1. I would be supprised if many applications support DDE these days.
I can imagine the sinking feeling one would have after ordering my book,
only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
|
|
|
|
|
When posting or replying to messages on this forum, there is a checkbox below the message area says
"Do not treat <'s as HTML tags"
Negatives are not a good idea in such situations - leaving it unticked is then a sort of double-negative required to traat them as tags -which is fact the default. I have to think this through each time, and I'm sure others have got it wrong on occassions. Better would be the more positive statement:
"Treat <'s as HTML tags"
and have the box ticked by default (if you want to keep the default the same as it is now.)
Now then... this message contains <.... do I tick this box or don't I....? Yes, I think so... Yes, I know, there is a preview button...
cheers
Phil
|
|
|
|
|
He's back... as a screensavers.com ad on the side of John Simmons' article "String Parsing Class". Also, at the bottom of this page is the "Earn Degree Now" ad from ASU (I think...)
I realize that CP needs money, but I think more relevant ads would be more effective. (And the moment we get a 'lower my bills' click-your-state ad with the super-long bouncing pig or the #$^*$@% gingerbread man, ...  )
|
|
|
|
|
hi,
I think it would be nice to somehow highlight "Do not treat <'s as HTML tags" text (red and bold?), or maybe reformulate the text... lot of people are confused, like "who the hell ate my XML tags??" 
yes, it's fairly obvious what "Do not treat <'s as HTML tags" means, but again and again I see lot of post duplicated (in better case  ) because of this.
Any ideas?
just my 2 cents
David
Never forget: "Stay kul and happy" (I.A.)
David's thoughts / dnhsoftware.org / MyHTMLTidy
|
|
|
|
|
Three ideas:
1) make it the default option, or one that must be turned off in preferences in order for it to stick.
2) replace all posters with new ones, better ones, ones that know to look for both the checkbox and the [edit] link when they screw up. We may need to institute a regimented breeding and training program to accomplish this, and needless to say it would be exceedingly long-term.
3) leave things as they are, recognizing malformed posts as one more indication of someone who really doesn't want a reply.
You must be careful in the forest
Broken glass and rusty nails
If you're to bring back something for us
I have bullets for sale...
|
|
|
|
|
Shog9 wrote:
recognizing malformed posts as one more indication of someone who really doesn't want a reply.
That's alright except when it is the reply.
|
|
|
|
|
True.
You must be careful in the forest
Broken glass and rusty nails
If you're to bring back something for us
I have bullets for sale...
|
|
|
|
|
Shog9 wrote:
1) make it the default option, or one that must be turned off in preferences in order for it to stick.
The only problem is that it will break all the "pretty" html people put in their sig, Shog9. They would have to separate that out from the content either with some kind of parser, or with adding an extra database field.
I can imagine the sinking feeling one would have after ordering my book,
only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
|
|
|
|
|
The sig and the message are initially sent as separate values - shouldn't be hard to treat one as HTML, the other as text. Yeah, going back and editing it would be odd, but no worse than if the user had just posted escaped HTML in the first place.
You must be careful in the forest
Broken glass and rusty nails
If you're to bring back something for us
I have bullets for sale...
|
|
|
|
|
Shog9 wrote:
1) make it the default option, or one that must be turned off in preferences in order for it to stick.
This certainly is good option. Most of -at least my- responses are links to MSDN (so HTML is needed for clickety), OTOH people who use clickety are usualy smart enough to use this option and/or "modify" ...
Shog9 wrote:
2) replace all posters with new ones, better ones, ones that know to look for both the checkbox and the [edit] link when they screw up. We may need to institute a regimented breeding and training program to accomplish this, and needless to say it would be exceedingly long-term.
3) leave things as they are, recognizing malformed posts as one more indication of someone who really doesn't want a reply.
You think they will just die off?  It would be definitely good for overall level of CP, but I am affraid this is not going to happen.
David
Never forget: "Stay kul and happy" (I.A.)
David's thoughts / dnhsoftware.org / MyHTMLTidy
|
|
|
|
|
sorry all - don't know how I managed to miss this post - just posted a new thread on this very topic
Phil
|
|
|
|
|
We could test the textbook example of natural selection.
I'm referring to the example where a group of people live on a mountain that has a low hanging branch. As the tall people continually hit their head on the branch and fall off the mountain and die, the only ones left to procreate are the short ones. According to natural selection, after a while, there will only be short people.
Well, if we refuse to answer posts from people who don't form their posts correctly...
Cheers,
Tom Archer - Archer Consulting Group
"So look up ahead at times to come, despair is not for us. We have a world and more to see, while this remains behind." - James N. Rowe
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
