Developers | Forum profile

WOL is not an issue because you use standby, not shutdown, the server preserves the value over that. Little sense in WOL if you have to wait four minutes until your server is fully up and running.

Quote: Originally Posted by bhaagensen as I see it, is that the formal as well as informal conditions for the 3. party developers has not improved, and is in fact getting worse, or in danger of getting so. Do you (or anyone else) see any way Logitech could improve this without spending too much resources on it ? (Besides what have already been mentioned in the initial posts of the thread) As Ben said, there are Logitech people reading this...

I have a jive menu that needs to relect the change in the radio (check) status. I can confirm it works by manually changing the value in the called routine and then firing $request->setStatusDone(); My problem though is that I have an asyncronous routine that runs and after it completes I need to set the new value. I have tried various techniques and none seem to cause anything to happen. I have a global variable that contains the state...

Quote: Originally Posted by erland I'm not saying that there aren't any bugs, but it does work also as alarm clock, at least for me. Ah, well I've seen 'Radio-specific' bugs about alarms, but didn't look too closely at what they are. My old SB2 works great as an alarm clock and even looks like one. The 'interesting' bug is the one about compilation albums selecting the wrong track. That one is...

Yes you're right. Still I'd like a persistant time stamp.

Quote: Originally Posted by pippin WOL is not an issue because you use standby, not shutdown, the server preserves the value over that. Little sense in WOL if you have to wait four minutes until your server is fully up and running. Unless you have a crappy old server that won't S3 suspend properly, or won't wake from S3 without crashing. And that crappy old server is probably an energy hog anyway, so a crappy server owner might feel...

Quote: Originally Posted by andynormancx By which time the SB3 had been on the market for two years, by the time the Touch has been on the market for two years it is likely to be the same street price as your SB3 was two years after launch. Fair comment - and in truth it's still one of the cheapest workable options today. Dave

Quote: Originally Posted by snarlydwarf guess if you have enough predictions about the future, you'll eventually be right. There's only been one prediction. Clearly an emotive topic for you Snarly, so I'll zip it lest you pop a clog.

Quote: Originally Posted by erland I've probably forgotten a lot, so please post everything I've forgotten and more important post new ideas which haven't been mentioned yet. Maintain a list of cool stuff that has been asked for but you don't want to implement yourself. 3rd party devs with no ideas thus would get new ones and might even start implementing it. If some of them get developed you can even prove business value...

Hi, I've got a line of code in my applet that appears to be interpreted incorrectly by the duet controller but works in desktop SquuezePlay. The line looks like this Code: log:info(tonumber("0x80000023", 16) & 0x7FFFFFFF) Desktop SqueezePlay 7.4r0 returns 35 (= 0x23) which is the right answer. Duet controller 7.4.1 r7915 returns 2147483647 (= 0x7FFFFFFF) which is wrong. I have used bitwise operands elsewhere in...