2016-01-19 GnuCash IRC logs
01:12:53 *** Mechtilde has joined #gnucash
02:07:32 *** Mechtilde has quit IRC
02:15:53 *** Loki has joined #gnucash
02:17:09 *** Loki has left #gnucash
02:49:56 *** autoditac__ has joined #gnucash
03:45:47 *** nomeata has joined #gnucash
03:53:07 *** karelk has joined #gnucash
04:18:10 *** fabior has joined #gnucash
06:10:36 *** MoeD has quit IRC
06:11:17 *** MoeD has joined #gnucash
07:03:01 *** Jimraehl1 has left #gnucash
07:08:01 *** Jimraehl1 has joined #gnucash
07:08:32 *** fabior has quit IRC
07:19:47 *** Guest89 has joined #gnucash
07:29:11 *** Guest89 has quit IRC
07:38:48 *** finster has quit IRC
08:45:30 *** uXus has quit IRC
08:53:11 *** uXus has joined #gnucash
09:09:12 *** fabior has joined #gnucash
10:34:39 *** rubdos has joined #gnucash
11:04:07 *** nomeata has quit IRC
12:20:26 *** Mechtilde has joined #gnucash
13:33:14 *** autoditac__ has quit IRC
13:35:15 *** autoditac__ has joined #gnucash
14:02:32 *** fabior has quit IRC
14:08:37 *** BuschMan has joined #gnucash
14:16:18 *** Mechtilde has quit IRC
15:20:50 *** fabior has joined #gnucash
15:22:08 *** nomeata has joined #gnucash
17:01:24 *** nomeata has quit IRC
17:37:45 *** LeaChim has joined #gnucash
17:39:30 <LeaChim> I'm hitting a rather weird bug. Opened up gnucash today, and one of my accounts is missing from the `Accounts` page. If I run the `Account Summary` report, I can see it, and click through to it. And it appears in splits and so on - just not on the main screen
17:41:38 * LeaChim sighs. And apparently the rubber ducking phenomenon strikes again. (Going to check the view options, try making it show zero total accounts, and it appears - because a scheduled transaction from the future was round the wrong way exactly cancelling it out)
17:42:09 <LeaChim> So - not a bug. But thanks for the place to type out my question and figure out the problem! :p
18:03:04 *** fabior has quit IRC
18:56:05 *** elepercq has joined #gnucash
19:39:47 *** elepercq has quit IRC
20:02:26 *** GnuGuest has joined #gnucash
20:09:08 <GnuGuest> There are 2 similar qof_collection_* methods/functions: qof_collection_insert_entity and the other is qof_collection_add_entity.
20:13:00 <GnuGuest> *_insert_entity removes the entity from its collection (from its member pointer) and then inserts it into another collection and it changes the member pointer of the entity appropriately.
20:16:58 <GnuGuest> *_add_entity checks using the entity's GUID if the entity already exists in the destination collection and only insert it into the destination collection without manipulating the member pointer of the entity.
20:21:10 <warlord> GnuGuest: yes, they perform slightly different tasks. This is important during load mechanisms because one can have "proto-objects", when an object is created due to a reference before the object itself is read in.
20:21:20 <warlord> (gotta run)
20:23:48 *** autoditac__ has quit IRC
20:28:18 <GnuGuest> Thanks, warlord.
20:32:20 <GnuGuest> There are two main places where *_add_* is used and they are "Invoices" and "References".
20:36:38 <GnuGuest> The "proto-object" for References makes sense and to some degree I am still trying to substantiate how this applies to Invoices, as *_add_* is used to put "Entries" into a collection for the Invoice.
20:43:30 <GnuGuest> One way that I have looked at this is noting a comment that said that *_insert_* is used mostly for *moving* an entity/instance from a source Book collection to a destination Book collection. In this case, both source and destination Book objects must be complete objects. In the *_add_* case, this does not have to be the case.
20:49:17 *** LeaChim has quit IRC
20:52:36 <GnuGuest> So the use of *_add_* in the two cases mentioned above seems okay for now, but some more details is needed to make this clearer.
20:57:48 <GnuGuest> There is a problem when it comes to the "load" semantics, because what seems to be happening here is that there is a pre-existing old-book and the creation of a new-book, then the backend from the old-book is switched to the new-book before the load takes place.
21:01:00 *** Guest89 has joined #gnucash
21:06:28 <GnuGuest> So the load starts loading all these objects into *new-book*, but then they are *_insert_*ed into the *new-book* again. Is this really the case, because this means that the load semantics could be greatly optimized if one uses the *_add_* instead of *_insert_*.
21:09:32 <GnuGuest> ... or if *_insert_* checks if the destination and the source collections are the same and skips the actual *removing* and *inserting* into the same collection.
23:40:42 *** Coderjoe has quit IRC
23:46:08 *** Coderjoe has joined #gnucash
23:51:01 *** Guest89 has quit IRC