Even while leaving the field! Yes, you had mentioned it earlier but for
some reason it slipped my mind that +Fmt was equivalent of +Set +Val...
I just want to get this approach to a logical conclusion since I started
out on it.
Could the problem be the "List" relation between Task and Tag?
: (setq T8 (db 'ttl '+Task "Item 8"))
-> {51}
: (print-task T8)
Item 8: [BLUE, RED, ALL]
-> "]"
: (request! '(+Tag) 'tsk T8 'nm (request! '(+TagNm) 'nm "RED"))
-> {55}
: (print-task T8)
Item 8: [RED, BLUE, RED, ALL]
-> "]"
:
Also any suggestion about getting a "val> bad message" error in the
"+Chart" approach?
Regards,
Kashyap
On Sun, Dec 8, 2019 at 10:56 AM Alexander Burger <a...@software-lab.de>
wrote:
> On Sun, Dec 08, 2019 at 10:15:54AM -0800, C K Kashyap wrote:
> > The unwanted side effect though is that the number of tags keeps
> doubling.
> > Looks like the Val function is called both when the "edit" button is
> > clicked and when "done" button is pressed. While I expected it to be
> called
> > when the "done" button was pressed but I am not sure why it is called
> when
> > "edit" is pressed.
>
> Not at all. As I wrote in the previous mail, these functions are called at
> every
> micro-transaction.
>
> > > is EXTREME overkill! You basically rewrite all task objects several
> times
> > > during any primitive GUI operation like key presses and refreshes.
>
> Just 'trace' stuff to see how much happens here :)
>
> Especially if JavaScript is enabled in your browser, these functions run
> even
> when leaving a field.
>
>
> > Anyway, it is not clear to my why the code results in
> > duplicate tags - but yes, feeling very optimistic :)
>
> Not clear to me either now. Perhaps due to the non-unique keys (I
> mentioned in a
> prev. mail)? Though 'request' will not create new ones all the time, just
> not
> clear *which* one it returns.
>
> ☺/ A!ex
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>
