Feedback - how on earth do I do this?

[Mastiff]

OK, I'm totally lost her. Where do I put the LUA thingy? It does not show up as a plug-in in Girder (which of course only dll-files do anyway), so how do I do this? I want to do a simple variable manipulation script - the original script with the old feedback method is this:

songname = strsub(songname, 15, strlen(songname) -1 )

First I get the caption from MC, and basically all this does is to adjust the caption (remove the Media Center-part and the paranthesis so I'm left with only the zone name as songname), and than that gets sendt to NetRemote from the Internet Event Client. But how do I do this the new way?

Hope somebody can help me here, this time I'm really confused! :oops:

[brockgr]

Tor,

Sorry, it is a rather liberal use of the word "Plugin" - the LUA stuff does not show up anywhere - it's just loaded at Girder start time (and script reset time). Perhaps it would be better called a "feedback API for Girder variable scripts"

Anyway, you are getting the variable "songname". You no longer need the Internet event client. You just need to add the following to your "variable manipulation script":


NetRemote.SendLabel("BUTTONNAME", songname)

Where BUTTONNAME is the name of the button you want to set teh label for.

Hope this helps.

Gavin

[Mastiff]

Thanks for answering, Gavin! Well, I'm not all there yet. How do I load this API? I get "Parse error" when I run the script, and my guess is that it's because I am not loading the API. Thanks again! 8)

[brockgr]

Okay - make sure you have the "Girder Events" plugin (a real plugin this time) installed and enabled. This is the glue code that tells girder to load the LUA code!

If you are still getting parse error, try running your script with the script editor window open and check what appears in the bottom frame.

Cheers,

Gavin

[Mastiff]

Thank you for your patience! What's the time in Tokyo now anyway? It's close to 11 A.M. here. :D
I have no plugin called Girder events, but I do have things that reacts when Girder starts (Girderopen) and exits, so that is what I need, right? I downloaded your LUA DVD Jukebox and imported the GML, so I think the LUA functions are initialising. I even tried to initialise manually, but got exactly the same answer.

Here's the information:

error: attempt to index global `NetRemote' (a nil value)
stack traceback:
1: main of string "?" at line 2

I'm sure this is an idiot mistake on my part, so we'll solve it.

[brockgr]

It's 7pm here - just leaving work now.

Anyway you need this Girder plugin:
http://prdownloads.sourceforge.net/girderplugins/LUAEvents.1.0.0.zip?download

I assume you have copied the feedback .lua file to the Girder/lua directory. Just restart with the new plugin enabled.

Your error is basicly saying "I don't know about this NetRemote object" - i.e. the API is not loaded.

Gavin

[Mastiff]

Thanks a lot, Gavin! Works like a charm now! After I had downloaded Girder 3.2.9, that is. I was still on 3.2.8 and could not get the plugin to fire. So I tried to read the "friendly" manual, or the readme file with the plugin, and with 3.2.9 I got my zones back. So thanks again! :D

[Mastiff]

Darn (that wasn't the original word, but I decided against my first word...), I'm back in the swamp again! I don't know that I have changed anything on my system, but suddenly I get this message:

error: attempt to call field `SendLabel' (a nil value)
stack traceback:
1: main of string "?" at line 1

So feedback is not working...again. Can anybody help me? What's the time in Tokyo now? :lol:

[brockgr]

Sorry - no idea!! What is the code you have now - could you post it?
I assume you have tried restarting Girder just to check it hasn't got unhappy.

Gavin

[Mastiff]

Gavin, it's the same code as in the beginning of the thread, with sending the title of the MC9 window as Sone (zone in norwegian) to the PPC. And I also tried the LUA Feedback Examples, and even without the PPC on I get "Parse error" and this message in the script debugging window:

error: attempt to call field `SendLabel' (a nil value)
stack traceback:
1: main of string "?" at line 1

And yes, I have restarted Girder, the computers (I have exactly the same problem on two computers with similar setup) and NetRemote. Thanks for your patience, I'm not about to give up!

[Mastiff]

The problem is solved! It turned out to be caused by me loading registers from a file when I open Girder. I use this playlist selector GML (you might have seen or heard about it) so I can press 0-9, up to four digits on any IR remote and start the CD with that number in the zone that IR remote is programmed for. And I also have a function for next playlist and previous playlist (sometimes I want to listen to the collective works of...say Iron Maiden). But when I have to reboot (which happens more and more seldom) I loose that "next play list" option, it will always start at play list 1. So I saved the register settings on Girder close and reloaded them on Girder startup. This obviously messed up something, since when I disabled that by accident, NetRemote feedback worked perfectly. I have no idea why this happens, probably some kind of bug. It's the common "Save Reg." in the Girder group of the lower right command part of Girder, and then "Load Reg." on restart. They are now eradicated from my GML's.

So thanks a lot to Gavin for helping me out (we did most of the work on e-mail)! 8)

[Eiffel]

I have gotten to the point where NetRemote (.99 rc3) communicates both way with MC9.0, and got the slider and the 'Hello Girder' demos to work... but I can't get Girder to send orders to the Netremote client. I don't get any error message but nothing happens. I've tried functions such as NetRemote.SendLabel("BUTTONNAME", test), NetRemote.GotoDevice(), etc...

I am not sure what is wrong (Could it be that the port that the client should listen to is not set properly, could it be a password or other setting issue on either the Girder or NR side... )

Thanks for your suggestions

[esajesa]

Hey all,

I get an error message when I initialize the Netremote feedback.lua script. It says the following:

Loading NetRemote Feedback.lua
error: attempt to call a nil value
stack traceback:
1: function `AddEventHandlerName' [C]
2: main of file `...ogram Files\girder32\LUA\NetRemote Feedback.lua' at line 45
LOAD


And that's it. I can't get girder to talk back to my netremote. When I look in the script I think I understand the following:

Pld1 should be the IP address of the Netremote client.
Pld2 should be the listening port, ie 1023.

Neither of these variables are defined when I look in the script editor.

But if I keep the script logger/editor open when I start Netremote, I get the IP address and all, it doesn't seem to stick into the variables though if I open it up and check.

So, in conclusion, girder/lua seem to get the IP address, but when I send something off, it won't go through.

For your error handling purposes, I've used all the default files, and I'm on Girder 3.2.9 and Netremote 0.982.

Cheers guys, and thanks for all your great help!!

//Jens

[brockgr]

Jens,

Dif you ever get anywhere. I have just released a new feedback release. This should have examples that work with the current (RC3/4) releases of NetRemote. Maybe that will help.

Anyway, ignore that "attempt to call a nil value" error. It's a bug todo with the LUA Events Plugin, but does not cause any problems.

Cheers,

Gavin

[esajesa]

Phuh, call me stupid, but I just can't get this to work.

Ok, let me tell you what I've done. I've downloaded the new files, put the lua script in the girder32\lua directory, started girder and reloaded the script.

Then start Netremote, change to the brand new ccf. I restart ccf, and girder receives the NR.RESEND and all that stuff. I even check with the script editor, and see it receives the IP address of the ppc. Everything seems cool.

On the Netremote screen, the buttons are there, with the labels {TEST_LABEL_1} etc. If I do the Test Command on the "Set A Label" command in girder, girder says "Ok: Result was 0", and that's it. Nothing happens in Netremote. Am I right in how I do things?

When I read your and others posts I see something about RC3/4. I've got NR 0.982, and that's it. I also saw somewhere, and I'm not sure about this, that if NR is realizing the {TEST_LABEL_1} is a variable, you shouldn't see the brackets in NR. Is that correct?? If so, could it be that I have the wrong version of NR? Is there somewhere I can download a newer version. I have a feeling that this might be the case, cuz people keep talking about "the old 0.982 Netremote", but I can't find anything newer...

Please Gavin, help me, I'm pulling my hair here! :) Is there any tools to help me debug or something?

Oh, btw, more info for your convenience: The plugins I have enabled in Girder are:

Internet Event Server (works well for receiving calls.. using port 1024)
LUA Events (Version 1.0.0 Device nr 77, API Ver 2)
Lua-socket Library (Version 1.0 Device nr 55 Ver 2)
Send Message (shouldn't make a difference here)

In NR I've set the listen port in GirderDriver to 1023. I've also tried other ports, but it doesn't seem to make a difference.

I've also played around with different Timeout values.

One more question, is the NetRemote emulator (W32 version) supposed to work with this? I've tried both that, and the PPC versions though.

Please Gavin, help me, I'm pulling my hair here! :) Is there any tools to help me debug or something?

Thanks a bunch,
Jens

[brockgr]

Jens,

I think you are correct in everything you say in your mail :lol:. Your number one problem is your netremote version.

Get the newest version (0.99rc4) from here http://www.netremote.org/phpBB2/viewtopic.php?t=176&start=45 See if that helps.

Also one gotcha - this does not wokr with an activesync network connection. You must have a real network, wifi or bluetooth connection. (Reason is that Activesyn NAT's so your PPC does not have a real IP address).

Gavin

[esajesa]

Hey Gavin,

once again, thanks a bunch for all your help! Today I'm a little bit closer. But I'm not quite there. Here's what happens:

When I start Netremote, I can see for the first time that the lua script is actually registering the IP address and port number. Funny enough, once the first registration is done, it just keeps on coming. Seems like the NR.REGISTER event is constantly being sent to girder or something, because the green light in Girder blinks like crazy! And in the script "debug" window it keeps on saying "Registering 192.168.0.203:1023", perhaps once every 1-2 seconds. It never stops. It actually hangs girder more or less, because girder gets stuck with the script.

Sooo, to do some troubleshooting of my own, I added a couple of lines in the lua script, and after that I can conclude that the first time it receives the NR.REGISTER event, it goes through the whole thing perfectly. Then it just seems to get stuck in the same place.

Well, this doesn't work very well as you understand, so I figured, perhaps it's a timeout thing. I've played with both the timeout value in Netremote and the timeout value in the script, but it doesn't seem to make much of a difference.

I guess perhaps I should tell you that I'm running on an iPaq 3970 via bluetooth.

cheers,
Jens

[brockgr]

Yes I have seen this - I suspect we may have a bug somewhere (I loathed to blame NetRemote without more evidence). I usually end up resarting everything to clear this up.

I'll see if I can reproduce this at home.

Gavin

[Mastiff]

Jens, can it be the IP address? I have found that PPCs do not like being anything above 99, but I have no idea why.

[esajesa]

Hey again,

well no luck yet. Been playing around a bit more with timeouts, reinstalling etc, but nothing changes. I've done it all on two different PCs as well, but I get the same problem. Perhaps I'm doing something fundamentally wrong, I don't know.. :)

This is what I get in the script window:

Example Event Logger:
203
Incoming connection
192.168.0.100
Example Event Logger:
203
Accepted connection
192.168.0.100
Registering 192.168.0.100:1023
Connected
Registering 192.168.0.100:1023
Connected
Registering 192.168.0.100:1023
Registering 192.168.0.100:1023
Registering 192.168.0.100:1023
Registering 192.168.0.100:1023

And then it just continues... I did try with different IP addresses, but no
luck. Seems to me like the event keeps coming from Netremote, and it just never stops, unless I kill Netremote of course.

What I've noticed is that I need to increase the timeout either in Netremote, or the script for Girder to get back with the Connected message. But once it's connected, it starts pushing the Registering... event once every 1-2 seconds or so.

I did remove Netremote from my ppc and reinstalled it with the RC2 installer, then upgraded to the RC4, but still the same. Also tried different port numbers.

Getting annoyed now, I'm so close and this is like the last part of my truly to be cool HTPC project, so I'm dying to get it to work!

Cheerio guys,
Jens

[esajesa]

...forgot to tell u that my win32 version and everything is working like clockwork, it's just the ppc I can't get working..

/Jens

[brockgr]

Ok - I just played with rc4 in my iPAQ and am not having this problem. Well not reproducably yet. I get a back log of messages when the iPAQ connects, as if the cocket is not being polled for a while after connecting, but then it clears up.

I know it's stupid - but double check that your Girder Plugin settings are exactly the same on both platforms.

Gavin

[Ben S]

If you didn't see the "registering" message, I would assume that it was a problem connecting, because the girder driver will keep attempting to connect until it gets one. That -looks- like what's happening.

Was is your timeout set to? The timeout on the pocket pc must be significantly larger than the Win32 timeout, I've noticed.

Can you try "telnetting" into the ppc's listen port? IE: telnet [ppc IP address] 1023.

We'll figure this one out yet, Jens!

[esajesa]

... on the subject. Guess what? Today, it actually worked for me. Once. Then never more.

the ppc does answer on telnet. The settings are correct.. Anyway, about the timeouts.

What effect does the timeout in Netremote Girder driver have for feedback? I know I have to increase it quite a bit for Girder to accept messages properly, but what does it do when it receives something?

The it's the timeout in the LUA script. Changed it back and forth a bit, doesn't really see much of a difference except that girder gets a bit slower if I increase it.

I also do see the registering message. As many times as I want actually, it just never ends!! hehe..

Phuh, I'm soon giving up. Thanks for your help though, without it I'd given up long ago. Still there's hope!!

Jens

[esajesa]

Hey guys... well, I'm nowhere closer to a solution, except perhaps taking $200 and go and buy myself a wi-fi router and stuff, but I figured I'd give you the logs I get.. So prepare for a huge post.

First, the one I get when I use the win32 client, and it works just fine:

22:52:34 Monday, May 19, 2003 EVENT: Dev: 203 NRCLIENT.REGISTER Pld1: 192.168.0.1 Pld2: 1023
22:52:34 Monday, May 19, 2003 LUA: return Lua GirderRegisterNRClient global
22:52:34 Monday, May 19, 2003 LUA: --> return Lua Register field
22:52:34 Monday, May 19, 2003 LUA: --> --> return Lua SyncState field
22:52:34 Monday, May 19, 2003 LUA: --> --> call Lua SyncState field
22:52:34 Monday, May 19, 2003 PRINT: Connected
22:52:34 Monday, May 19, 2003 LUA: --> --> return C receive field
22:52:34 Monday, May 19, 2003 LUA: --> --> call C receive field
22:52:34 Monday, May 19, 2003 LUA: --> --> return C send field
22:52:34 Monday, May 19, 2003 LUA: --> --> call C send field
22:52:34 Monday, May 19, 2003 LUA: --> --> return C receive field
22:52:34 Monday, May 19, 2003 LUA: --> --> call C receive field
22:52:34 Monday, May 19, 2003 LUA: --> --> return C send field
22:52:34 Monday, May 19, 2003 LUA: --> --> call C send field
22:52:34 Monday, May 19, 2003 LUA: --> --> return C timeout field
22:52:34 Monday, May 19, 2003 LUA: --> --> call C timeout field
22:52:34 Monday, May 19, 2003 LUA: --> --> return C connect global
22:52:34 Monday, May 19, 2003 LUA: --> --> call C connect global
22:52:34 Monday, May 19, 2003 PRINT: Registering 192.168.0.1:1023
22:52:34 Monday, May 19, 2003 LUA: --> call Lua Register field
22:52:34 Monday, May 19, 2003 LUA: call Lua GirderRegisterNRClient global
22:52:34 Monday, May 19, 2003 LUA EVENTS: 'Name' type event processing using: 'GirderRegisterNRClient'
22:52:34 Monday, May 19, 2003 EVENT: Dev: 203 Accepted connection Pld1: 192.168.0.1
22:52:34 Monday, May 19, 2003 LUA: return Lua ExampleEvent global
22:52:34 Monday, May 19, 2003 PRINT: 192.168.0.1
22:52:34 Monday, May 19, 2003 PRINT: Accepted connection
22:52:34 Monday, May 19, 2003 PRINT: 203
22:52:34 Monday, May 19, 2003 PRINT: Example Event Logger:
22:52:34 Monday, May 19, 2003 LUA: call Lua ExampleEvent global
22:52:34 Monday, May 19, 2003 LUA EVENTS: 'Name' type event processing using: 'ExampleEvent'
22:52:34 Monday, May 19, 2003 EVENT: Dev: 203 Incoming connection Pld1: 192.168.0.1
22:52:34 Monday, May 19, 2003 LUA: return Lua ExampleEvent global
22:52:34 Monday, May 19, 2003 PRINT: 192.168.0.1
22:52:34 Monday, May 19, 2003 PRINT: Incoming connection
22:52:34 Monday, May 19, 2003 PRINT: 203
22:52:34 Monday, May 19, 2003 PRINT: Example Event Logger:
22:52:34 Monday, May 19, 2003 LUA: call Lua ExampleEvent global
22:52:34 Monday, May 19, 2003 LUA EVENTS: 'Name' type event processing using: 'ExampleEvent'


Then from my ppc:

22:49:54 Monday, May 19, 2003 LUA: --> return Lua Register field
22:49:54 Monday, May 19, 2003 LUA: --> --> return C connect global
22:49:53 Monday, May 19, 2003 LUA: --> --> call C connect global
22:49:53 Monday, May 19, 2003 PRINT: Registering 192.168.0.115:1023
22:49:53 Monday, May 19, 2003 LUA: --> call Lua Register field
22:49:53 Monday, May 19, 2003 LUA: call Lua GirderRegisterNRClient global
22:49:53 Monday, May 19, 2003 LUA EVENTS: 'Name' type event processing using: 'GirderRegisterNRClient'
22:49:53 Monday, May 19, 2003 EVENT: Dev: 203 NRCLIENT.REGISTER Pld1: 192.168.0.115 Pld2: 1023
22:49:53 Monday, May 19, 2003 LUA: return Lua GirderRegisterNRClient global
22:49:53 Monday, May 19, 2003 LUA: --> return Lua Register field
22:49:53 Monday, May 19, 2003 LUA: --> --> return C connect global
22:49:52 Monday, May 19, 2003 LUA: --> --> call C connect global
22:49:52 Monday, May 19, 2003 PRINT: Registering 192.168.0.115:1023
22:49:52 Monday, May 19, 2003 LUA: --> call Lua Register field
22:49:52 Monday, May 19, 2003 LUA: call Lua GirderRegisterNRClient global
22:49:52 Monday, May 19, 2003 LUA EVENTS: 'Name' type event processing using: 'GirderRegisterNRClient'
22:49:52 Monday, May 19, 2003 EVENT: Dev: 203 NRCLIENT.REGISTER Pld1: 192.168.0.115 Pld2: 1023
22:49:52 Monday, May 19, 2003 LUA: return Lua GirderRegisterNRClient global
22:49:52 Monday, May 19, 2003 LUA: --> return Lua Register field
22:49:52 Monday, May 19, 2003 LUA: --> --> return Lua SyncState field
22:49:52 Monday, May 19, 2003 LUA: --> --> call Lua SyncState field
22:49:52 Monday, May 19, 2003 PRINT: Connected
22:49:52 Monday, May 19, 2003 LUA: --> --> return C receive field
22:49:37 Monday, May 19, 2003 LUA: --> --> call C receive field
22:49:37 Monday, May 19, 2003 LUA: --> --> return C send field
22:49:37 Monday, May 19, 2003 LUA: --> --> call C send field
22:49:37 Monday, May 19, 2003 LUA: --> --> return C receive field
22:49:22 Monday, May 19, 2003 LUA: --> --> call C receive field
22:49:22 Monday, May 19, 2003 LUA: --> --> return C send field
22:49:22 Monday, May 19, 2003 LUA: --> --> call C send field
22:49:22 Monday, May 19, 2003 LUA: --> --> return C timeout field
22:49:22 Monday, May 19, 2003 LUA: --> --> call C timeout field
22:49:22 Monday, May 19, 2003 LUA: --> --> return C connect global
22:49:22 Monday, May 19, 2003 LUA: --> --> call C connect global
22:49:22 Monday, May 19, 2003 PRINT: Registering 192.168.0.115:1023
22:49:22 Monday, May 19, 2003 LUA: --> call Lua Register field
22:49:22 Monday, May 19, 2003 LUA: call Lua GirderRegisterNRClient global
22:49:22 Monday, May 19, 2003 LUA EVENTS: 'Name' type event processing using: 'GirderRegisterNRClient'
22:49:21 Monday, May 19, 2003 EVENT: Dev: 203 Accepted connection Pld1: 192.168.0.115
22:49:21 Monday, May 19, 2003 LUA: return Lua ExampleEvent global
22:49:21 Monday, May 19, 2003 PRINT: 192.168.0.115
22:49:21 Monday, May 19, 2003 PRINT: Accepted connection
22:49:21 Monday, May 19, 2003 PRINT: 203
22:49:21 Monday, May 19, 2003 PRINT: Example Event Logger:
22:49:21 Monday, May 19, 2003 LUA: call Lua ExampleEvent global
22:49:21 Monday, May 19, 2003 LUA EVENTS: 'Name' type event processing using: 'ExampleEvent'
22:49:21 Monday, May 19, 2003 EVENT: Dev: 203 Incoming connection Pld1: 192.168.0.115
22:49:21 Monday, May 19, 2003 LUA: return Lua ExampleEvent global
22:49:21 Monday, May 19, 2003 PRINT: 192.168.0.115
22:49:21 Monday, May 19, 2003 PRINT: Incoming connection
22:49:21 Monday, May 19, 2003 PRINT: 203
22:49:21 Monday, May 19, 2003 PRINT: Example Event Logger:
22:49:21 Monday, May 19, 2003 LUA: call Lua ExampleEvent global
22:49:21 Monday, May 19, 2003 LUA EVENTS: 'Name' type event processing using: 'ExampleEvent'



And then the red part just keeps on coming. Just fyi, hope it helps.

Cheers,
Jens

[Mastiff]

Jens, I'd go for a router! Try Komplett Data (it's in all the nordic countries (my guess is that you're Danish, or am I wrong?) and in England). Or you can buy a used one on QXL. Usually a lot cheaper. 8)

[brockgr]

Jens,

Great so see some debug. This is the right kind of stuff. Sadly, though it looks like things are working. :cry: Actually, it looks like there is too much data there - I'm not sure about some of those "PRINT" statements.

A couple of questions:

- Do you have the old style Girder feedback GML in your girder file? Since we moved to the "LUA Events", you just need the .lua file in your directory - nothing on the Girder GUI side.

- You look like you also have the "LUA Events" example .lua file loaded. Might just be worth removing that.

We must be able to beat this one.

Gavin

[esajesa]

hi again,

I'm not NAT'ng at all, I go straight over Bluetooth, Network Access. I'll check if it helps to delete the sample lua script tonight when I'm home from work.

And I'm only using the latest GML file, nothing else.

I'll get back after I've tested without the sample lua script!

Keep well dudes!

/Jens

[esajesa]

Hey guys,

no luck, it didn't change anything unfortunately... any ideas?

//Jens

[Ben S]

Hi Jens,
Can you wait and see if RC5 resolves the issue? Or at least gives us a stable base to start from again?

Don't lose hope!

[esajesa]

Of course I'll wait for RC5! Any idea of when ur releasing it?

//Jens

[Mastiff]

That really seems to be the question of the day... Maybe it helps to threaten him? Usually I beg, and that works sometimes, but as of this...nope. :roll:

[esajesa]

*threaten threaten*!!! OR, if it happens soon, I'll buy you a beer whenever you're around Stockholm or so... :))

[Ben S]

Uh oh! Now I'm in trouble!

I will release RC5 this weekend. I have one bug to track down relating to Media Center, and then RC5 is what I believe to be stable enough for a public release.

Sunday end of day at the latest.

[Mastiff]

So that'll be Monday morning for Jens and me... OK, I can relax with the great battle tonight: Norway will beat the crap out of Denmark on the socccer field! :D

[Ben S]

What time is it in Norway? 6 o'clock here. And the software is available.

I wasn't going to release it, but all that threatening had me running scared! :)

[markus00]

Hello I'm new in this forum.

I have exact the same problem as esajesa.
Please help us!

/Markus

[brockgr]

Welcome Marcus,

Sorry, which problem is it you have? Things are evolving fast.

Just to confirm - you have NR 0.99 RC5 and the latest Girder?

Gavin

[markus00]

Yes I have NR 0.99 RC5 and Girder 3.2.9 with NetRemote Feedback 0.06

When I have the Girder opened and open Netremote.
The green "lamp" in Girder start to plink very fast and I see the text NRCLIENT.REGISTER

In the log I see this text:

09:42:17 Saturday, June 21, 2003 PRINT: Registering 192.168.0.102:5190
09:42:17 Saturday, June 21, 2003 LUA: --> --> --> call Lua Register field
09:42:17 Saturday, June 21, 2003 LUA: --> --> call Lua GirderRegisterNRClient global
09:42:17 Saturday, June 21, 2003 LUA EVENTS: 'Name' type event processing using: 'GirderRegisterNRClient'
09:42:17 Saturday, June 21, 2003 EVENT: Dev: 203 NRCLIENT.REGISTER Pld1: 192.168.0.102 Pld2: 5190
09:42:17 Saturday, June 21, 2003 LUA: --> --> return C connect global
09:42:17 Saturday, June 21, 2003 ALERT: 2: function `GirderRegisterNRClient' at line 49 [file `C:\Program\girder32\LUA\NetRemote Feedback.lua']
09:42:17 Saturday, June 21, 2003 ALERT: 1: method `Register' at line 83 [file `C:\Program\girder32\LUA\NetRemote Feedback.lua']
09:42:17 Saturday, June 21, 2003 ALERT: stack traceback:
09:42:17 Saturday, June 21, 2003 ALERT: error: attempt to call global `connect' (a nil value)
09:42:17 Saturday, June 21, 2003 LUA: --> --> call C connect global
09:42:17 Saturday, June 21, 2003 PRINT: Registering 192.168.0.102:5190


And the text is just reapeating until I close Netremote.

Help me please!

[markus00]

I have tried to change both the send port in netremote and the listening port with the same fault.

I use LUA Events 1.0.0

[brockgr]

This looks like the critical one:

ALERT: error: attempt to call global `connect' (a nil value)

This means the 'connect' socket function is not defined. Have you got the LUA Socket's Plugin loaded and enabled?

Otherwise, some more things to check.. Is this with the demo CCF and GML? Is that all that is in the GML? How are you connecting the machines (no NAT or ActiveSync involved)?

Gavin

[markus00]

Now it works!
Thanks!!!

I did'nt use the LUA Socket's Plugin only the LUA Events plugin.

[esajesa]

WHOOHOOOHAAAAA!!!! YES! YES!!! Thanks guys for all your help! RC6 did the job for me, straight up.. I'm so happy now.. Now I can finally get started with all the feedback stuff I want to do. I'll post my CCF's and GML's when I get something nice working too, so you can see the fruit of our labour!

Cheers guys, and have a greaaat weekend!

//Jens

[brockgr]

That's good to hear!! :D

[Ben S]

Yeah! Glad we got this worked out.

Gavin, I'm guessing the fix I made in RC6 will make your ZoomPlayer control ccf respond faster, as well. I'm going to go try it now.

[brockgr]

Thanks Ben - I'll look at it in a few weeks time. I'm currently on vacation in Europe and am a long way away from my little NetRemote.
Gavin

[JcMarin]

Ben, Gavin:

Are there any plans to expand the Feedback capabilities beyond Label and Picture functions?

I was looking at being able to send a Directory Tree for instance, choosing an entry from that list and sending it back to girder to “execute” this would allow for a very generic client to “Playing” any kind of media.

Could this be done with the current Feedback plug-in and something like the Tree Control for MC9? :idea:

[Ben S]

This cannot -currently- be handled, but with some changes can be handled.

Feedback can currently be in the form of labels, images, and scroll positions.

This actually ties into the idea of taking most of the drivers and moving them server side and leaving a thin client on the PPC. The client would know it's a tree, but would get the contents from the server whether it's coming from Media Center or Girder.