rejetto forum

Software => HFS ~ HTTP File Server => Beta => Topic started by: SilentPliz on July 31, 2010, 05:39:23 PM

Title: {.notify.}
Post by: SilentPliz on July 31, 2010, 05:39:23 PM
I tried the "notify" feature, I can hear the sound of the event when it occurs, but nothing is displayed visually.
I must activate/deactivate something in Windows? (XP SP3).

Or maybe it's a bug ... if anyone can confirm or not (?)
Title: {.notify.}
Post by: AniFran on August 01, 2010, 09:33:23 AM
Not sure, hear sound also, but nothing shows up. Win7 x64
Title: {.notify.}
Post by: rejetto on August 03, 2010, 11:58:23 AM
menu > debug > run script

type
{.notify|ciao.}
and save.

don't you get the balloon?
Title: {.notify.}
Post by: SilentPliz on August 03, 2010, 12:01:15 PM
No, just a "plop" sound.
Title: Re: {.notify.}
Post by: rejetto on August 04, 2010, 10:35:42 AM
1. do you know if balloons are working correctly for other programs on your computer?
2. what windows version are you using? mine is W7 pro 32.
3. are you testing my build or your own?
Title: Re: {.notify.}
Post by: SilentPliz on August 04, 2010, 10:58:23 AM
1. do you know if balloons are working correctly for other programs on your computer?
2. what windows version are you using? mine is W7 pro 32.
3. are you testing my build or your own?

1 - Yes it work with other programs.
     If you know what files are necessary under Windows,
     I can compare the dates between my version and yours.
2 - Win XP pro 32 (SP3)
3 - both with the same result
Title: Re: {.notify.}
Post by: SilentPliz on August 04, 2010, 01:02:11 PM
Ok fixed !  ;)

The programs that worked correctly, included their own balloon system.
I had disabled the Windows balloons tips (Shame on me or Peace on me (?))

I have attached 2 screenshot about this option in Win XP, in French only, sorry.

Sorry for the inconvenience.
Title: Re: {.notify.}
Post by: rejetto on August 04, 2010, 01:15:34 PM
i guess/hope anifran had the same problem
Title: Re: {.notify.}
Post by: SilentPliz on August 04, 2010, 01:21:17 PM
Anifran uses the same OS as you ... perhaps you will find the good option before he finds it.  :D ;)
Title: Re: {.notify.}
Post by: rejetto on August 04, 2010, 03:12:43 PM
I don't mean to find it.

So, do you like this feature?
Title: Re: {.notify.}
Post by: SilentPliz on August 04, 2010, 04:11:28 PM
Yes I like these balloons! 8)

I used untill date, internally with HFS, the JVDesktopAlert (JEDI JVCL), and Growl, externally.

Your choice is a good choice, I will totally replace the JEDI alert version by yours. But not right away, I'm a bit tired. :P

For now the two possibilities will coexist into the "HFS VF".
Title: Re: {.notify.}
Post by: sequestrum on August 04, 2010, 05:01:57 PM
All these features that you never even know exist, even after using the software for two years and browsing the wiki for hours, heh.

I thought I'd try this, since I'm interested in getting some kind of notification whenever something is uploaded to the server. I wanted to make sure that everything was set up properly first though, so I tried this:
menu > debug > run script
type
{.notify|ciao.}
and save.

I get this error message though:
Quote
<div class=macroerror>macro error: notify<br>not supported or illegal parameters</div>

I get it with both build 260 and 265. I'm guessing there's some setting somewhere that needs to be enabled? I couldn't find anything that looked relevant in the options menu though (the closest I came was the "Enable macros" one under HTML template, but that's already enabled), and I didn't find anything about it in the wiki or the forum either. Any help would be appreciated.
Title: Re: {.notify.}
Post by: SilentPliz on August 04, 2010, 05:23:14 PM
"notify" exists only since version 263 of HFS, so it's normal that you have seen this macro error with 260.

You should not have it with version 263, 264, 265 ... or it works or it does not work that's all.

What OS you use?
Title: Re: {.notify.}
Post by: sequestrum on August 04, 2010, 07:20:35 PM
Ah, false alarm. I just trusted the updater to work, but I never double checked. Apparently the updater failed to update my version, so I was still using build 260. Sorry about not noticing that.