NetRemote 1.0.18.0 posted

[Ben S]

Hello everyone,
I've just posted links to prereleases for 1.0.18.0 for all versions. I have not run through full regression tests yet, but have done some basic tests. I will be running through full regression tests over the next few days.

Changes
* Bugfix - Memory leak freeing first image on panels fixed (on 480x640 this would break after 5-10 jumps with a large background image)
* Bugfix - Possible threading issue during connect/disconnect of socket fixed in SDK and built-in plugins
* Enhancement - Added ability for NetRemote to discover device size and select a proper sized CCF if available
* Enhancement - Added 480x640 versions of all CCFs to installers
* Enhancement - Added Girder.LinkActive variable, which is set to 1 when Girder is connected, and 0 when not connected.
* Enhancement - Added ability to fire an action only if a variable is set, and to wait to fire the action until the variable is set. Action is -999,5,16, with the IR name being "Variable Name,Value to wait for,Max wait in milliseconds". So to wait for Girder.LinkActive to equal 1, or timeout after 10 seconds, the IR name would be "Girder.LinkActive,1,10000"
* Bugfix - Fixed issue with iTunes not handling album cover for current playing track correctly
* Bugfix - Fixed issue with iTunes not handling playlists properly
* Bugfix - Fixed issue with switching of current IR plugin instance locking up NetRemote when GlobalCache being used.
* Bugfix - Should properly install on PPC's and Simpad
* Enhancement - Added repeat limit back to IR plugin for GlobalCache usage.
* Enhancement - Setup basic usage of plugins describing their actions for designer usage.
* Enhancement - Internally documented all actions in base plugins for designer usage.
* Enhancement - Added code to ensure that NetRemote.ExecuteAction (from lua) are handled synchronously.
* Enhancement - Made calling of lua from plugins more thread safe.

[danward79]

Thanks Ben,

That Girder link active variable sounds great! I will not even have to change my ccf! Only stop my gml sending it!

[Jlee]

Wow, you have been busy! Nice one Ben. Thanks for all your hard work.

[Wilhelm]

Thanks, Ben,

I find it great, that you added the "wait for variable" action. Could you please please please find it in your heart to also add an action to "skip the next action if" a variable has a certain state? This would make life so much easier with controlling toggle switches on certain devices.



* Enhancement - Added repeat limit back to IR plugin for GlobalCache usage.


does this mean you are giving up on the missed transmission bug?

[avid]

Could you please please please find it in your heart to also add an action to "skip the next action if" a variable has a certain state? This would make life so much easier with controlling toggle switches on certain devices.
Wilhelm,

Surely this can be simply handled by LUA? [Especially as NetRemote.Execute actions may now be fixed!] Or are you talking about true IR actions that have to be in the CCF?

Brian

[Wilhelm]

Yes, I am using GC device as you probably know. This device has inputs, that can be checked. e.g. you can get a little interface, that checks for a logical signal or even the existance of a video signal.
So what I want to do, is to check, if my sat receiver is switched on or off, to get a distinct on and off action for this device. So the sequence would have to be:

if switched_on
SendIR "On/Off-ToggleCode"

If you have any other idea to achieve this, please let me know. I don't think sending IR-Codes can be done in the LUA code, right?

Cheers

[Ben S]

Wow, you have been busy! Nice one Ben. Thanks for all your hard work.

You're welcome! I hope everything works as expected! I don't like to disappoint.


Could you please please please find it in your heart to also add an action to "skip the next action if" a variable has a certain state? This would make life so much easier with controlling toggle switches on certain devices.
Sure. Based on how I had to add the wait, adding the "skip next" should be easy enough.


does this mean you are giving up on the missed transmission bug?
No, just added something in case someone has a spotty network. Unfortunately even without a missed transmission if the network drops you could have blown speakers.

[Wilhelm]

Great!

[Wilhelm]

Just a short question:

Is it intended, that NR on WIn2K/Win32 allways comes up with the maximun size the screen allows, independant from the size of the actual ccf?
Up to now, I allways used my PPC CCF als a small remote window on my desktop. This obviously is not possible any more, since the NR window also isn't resizable.

Any coments?

[Ben S]

No. It definitely shouldn't do that. It doesn't do that for me here (running an 800x600 ccf). Are you using one of the stock interfaces?

[Wilhelm]

Yes, it's definately related to loading the standard skin.

[Ben S]

Are you saying that it starts fullscreen? IE: The default Pro interface is rendered with black on the sides?

Is it possible you set it to start in fullscreen for some reason? I can load the Pro interface (240x320) and it stays 240x320.

Anyone else seeing this issue?

[danward79]

Hi,

I had some problems starting my ccf's. I found this to be caused by the girder calls in OnCCFLoad.

By moving these to onPanelLoad, it starts fine. However, the actions are not run on start up, as I would wish.

I will try and move the start up stuff to the new waiting action

[Ben S]

That will be difficult. The wait stuff will only work when attached to a button (long story why).

The girder stuff should work in the OnLoadCCF. This worked before but now doesn't? If so, I will resolve.

[danward79]

That will be difficult. The wait stuff will only work when attached to a button (long story why).

The girder stuff should work in the OnLoadCCF. This worked before but now doesn't? If so, I will resolve.

It worked fine before this version

[Jlee]

NR simply will not load on Win32 or PPC since installing this new release. If I comment out this line from my lua file it's OK, otherwise I have to kill NR from task manager (Win32) or soft reset (PPC).

NetRemote.ExecuteAction(-1,0,1,"NR.StartUp");

If you want to test it yourself my ccf & gml is here. (http://uk.geocities.com/rigbys.biz@btinternet.com/zips/jleeccf.zip)

[Ben S]

NR simply will not load on Win32 or PPC since installing this new release. If I comment out this line from my lua file it's OK, otherwise I have to kill NR from task manager (Win32) or soft reset (PPC).

NetRemote.ExecuteAction(-1,0,1,"NR.StartUp");


This is also in your OnCCFLoad, correct? Moving it to OnPanelLoad works, most likely.

I'll investigate right away. Thanks for the feedback, guys.

[danward79]

I think this has something to do with no girder link active! Oh well...

[Wilhelm]

Are you saying that it starts fullscreen? IE: The default Pro interface is rendered with black on the sides?
No, its opening a window with the maximum screensize, all white and displays the CCF in the upper left corner including it's skin. The maximize button is grayed, and the window is not resizable.



Is it possible you set it to start in fullscreen for some reason? I can load the Pro interface (240x320) and it stays 240x320.


No, if I start fullscreen, it looks the same, only the title bar and menues are supressed.

Could this be another Win2K problem? Or better a WinXP problem, because I'm pretty sure it will happen on all other Win32 platforms as well.

P.S. "Disable shaped windows" has no effect on this one-

[danward79]

I tried this, but it causes NR to freeze on win32, in OnVariableChange


if (varname=="Girder.LinkActive" and varvalue == 1) then
NetRemote.ExecuteAction(-1,0,1,"NR.Checkweather")
print ('girder')
end;

[Jlee]

NR simply will not load on Win32 or PPC since installing this new release. If I comment out this line from my lua file it's OK, otherwise I have to kill NR from task manager (Win32) or soft reset (PPC).

NetRemote.ExecuteAction(-1,0,1,"NR.StartUp");


This is also in your OnCCFLoad, correct? Moving it to OnPanelLoad works, most likely.

I'll investigate right away. Thanks for the feedback, guys.
Yes it's in OnCCFLoad and Girder is available. Even if I disable the corresponding event in Girder I get the same problem so it's nothing to do with the actions the girder event would be triggering. I don't have an OnPanelLoad section and don't know the syntax for it so I can't test that.

[Ben S]

Could this be another Win2K problem? Or better a WinXP problem, because I'm pretty sure it will happen on all other Win32 platforms as well.

Could be windows 2K, but it's definitely not solely platform based (I don't have this issue on my WinXP machines), unless it's with specific files.

Anyone else having this issue, with Win2k or XP?

When you say "including it's skin", do you mean that you are using a skin .ini file still? This could be the problem, as a custom CCF should no longer be using a skin file.



I tried this, but it causes NR to freeze on win32, in OnVariableChange


Unfortunately these issues are all related to threading, and NetRemote's job of handling the girder connection thread and variable handling all attempting to shuffle themselves onto the main thread. I'll need to investigate.

[Wilhelm]

Could be windows 2K, but it's definitely not solely platform based (I don't have this issue on my WinXP machines), unless it's with specific files.


What I meant was, I suppose it's only working on XP,



When you say "including it's skin", do you mean that you are using a skin .ini file still? This could be the problem, as a custom CCF should no longer be using a skin file.


What do you mean by custom CCF? My CCF is still in the original Pronto 970 size and worked fine before 1.18. Anyway if you want to remove support for the standard skins, I suppose you should tell us und secondly remove the menue to load it.
Anyway I like the pull down menue of the original pronto to switch to seldom used devices and would be very disappointed if the compatibility to the Pronto would go for such a minor glitch.

[Ben S]

Now I understand - and now I'm able to successfully recreate what you are seeing.

No, support for TSU6000 and RC9200 is not being removed. I thought you were using the skin file with a custom ccf (not the two formats as mentioned).

Since I now can now replicate, I'll investigate a fix this evening. My apologies.

[Ben S]

Ok Wilhelm - This is related to NetRemote using the true device resolution (it used to default to 240x320) during pronto skin creation. Simply add the following code to your .ini file (most likely My Documents\NRSkin\standard.ini).



[Master]
Window=240,320


This will tell NetRemote to make the window 240x320 (instead of using the default device resolution.

The next install will have these lines in the standard.ini file.

[Ben S]

For all having troubles with Girder calls, please try the attached Girder plugin for windows.

Lee - thanks for your samples. I was able to confirm, replicate, and resolve the issue using your .gml and .ccf.

Upon confirmation, I will rebuild for PPC as well and rerelease installers.

[danward79]

Hi Ben,

Tested that it appears to work, thanks for the quick fix

[Jlee]

Great to see you've fixed it so soon Ben. I'm at work now so can't test until tonight but since you've already tested my ccf and Dan (being our resident UK insomniac) has tested his I'd say it's a goer.

Thanks again.

[Wilhelm]

This will tell NetRemote to make the window 240x320 (instead of using the default device resolution.


Great, thanks.

[danward79]

Great to see you've fixed it so soon Ben. I'm at work now so can't test until tonight but since you've already tested my ccf and Dan (being our resident UK insomniac) has tested his I'd say it's a goer.

Thanks again.

Should be good for you to Lee, I beleive your prob was the same as mine.

[danward79]

Ben,

Are you going to do the same fixes on the PPC version of the plugin?

[Mastiff]

Yeah, this is more like it! I actually came in now (at 1 A.M.) to report that NR wouldn't start (I could see it in task manager, but I never saw the window) with the LUA file I'm using for browser URL's and phone numbers for drop-down lists and LDJ, but downloading this fix cleared it right up! :D

[Ben S]

Just uploaded 1.0.19.0 (Pro only) as 27-Jan-2005.

Changes
* Bugfix - IR plugin now properly switches instances
* Bugfix - Girder plugin locking issue resolved (on PPC as well as Win32)
* Bugfix - A panel jump to the same panel no longer sets the "previous" panel and device as used by Jump back.
* Bugfix - Set standard skin (used when in TSU6000 and RC9200 mode) to have window size of 240x320.
* Enhancement - Added ability to stop execution of actions if a variable is not set. Action is -999,5,18, with the IR name being "Variable Name,Value".
* Enhancement - Added ability to skip next action if a variable is not set. Action is -999,5,17, with the IR name being "Variable Name,Value ".
* Enhancement - Added progress bar (this was actually added to 1.0.18.0). Action is -999,0,64, with the IR name being "Direction,Variable,Min,Max". Direction is 0 for up, 1 for right, 2 for down, 3 for left. The button down image will show as progress over the button up image. (IE: If direction is 1, the button down image will progress over the button up image).

[Ben S]

Sample Progress Bar Test .ccf (for Windows)

[Jlee]

So is -999,5,17 the same as 5001 0000 0000 0002 FC19 0005 0017 0000 ?

Is there any way to use -999,5,17 in a ccf or do we have to use 5001 0000 0000 0002 FC19 0005 0017 0000 in the IR code?

[avid]

So is -999,5,17 the same as 5001 0000 0000 0002 FC19 0005 0017 0000 ?

Is there any way to use -999,5,17 in a ccf or do we have to use 5001 0000 0000 0002 FC19 0005 0017 0000 in the IR code?
Use 5001 0000 0000 0002 FC19 0005 0011 0000
IR codes are in hex - Ben usually quotes the codes in decimal just to confuse everyone!

Brian

[danward79]

Lee if you mean use execute action in a ccf button you could use the lua ir code

5001 0000 0000 0002 fc19 0007 0000 0000

[Ben S]

IR codes are in hex - Ben usually quotes the codes in decimal just to confuse everyone!

That's my goal! :)

It's just easier for me to post the driver ID and two parameters than paste the full IR string. Maybe I should add a button to the forum to convert between -999,5,17 format to 5001 0000 0000 0002 FC19 0005 0011 0000. :)

Also, just FYI: Since these 3 codes manipulate the way actions are handled, calling them from lua won't do anything (an ExecuteAction is an action list of only 1 item).

[mhwlng]

* Enhancement - Added code to ensure that NetRemote.ExecuteAction (from lua) are handled synchronously.

I can confirm that this works ok now in win32 :

3 executeactions in a row are ok :

NetRemote.ExecuteAction(-1,0,1,"BACKGROUND.RESCAN(800)");
NetRemote.ExecuteAction(-1,0,1,"MCAL.ALRESCAN(39)");
NetRemote.ExecuteAction(-1,0,1,"LDJ.RESCAN(12)");

before I had to combine them into one executeaction:

NetRemote.ExecuteAction(-1,0,1,"SCANALL(800,12,39)");


Marcel

[Ben S]

NetRemote 1.0.20.0 posted (all versions).

Changes
* Bugfix - NetRemote now properly supports left handed people (will properly flip hardware buttons for threads and sliders).
* Bugfix - Fixed issue with NRBasic exit command not compatible with Designer.
* Enhancement - Direct IR works as it did before the 2005 timeout (better angle/strength on Axim x50v and possibly others).

Unless I hear otherwise from anyone, these versions will become the general release versions tomorrow. In other news, I have a few tweaks to make for the designer in order to get a beta into peoples hands later this week.

Thanks prerelease testing team!

[windtrader]

Ben S,

Since installing dot19 jan27 release a few days ago,, I am getting intermittent Girder crashes while executing NR. I have not isolated the problem as yet but I get a GIrder panel with little info : something like a yellow !Program error message.

During the same time, I also made a fair amount of coding changes in Girder to handle device timing issues by setting delays using TIME_Sleep commands in loops. It could be something with this, maybe other changes, I don't know.

If no one else is reporitng problems with the latest NR releases creating Girder problems, then it must be something on the Girder side.

Just wanted to let you know since you posted the message about releasing the NR code.

I use logger a lot but it does not seem to record the problem. Is there other debug logs in Girder I can turn on or view to get a better idea of what is causing Girder to fail?

thx don

[Promixis]

The 1.09 logger crashes after a period of time due to a bug. The logger is really only good for debugging only and then should be turned off.

[windtrader]

Thanks. That's likely it since all the extra logging is being done with the loop da loop da loop.... :lol: