AW: KMail development advice

[Kevin Krammer]

Hi Leonard,

On Thursday, 2016-08-18, 13:08:19, Leonard Marquitan wrote:
> Hi Dan,
> 
> thanks for your response and the short explanations.
> I'll explain a simple task that I tried to accomplish which will help me
> working on larger parts once I know how it is to be approached:
> I chose the kmcomposerui for first tries because it seems rather
> straightforward and well-structured. I want to add a basic element to the
> toolbar contents. The most basic one I found was a separator. So I open
> kmcomposerui.rc, bump the version number (from 435 to 436) and add
> <Separator/> at any spot between two actions. Then I rebuild the project. I
> guessed that those were the most basic steps I could do to perform any ui
> changes. However, the new separator was nowhere to be seen. So I believe
> there's something I'm not getting right.
> Can you explain why this approach is not working?

Maybe you didn't commence the install step that would put the modified files 
into a location searched by the application at runtime.

See Ingo's mail.

If you are mainly modifying these rc files it might be an option to just put 
symlinks into the user local directory that Ingo mentioned which then point to 
the rc files in your source directory.

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20160819/7a3de01a/attachment.sig>