NetRemote Designer 2.0.0 BETA

[Rob H]

Correction... after a few hours editing and many saves later the Lua states are gone again. And the changes I was making were no where near these buttons.

Are you sure you didn't edit those buttons? That's the only way that the Lua states can be changed as far as I can see. I have however found a bug where editing a button with Lua states would kill the Lua state even if you didn't edit the state rules.

I'd appreciate it if you could stick with NRD2 - perhaps making frequent backups of your CCF at intermediate stages.

Here's the fix for that bug :-

[Jlee]

I definately did not edit those buttons. I just viewed the Lua states on them after installing NRD and saving my CCF to confirm the fix. Then later I realised I'd lost all lua state code on all buttons with lua states.

I'll persevere with NRD 2 and would encourage others to do so too because once these few bugs are ironed out it really is a great step forward from v1.

[Rob H]

On all buttons? Hmm... that's really weird. I'll keep looking then.

[Rob H]

I definately did not edit those buttons. I just viewed the Lua states on them after installing NRD and saving my CCF to confirm the fix. Then later I realised I'd lost all lua state code on all buttons with lua states.

I'll persevere with NRD 2 and would encourage others to do so too because once these few bugs are ironed out it really is a great step forward from v1.

So you opened the Element properties dialog presumably? Did you press Cancel or OK?

I still can't see any way that it could lose Lua state rules on any other buttons though.

I may have to give you a build that includes some logging code at some point if I can't solve this.

[Jlee]

I would like to think I pressed cancel but can't be sure. What I can be sure of is I did not go anywhere near my GAC panels, which lost all the Lua states from them. I have many different GAC panels and had no need to edit the buttons on there. The result was when calling GAC panels buttons which should have been hidden because there were not enough GAC results to fill them were displayed but empty.

[vitello]

Rob,

The new designer is great, but I am also having problems with my lua states. It looks
like none of my lua state settings are working properly. One major problem is that
when I try to look at a Lua rule attached to State 1, the Edit Lua Code window is empty.
Now last night when I was looking into what was going on with my Lua states there was
code, but I found that when editing the Rule selection would often end up blank and not
as Lua after editing. Lua state rule coding I changes last night is still there, but
frames I did not touch have no Lua code in their Lua rule. So it looks like the new
designer has erased Lua state rule code.

This was with version 2.0.0.0.

Peter

[vitello]

Rob,

As a quick experiment, after installing 2.0.0.1, I opened my ccf in NRD and then did a
save as. I then opened the new ccf in NR. What I found was that all of my lua state
behaviors has changed. Frames that should have been hidden were shown, and frames
that should have been visible were not.

Peter

[Rob H]

I think I need to see a concrete example of this. I can't seem to reproduce it here.

First of all, can both of you with this Lua state confirm that you are using the latest CCF format? The only state manipulation that I can see being performed on loading is when using 1.0 format

[RLeBrette]

That looks great, I've started to play with it, it's really more user friendly that version 1.
Is there any roadmap for this new version?
What are the new features you plan to add?

If not already planned, it would be cool to be able to define an external editor for LUA scripts.

[Rob H]

I do have some ideas, but 2.0 is mostly feature complete. Any new features will probably have to wait for 2.1

I quite like the idea of an external editor though.