save/copy messages in message window?

[MoonKid]

How is it possible to copy/save messages from the message window (build messages).

I can not save build-errors to clipboard and post them anywhere. Understand?

I am using
Code::Blocks 1.0 revision 2062 Build: Feb 23 2006, 03:02:53 - wx2.6.2 (Windows, ANSI)

[Michael]

Hello,

Did you try in the Build log tab to click the right mouse button, chose e.g., Select All and then Copy?

Best wishes,
Michael

[MoonKid]

The context menu on the build-tab shows
- tabs at top
- tabs at bottom
- show/hide >

context menu in the message window (where the messages are) is not possible.

[Michael]

The context menu on the build-tab shows

Not on the tab, but inside the window .

Best wishes,
Michael

[MoonKid]

Not on the tab, but inside the window .

inside the window I can get no contextmenu. There is nothing!

[tiwag]

it does not work on the moon, only on earth ...

[Michael]

Not on the tab, but inside the window .

inside the window I can get no contextmenu. There is nothing!

Inside the Build log window and not in the Build messages windows. Here it works fine.

Best wishes,
Michael

[MoonKid]

Inside the Build log window and not in the Build messages windows. Here it works fine.

The build log window works fine. That is not the problem. But it does not help me.

I need the clean extracted messages from the build messages window.

[Michael]

Inside the Build log window and not in the Build messages windows. Here it works fine.

I need the clean extracted messages from the build messages window.

Ah, ok. Then AFAIK it is not possible.

Best wishes,
Michael

[thomas]

Ah, ok. Then AFAIK it is not possible.

Luckily, it is not
Would be quite bad if that was possible.

[mandrav]

Well, it is possible since revision 2312.

[thomas]

What a great idea...
When we tell someone having the typical "XXX does not compile" problem to post the build log, we will now get those absolutely useless build messages 50% of the time... brilliant.

[mandrav]

What a great idea...
When we tell someone having the typical "XXX does not compile" problem to post the build log, we will now get those absolutely useless build messages 50% of the time... brilliant.

"useless" ?!?
You know, they 're the very same messages that appear in the build log.
And, yes, I know they don't contain the actual command-lines. You have to tell people to enable full command-line logging anyway, so you might as well clarify that you 're interested in the build log and not the build messages...

[tiwag]

... You have to tell people to enable full command-line logging anyway ...

i would propose to set "full comandline logging" as default setting anyways

[thomas]

You have to tell people to enable full command-line logging anyway

That's why I suggested making the full commandline the default a few months ago. It is bad enough that people have to enable "normal" output explicitely.

I mean, OK... if someone absolutely does not want to see the compiler messages, I can even understand why someone would want beautified messages (although you don't need to read them if you don't want...), and they're handy for jumping to an error line, too.

But if you give them the ability to copy the beautified messages, then people will really do so.
As people post "Compiling foo.cpp" now when asking for help building something, they will now post beautified error messages. I don't think that is any good.

[takeshimiya]

Everything is right as is now.

What could be improved is put a checkbox or an item in the contextual menu for changing enable full command-line logging.
I tend to change it from time to time (I try to have always disabled, but for some testings, ie. testing if the compiler is setup ok, or if backticks are expanding correctly, I enable it), so a setting for doing this more accesible would be great.

[mandrav]

But if you give them the ability to copy the beautified messages, then people will really do so.
As people post "Compiling foo.cpp" now when asking for help building something, they will now post beautified error messages. I don't think that is any good.

OK, I see the fault in your thinking: you only think about us and the support we offer in these boards.
But, please, stop for a while and think of a feature as exactly that: a feature, something that boosts productivity (at least for those who need it). When we add a feature, we don't add it for us but for the users.
If we were to think only about ourselves, most of current C::B features would not have been implemented unless we really needed them. Does this sound nice to you?

Regarding the specific feature discussed here:
When you tell a user to post his "build log", you expect he does that. If he posts the "build messages" then you have every right not to help him any further, if you don't feel the need to clarify. He doesn't deserve our help if he fails to do what he was asked to do. It's as simple as that.
Hence, I see no reason for this debate to continue...

[mandrav]

i would propose to set "full comandline logging" as default setting anyways

There's a reason for the default setting being "simple logging": It helps new users (mostly newbies) and makes C::B look a little more user-friendly. Believe it or not, long command-lines can intimidate new users (if they 're coming from the windows land). We don't want that.
And most importantly: it's a setting you can easily change once and never have to worry about it anymore.

[tiwag]

i would propose to set "full comandline logging" as default setting anyways

There's a reason for the default setting being "simple logging": It helps new users (mostly newbies) and makes C::B look a little more user-friendly. Believe it or not, long command-lines can intimidate new users (if they 're coming from the windows land). We don't want that.
And most importantly: it's a setting you can easily change once and never have to worry about it anymore.

ok i understand your preference,

now to something completely different ... 
would you accept a third logging option,
which sends short build messages to the build-log by default,
and only if an error has occured the complete compiler or linker commandline ?

if you'd accept such an option, i would implement it.

[takeshimiya]

OK, I see the fault in your thinking: you only think about us and the support we offer in these boards.
But, please, stop for a while and think of a feature as exactly that: a feature, something that boosts productivity (at least for those who need it). When we add a feature, we don't add it for us but for the users.
If we were to think only about ourselves, most of current C::B features would not have been implemented unless we really needed them. Does this sound nice to you?

Little off-topic, but that's a perfect description of thomas attitude. It's like more inclined of a customer-client thinking instead of a community thinking.

I've noted this to you before, thomas, on a personal message which you never replied. I really don't like when you say everytime to the people here "no this, no that".

Instead you could said 'I' will not do that, or something less dissapointing than a simple 'no', like "you 'll have to wait until we close most bugs and after other imporant things". That keeps people with hopes and a smile, at least.

[Michael]

Well, it is possible since revision 2312.

Sorry, but how?

I have built C::B rev2312 both in Windows and in Linux (Ubuntu 5.10), but I do not have a context menu in the "Build messages" tab. Should I do something special to activate this menu?

Thank you.

Best wishes,
Michael

[mandrav]

Well, it is possible since revision 2312.

Sorry, but how?

I have built C::B rev2312 both in Windows and in Linux (Ubuntu 5.10), but I do not have a context menu in the "Build messages" tab. Should I do something special to activate this menu?

Thank you.

Best wishes,
Michael

Not "on" the tab, but "in" the messages list

[tiwag]

Well, it is possible since revision 2312.

Sorry, but how?

I have built C::B rev2312 both in Windows and in Linux (Ubuntu 5.10), but I do not have a context menu in the "Build messages" tab. Should I do something special to activate this menu?

Thank you.

Best wishes,
Michael

Not "on" the tab, but "in" the messages list

it doesn't work for me too ( be sure i tried also ""in" the messages list" ) 

[Michael]

Not "on" the tab, but "in" the messages list

Yes, I have tried both on the tab and on the messages list, but without result.

Best wishes,
Michael

[thomas]

Little off-topic, but that's a perfect description of thomas attitude.

Actually it is a misunderstanding of my intent, but never mind that.

I've noted this to you before, thomas, on a personal message which you never replied. I really don't like when you say everytime to the people here "no this, no that".

In fact, you are the only person who regularly gets to hear "No" without further comment from me. And it will stay like that.
I could explain why that is so, but honestly, I am not willing to spend the time for that, for it is in vain. Actually I did not intend to answer to this post either, but was convinced to do so anyway.

[takeshimiya]

I've noted this to you before, thomas, on a personal message which you never replied. I really don't like when you say everytime to the people here "no this, no that".

In fact, you are the only person who regularly gets to hear "No" without further comment from me. And it will stay like that.
I could explain why that is so, but honestly, I am not willing to spend the time for that, for it is in vain.
Actually I did not intend to answer to this post either, but was convinced to do so anyway.

I don't have any problems with that personally, note that I was talking about other persons, not me.
Agree to disagree?

[mandrav]

Not "on" the tab, but "in" the messages list

Yes, I have tried both on the tab and on the messages list, but without result.

Best wishes,
Michael

Hmm, seems I forgot to commit? :lol:

[Michael]

Not "on" the tab, but "in" the messages list

Yes, I have tried both on the tab and on the messages list, but without result.

Best wishes,
Michael

Hmm, seems I forgot to commit? :lol:

Ah, ok :lol:.

Best wishes,
Michael

[tiwag]

Not "on" the tab, but "in" the messages list

Yes, I have tried both on the tab and on the messages list, but without result.

Best wishes,
Michael

Hmm, seems I forgot to commit? :lol:

no you didn't forget 

the problem is, that there is some interaction with the DragScroll V0.19 plugin,
when i deactivate the DragScroll plugin i get the Message-log's Popupmenu too.

[Pecan]

the problem is, that there is some interaction with the DragScroll V0.19 plugin,
when i deactivate the DragScroll plugin i get the Message-log's Popupmenu too.

Wups! I'll have a look at this and fix it.
Are we talking about Windows or Linux?

thanks
pecan

[Pecan]

Re: DragScroll vs. Build Messages Context menu confict.

Fixed in SVN 2315. Had to remove drag scrolling ListCtrl windows.

Hate to do this since drag scrolling the Find Results window is
very convenient.

Will try to figure out a better solution.

thanks
pecan

[mandrav]

Not "on" the tab, but "in" the messages list

Yes, I have tried both on the tab and on the messages list, but without result.

Best wishes,
Michael

Hmm, seems I forgot to commit? :lol:

no you didn't forget 

the problem is, that there is some interaction with the DragScroll V0.19 plugin,
when i deactivate the DragScroll plugin i get the Message-log's Popupmenu too.

Ah, thanks
That was strange because since I referred to a specific revision, I must had committed...

[Michael]

Hello,

I have just tried it in Ubuntu 5.10 and it works fine . I just wonder why you cannot simply click anywhere in the window list, but on a message to get the context menu.

Best wishes,
Michael

[tiwag]

Re: DragScroll vs. Build Messages Context menu confict.

Fixed in SVN 2315. Had to remove drag scrolling ListCtrl windows.

Hate to do this since drag scrolling the Find Results window is
very convenient.

Will try to figure out a better solution.

Wouldn't it be possible to skip the event for further processing after drag-scrolling ?

[Pecan]

Wouldn't it be possible to skip the event for further processing after drag-scrolling ?

Have found the problem. Wouldn't you guess....A missing event.Skip().
Man, it's just too easy to forget 'em. We need an auto_event.Skip() like
an auto_ptr.

Will commit after testing on linux. Then we'll have listctrl scrolling back.

thanks
pecan

[tiwag]

Have found the problem. Wouldn't you guess....A missing event.Skip().

found it too and patched it locally, works fine again 

btw. many thanks for this great plugin !