Discussion about CodeLite development process and patches
petah
CodeLite Expert
Posts: 231 Joined: Sat Nov 24, 2012 8:04 pm
Genuine User: Yes
IDE Question: c++
Location: Los Angeles
Contact:
Post
by petah » Sun Jun 30, 2013 7:09 pm
just remembered: to make it easier to identify the debugged CL instance, I suggest patching your ./CL_test/LiteEditor/frame.cpp in SetFrameTitle() so the window tab has a different title, f.ex. change:
Code: Select all
title << _("Codelite ");
title << clGitRevision;
to:
It's especially useful under Xfce where the active instance highlight can get out of sync.
cheers,
-- p
main: Debian Jessie x64 + custom wxTrunk
pavel.iqx
CodeLite Enthusiast
Posts: 19 Joined: Wed Jun 26, 2013 12:46 pm
Genuine User: Yes
IDE Question: c++
Contact:
Post
by pavel.iqx » Sun Jun 30, 2013 11:06 pm
how do you know i'm using xfce?!
Debian GNU/Linux 7.3 (wheezy) x64; CodeLite 5.4 from repo & CodeLite self-compiled from git HEAD
eranif
CodeLite Plugin
Posts: 6375 Joined: Wed Feb 06, 2008 9:29 pm
Genuine User: Yes
IDE Question: C++
Contact:
Post
by eranif » Mon Jul 01, 2013 8:14 am
pavel.iqx wrote: how do you know i'm using xfce?!
He doesn't - but now we know
He was talking about himself, petah is using xfce ...
Eran
pavel.iqx
CodeLite Enthusiast
Posts: 19 Joined: Wed Jun 26, 2013 12:46 pm
Genuine User: Yes
IDE Question: c++
Contact:
Post
by pavel.iqx » Mon Jul 01, 2013 5:02 pm
I knew...
Debian GNU/Linux 7.3 (wheezy) x64; CodeLite 5.4 from repo & CodeLite self-compiled from git HEAD