erengy / taiga

A lightweight anime tracker for Windows
https://taiga.moe
GNU General Public License v3.0
2.1k stars 224 forks source link

HTTP parameters don't seem to work #94

Open rr- opened 9 years ago

rr- commented 9 years ago

I'm using the HTTP sharing feature.

Format string (EOLs added for readability):

playstatus=%playstatus%
&path=%folder%/%file%
&name=%name%

What I expected:

  1. First request

    playstatus=stopped
    path=Z:\hub\dl\Bleach + Movies + Specials\001-100\Bleach - 024 [Lunar][640x480][92E29967].avi
    name=Bleach
  2. Second request

    playstatus=updated
    path=Z:\hub\dl\Bleach + Movies + Specials\001-100\Bleach - 024 [Lunar][640x480][92E29967].avi
    name=Bleach

What I got:

  1. First request

    playstatus=stopped
    path=/Bleach - 024 [Lunar][640x480][92E29967].avi
    name=
  2. Second request

    playstatus=updated
    path=/
    name=

Version: 1.1.11

:boar:

rr- commented 9 years ago

While we're at it, let's say I've just watched an episode, a popup appears: "do you want to update?" to which I agree... or update my list manually. And for whatever reason, the update fails (MAL API changed, the Internet is down, whatever.)

Can we have a new event that is executed when the list is about to be updated? Like, updating. Listening to closed is too unreliable because it happens even if I don't agree to anything.

erengy commented 9 years ago

Taiga isn't aware of the full path, depending on the method used to retrieve the filename from the media player. In v1.2, I prioritized file-handle-based detection, which should take care of the issue with %folder%.

%name% is actually for the episode title; you need to use %title% for the anime title. It's confusing, but I decided to keep them as is for backward compatibility. The new variables menu in v1.2 should help, though:

variables-menu

When playstatus is updated, Taiga isn't aware of the filename (or pretty much anything) at all, which is why %file% is empty. I should take care of that.

As for your final suggestion, I do have some plans to make Taiga trigger various events, and have other parts of the application register for and respond to those events (e.g. announcements, notifications, API).