search

rufuscoder / Shakespeer

A Direct Connect Client for Multiple Platforms
GNU General Public License v2.0
28 stars 13 forks source link

/np not working #58

Closed rufuscoder closed 11 years ago

rufuscoder commented 11 years ago

Original author: ddutc...@gmail.com (May 26, 2008 18:08:39)

What steps will reproduce the problem?

  1. Pretty Self Explanitory 2. 3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue: http://code.google.com/p/shakespeer/issues/detail?id=28

rufuscoder commented 11 years ago

From void...@gmail.com on May 27, 2008 05:09:32 This diff and updated np.scpt should fix this issue.

rufuscoder commented 11 years ago

From void...@gmail.com on May 27, 2008 05:14:54 Whoops I had an extra " in the script. This one fixes that.

rufuscoder commented 11 years ago

From hwa...@gmail.com on May 27, 2008 07:10:23 What was the problem? Was an exception thrown to the console?

Also, I'd prefer that you remove (rather than uncomment) code unless this is somehow a temporary workaround.

rufuscoder commented 11 years ago

From void...@gmail.com on May 27, 2008 07:15:00 I couldn't see why it wasn't working. I just rewrote it using the now playing script I've used previously in other things.

rufuscoder commented 11 years ago

From markus.m...@gmail.com on May 27, 2008 07:50:48 It was the AppleScript itself that broke after an iTunes update, I think.

rufuscoder commented 11 years ago

From flapane on May 27, 2008 11:36:07 here it never worked, it didn't simply return any message.

rufuscoder commented 11 years ago

From ddutc...@gmail.com on May 27, 2008 17:09:25 i can see how it works but, i have no idea how to recompile or compile... thanks though...

rufuscoder commented 11 years ago

From markus.m...@gmail.com on June 01, 2008 18:44:09 I just tried this with the latest source and iTunes 7.6.2 and it works just fine. However, commands does not work in private chats, they never have. Could someone confirm that this works in main chat?

rufuscoder commented 11 years ago

From hwa...@gmail.com on June 02, 2008 10:12:29 Is this fixed as of svn revision 405, Markus?

rufuscoder commented 11 years ago

From markus.m...@gmail.com on June 02, 2008 16:01:18 I haven't touched the actual applescript, 405 only implements it for private chats too. As I said, this works for me, we need testing by others to confirm that though.

rufuscoder commented 11 years ago

From hwa...@gmail.com on June 03, 2008 19:49:03 ddutchie or voidboi: is this issue occuring in the main chat or in private chat?

If no one provides exact steps to reproduce this, we're gonna have to close this ticket as worksforme.

rufuscoder commented 11 years ago

From ddutc...@gmail.com on June 03, 2008 23:33:56 What steps will reproduce the problem?

  1. when typing /np in mainchat or in private chat it does not run.

attached is a prog i wrote with the np code that was attached below, it basically gets the info and puts it on your clipboard. and you just have to command+v it into your main chat.

rufuscoder commented 11 years ago

From void...@gmail.com on June 14, 2008 19:35:48 hwaara: I'll check it out when I get back from WWDC.

rufuscoder commented 11 years ago

From flapane on July 08, 2008 14:09:37 I wrote a code that shows something like this: MacItunz 7.6.2 listening to: Aerosmith - I Don't Want to Miss a Thing (Armageddon) @ 128 kbps (4:56 min)

I already told it to Valknut dev, but it could finally close the /np problem on Shakespeer. It simply calls an applescript from a shell command, so we only need Shakespeer to show an output from a shell script like Valknut does, is it possible? It would become very customizable in this way, too.

rufuscoder commented 11 years ago

From markus.m...@gmail.com on July 08, 2008 15:57:42 Seems like the current script worked all along, but wasn't included when building from the command line. So release builds wouldn't have the script, which explains why it worked for me since I apparently only tested it in my debug build. Well, it has been fixed in r426.