NetRemote Designer 2.0.0 BETA

[Rob H]

BUG FOUND!

I have discovered the bug! It appears that when a button has a BEEP action, NRD will not save any other actions to it. Once I removed the beep, I can add anything and it saves. I hope this helps!

That definitely helped, the problem (in case anyone is interested) is that when writing out the beep action NRD was writing a 4 byte int, a 2 byte short, and a single byte (the volume). However when reading back it would read two 4 byte ints. The extra byte was the action type of the subsequent action and in this case was usually 0 so the action wasn't created. The beep action now pads out to 8 bytes.

So, fixed in the next build.

[Manser]

Yes, but in my opinion that should happen automatically, if I replace an image I want to use this image with the new size.
Otherwise I add a new one. But that's my way of thinking ;-)

[Manser]

And that's just an idea now:

It would be cool if we could edit an "component gallery element" in the ccf as we can do when we drag the element into the ccf.
Something like a new popup where the placeholders of the component are still editable.

[Rob H]

And that's just an idea now:

It would be cool if we could edit an "component gallery element" in the ccf as we can do when we drag the element into the ccf.
Something like a new popup where the placeholders of the component are still editable.

If I understand you correctly then this won't be possible, as the placeholders will already have been substituted. Unless you mean that if the placeholders haven't been substituted then the popup could appear?

[Rob H]

Yes, but in my opinion that should happen automatically, if I replace an image I want to use this image with the new size.
Otherwise I add a new one. But that's my way of thinking ;-)

You're probably right. However, I've just discovered another major problem with the existing Replace image from file code - it isn't undoable! That really isn't right.

[Manser]

Yes I now they are already substituted then.
So it isn't possible then. That's what I thought.


What I wanted is perhaps a new component something like a "super button"
So you can create a "super button" in the component gallery with has then properties "in fakt placeholders" witch are editable in the ccf like the properties of a button.

that's because if I want to edit a little more complex component in the ccf isn't really comfortable. Would be cool if we could edit only the placeholders there.

It was just an idea

[Rob H]

This would probably require a substantial change to the CCF format, and as such will probably have to wait for NR3.

[maxthebuilder]

.... wait for NR3.

uh?!

is there any timeframe?

[Rob H]

No, there's no timeframe for NR3 I'm afraid.

Not sure how much I'm allowed to say about NR3 either.

[jwilson56]

Well its good to know there might be a NR3 given the current economic conditions..... I plan on getting back into my project in September