Tags support

[Jack]

Sorry - my fault on that last one.  Once you said Windows 10, I know  
there's only one current installer.  It's also possible there is some  
issue with Windows 10, but I'm guessing it's more likely related to the  
database code.  However, I think it's actually good to know that the  
database back end does work on Windows.  I don't recall anyone  
confirming that in the past.

Jack

On 2016.03.09 12:11, Phil Richardson wrote:
> The binary installer download from the KMM site. So not compiled from
> source.
> 
> I will attempt to apply the tag manually this evening, when I work  
> out the
> schema specific to the tags.
> 
> On 9 March 2016 at 15:59, Jack <ostroffjh at users.sourceforge.net>  
> wrote:
> 
> > Using the file backend, can you apply a tag to a split  
> transaction?  If
> > so, then it is possible that the issue is related to the database  
> backend.
> >
> > (I don't think it matters here, but when you say site release, do  
> you mean
> > compiled from source, or installed through your distribution?)
> >
> >
> >
> > On 2016.03.09 02:23, Phil Richardson wrote:
> >
> >> Windows 10
> >>
> >> I have converted back to a flat file structure from a MySQL DB in  
> the KMM
> >> upgrade.
> >>
> >> KMM  is 4.7.2 direct from the site release.
> >>
> >> On 9 March 2016 at 00:55, Jack <ostroffjh at users.sourceforge.net>  
> wrote:
> >>
> >> > That's very strange.  I actually did test before I replied, just  
> in
> >> case I
> >> > was mistaken, and I just tried again to confirm.  What version  
> of KMM
> >> are
> >> > you using, what OS/distro, and where did you download the package
> >> (distro
> >> > repository, compile from source, other...)?
> >> >
> >> >
> >> > On 2016.03.08 17:33, Phil Richardson wrote:
> >> >
> >> >> Hi Jack and Christian,
> >> >>
> >> >> Thanks for your responses.
> >> >>
> >> >> Good to know this problem is recognised.
> >> >>
> >> >> Jack,
> >> >>
> >> >> I had meant to raise this email several days ago, but refrained  
> when I
> >> >> noticed the way in which tags show to the side, so wanted to  
> explore
> >> the
> >> >> problem further before reporting.
> >> >>
> >> >> However, the tags show to the side on a normal transaction, but  
> not on
> >> a
> >> >> split one.
> >> >>
> >> >> On split and non-split transactions, I can type a tag in. But  
> it will
> >> only
> >> >> show to the side of a non-split.
> >> >>
> >> >> If I submit the edited transaction, it will suggest it has gone  
> in, but
> >> >> editing it again show no tag, the tags tab shows no transaction  
> in the
> >> >> embedded ledger, and the transaction list on the account shows  
> not
> >> "(tag)"
> >> >> in brackets.
> >> >>
> >> >>
> >> >>
> >> >> On 8 March 2016 at 22:20, Jack <ostroffjh at users.sourceforge.net>
> >> wrote:
> >> >>
> >> >> > On 2016.03.07 02:55, Phil Richardson wrote:
> >> >> >
> >> >> >> So I finally bit the bullet and upgraded, which was not easy  
> as it
> >> >> >> involved
> >> >> >> a couple of OS upgrades as well. I mainly did so for tag  
> support.
> >> >> >>
> >> >> >> However, I am disappointed by it.
> >> >> >>
> >> >> >> It seems you can only tag transactions that are not split?
> >> >> >>
> >> >> >> Why is this?
> >> >> >>
> >> >> >> The features to tag them is present and your selection can  
> be made,
> >> >> only
> >> >> >> the the transaction to remain tag'less.
> >> >> >>
> >> >> >> I would add something to Christian's reply.  You can tag
> >> transactions
> >> >> > which have multiple splits.  However, the tag can be applied  
> only to
> >> the
> >> >> > whole transaction, not to an individual split.
> >> >> >
> >> >> > In addition, note that after you apply the tag by typing in  
> (or
> >> >> selecting
> >> >> > from) the dropdown, the dropdown does go blank again, since  
> you can
> >> add
> >> >> > more than one tag to a transaction.  Once you add a tag, it  
> is noted
> >> to
> >> >> the
> >> >> > right of the dropdown.  Is it possible you just didn't notice  
> the
> >> tag,
> >> >> > since it was in a place you didn't expect to see it?
> >> >> >
> >> >> > Jack
> >> >>
> >> >>
> >> >
> >>
> >>
> >
>