Re: [GNC-dev] Solved : how to extend the selection of predefined actions on a split

[Paul Dest]

Hi Chris,

That could be a very nice solution.

But (in GTK) it doesn't seem possible to bind an accelerator key to an
arbitrary string of keystrokes. I have checked the GTK3 docs:
https://developer.gnome.org/gtk3/stable/gtk3-Accelerator-Maps.html
It explains about the accelerator path:
--
The accelerator path must consist of
“/Category1/Category2/.../Action”, where WINDOWTYPE should
be a unique application-specific identifier that corresponds to the kind
of window the accelerator is being used in, e.g. “Gimp-Image”,
“Abiword-Document” or “Gnumeric-Settings”. The “Category1/.../Action”
portion is most appropriately chosen by the action the accelerator
triggers, i.e. for accelerators on menu items, choose the item’s menu
path, e.g. “File/Save As”, “Image/View/Zoom” or “Edit/Select All”. So a
full valid accelerator path may look like:
“/File/Dialogs/Tool Options...”.
--

Actually, the accelerator path does not need to reference a menu item
but it must reference an action declared and implemented by the
application. So, the wanted string of keystrokes have to be coded as an
action of the application. Hence, a change in the GnuCash application
itself would be needed.

Regards,
Paul

Am 30.04.2018 um 23:39 schrieb Chris Good:
>>>
>>> Hi Paul,
>>>
>>> Another solution, which does not cause extra work each time you
>>> upgrade, would be to program a function key to output "Paul".
>>> I haven't tried this myself but I think it should be possible to do
>>> this by modifying a gtk3 user configuration file which doesn't get
>>> clobbered by an upgrade.
>>> See https://wiki.gnucash.org/wiki/GTK3
>>>
>>> Regards, Chris Good


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Solved : how to extend the selection of predefined actions on a split

[John Ralls]

> On Apr 30, 2018, at 2:39 PM, Chris Good  wrote:
> 
> 
>> On 1 May 2018, at 7:23 AM, Chris Good  wrote:
>> 
>> 
>> 
>>> On 1 May 2018, at 7:06 AM, Chris Good  wrote:
>>> 
 Message: 6
 Date: Mon, 30 Apr 2018 10:15:29 +0200
 From: Geert Janssens 
 To: gnucash-devel@gnucash.org
 Subject: Re: [GNC-dev] Solved : how to extend the selection of
  predefined actions on a split
 Message-ID: <1739455.a6lqanb...@legolas.kobaltwit.lan>
 Content-Type: text/plain; charset="us-ascii"
 
 Op maandag 30 april 2018 10:07:47 CEST schreef Paul Dest:
> My problem is solved. Due to a hint in the gnucash-de mailing list I
> have identified the needed files and made the changes successfully.
> 
> But still wondering how the *.po files are created. They have very
> regular format and each entry is commented with references to the lines
> in c-files. That does not seem to be coded by the hand; all the *.po
> files would be needed to be rewritten if a line would be inserted in one
> of the c files referenced (what is actually the case with my personal
> changes). Here is an example from de.po to illustrate what I am talking
> about:
> 
> #: gnucash/gnome-utils/gnc-tree-model-split-reg.c:2856
> #: gnucash/register/ledger-core/split-register.c:2486
> msgid "Withdraw"
> msgstr "Belastung"
> 
 
 https://wiki.gnucash.org/wiki/Translation#Updating_an_existing_.po_file
 
 That page has additional documentation on how to translate gnucash (for 
 which 
 the *.po files are used), gnucash documentation or gnucash account 
 hierarchy 
 templates.
 
 Regards,
 
 Geert
>>> 
>>> Hi Paul,
>>> 
>>> Another solution, which does not cause extra work each time you upgrade, 
>>> would be to program a function key to output "Paul".
>>> I haven't tried this myself but I think it should be possible to do this by 
>>> modifying a gtk3 user configuration file which doesn't get clobbered by an 
>>> upgrade.
>>> See https://wiki.gnucash.org/wiki/GTK3
>>> 
>>> Regards, Chris Good
>> 
>> Sent again with Subject this time which I must have somehow clobbered on my 
>> iPad. Sorry.
>> 
>> Regards, Chris Good
> 
> Ah... Problem with missing subject was caused by copying Subject which 
> contained newline. Sorry again...
> 
> BTW, does the GnuCash mailing list enable threads to continue if "Solved" is 
> used to prefix subject?

It's just email and just a subject.

Regards,
John Ralls
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Solved : how to extend the selection of predefined actions on a split

[Chris Good]

> On 1 May 2018, at 7:23 AM, Chris Good  wrote:
> 
> 
> 
>> On 1 May 2018, at 7:06 AM, Chris Good  wrote:
>> 
>>> Message: 6
>>> Date: Mon, 30 Apr 2018 10:15:29 +0200
>>> From: Geert Janssens 
>>> To: gnucash-devel@gnucash.org
>>> Subject: Re: [GNC-dev] Solved : how to extend the selection of
>>>   predefined actions on a split
>>> Message-ID: <1739455.a6lqanb...@legolas.kobaltwit.lan>
>>> Content-Type: text/plain; charset="us-ascii"
>>> 
>>> Op maandag 30 april 2018 10:07:47 CEST schreef Paul Dest:
 My problem is solved. Due to a hint in the gnucash-de mailing list I
 have identified the needed files and made the changes successfully.
 
 But still wondering how the *.po files are created. They have very
 regular format and each entry is commented with references to the lines
 in c-files. That does not seem to be coded by the hand; all the *.po
 files would be needed to be rewritten if a line would be inserted in one
 of the c files referenced (what is actually the case with my personal
 changes). Here is an example from de.po to illustrate what I am talking
 about:
 
 #: gnucash/gnome-utils/gnc-tree-model-split-reg.c:2856
 #: gnucash/register/ledger-core/split-register.c:2486
 msgid "Withdraw"
 msgstr "Belastung"
 
>>> 
>>> https://wiki.gnucash.org/wiki/Translation#Updating_an_existing_.po_file
>>> 
>>> That page has additional documentation on how to translate gnucash (for 
>>> which 
>>> the *.po files are used), gnucash documentation or gnucash account 
>>> hierarchy 
>>> templates.
>>> 
>>> Regards,
>>> 
>>> Geert
>> 
>> Hi Paul,
>> 
>> Another solution, which does not cause extra work each time you upgrade, 
>> would be to program a function key to output "Paul".
>> I haven't tried this myself but I think it should be possible to do this by 
>> modifying a gtk3 user configuration file which doesn't get clobbered by an 
>> upgrade.
>> See https://wiki.gnucash.org/wiki/GTK3
>> 
>> Regards, Chris Good
> 
> Sent again with Subject this time which I must have somehow clobbered on my 
> iPad. Sorry.
> 
> Regards, Chris Good

Ah... Problem with missing subject was caused by copying Subject which 
contained newline. Sorry again...

BTW, does the GnuCash mailing list enable threads to continue if "Solved" is 
used to prefix subject?

Regards, Chris Good
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Solved : how to extend the selection of predefined actions on a split

[Geert Janssens]

Op maandag 30 april 2018 10:07:47 CEST schreef Paul Dest:
> My problem is solved. Due to a hint in the gnucash-de mailing list I
> have identified the needed files and made the changes successfully.
> 
> But still wondering how the *.po files are created. They have very
> regular format and each entry is commented with references to the lines
> in c-files. That does not seem to be coded by the hand; all the *.po
> files would be needed to be rewritten if a line would be inserted in one
> of the c files referenced (what is actually the case with my personal
> changes). Here is an example from de.po to illustrate what I am talking
> about:
> 
> #: gnucash/gnome-utils/gnc-tree-model-split-reg.c:2856
> #: gnucash/register/ledger-core/split-register.c:2486
> msgid "Withdraw"
> msgstr "Belastung"
> 
> 

https://wiki.gnucash.org/wiki/Translation#Updating_an_existing_.po_file

That page has additional documentation on how to translate gnucash (for which 
the *.po files are used), gnucash documentation or gnucash account hierarchy 
templates.

Regards,

Geert


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] Solved : how to extend the selection of predefined actions on a split

[Paul Dest]

My problem is solved. Due to a hint in the gnucash-de mailing list I
have identified the needed files and made the changes successfully.

But still wondering how the *.po files are created. They have very
regular format and each entry is commented with references to the lines
in c-files. That does not seem to be coded by the hand; all the *.po
files would be needed to be rewritten if a line would be inserted in one
of the c files referenced (what is actually the case with my personal
changes). Here is an example from de.po to illustrate what I am talking
about:

#: gnucash/gnome-utils/gnc-tree-model-split-reg.c:2856
#: gnucash/register/ledger-core/split-register.c:2486
msgid "Withdraw"
msgstr "Belastung"


Thanks in advance,
Paul

Am 29.04.2018 um 18:44 schrieb Paul Dest:
> Hi,
>
> I want to add own entries (e.g. "Paul") to the selection of predefined
> actions ("Increase", "Decrease", "Sell", "Buy" etc.) on a transaction split.
> (Rationale: I want to use the action as an additional select criterium
> for reports. Like the classes feature in Quicken; I mean not categories
> but classes - I'm aware that the Quicken's categories correspond to
> accounts in the double-accounting system.)
>
> After reviewing all configuration files, it seems to me that the
> predefined actions cannot be added to GnuCash after a build. Is that
> correct?
>
> If yes, then I have to make appropriate changes in code and rebuild
> GnuCash. A rebuld after additions in .po-files only seems not to have
> the desired effect.
> Could you please give an advice which files need to be edited for this
> change?
>
> Thanks in advance,
> Paul
>
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel