Empty buttons

[barend]

Not yet programmed buttons (in ccf mode) do not appear on the screen. This has been the case with all NR versions I have used.
It is a bit irritating though, for buttons that need a learned ir command I have to insert some dummy code or alias so the button shows up, and I can overwrite by learning.

Empty buttons do show up in TR and PDAWIN, IMO it just works nicer that way...
Anyone?

Furthermore I can confirm the recent issues (2005 issue and the settings not showing up in the IR Direct Version) have been solved, ultimately by the Dec 29 upgrade and of course the Jan 3 file ir.dll.

Good work!

[Rob H]

I prefer it the way it is - ie the same way that it works on a real Pronto. Mind you there the buttons appear when you switch to learn mode - does this not happen in NR?

IME it's generally a bad idea to put the learned IR directly into a button, it's better to have a normally hidden panel with plain buttons for each remote and to learn all your IR codes there. Then you can use an alias to those buttons instead. Make life a lot easier when you change your CCF

[ebariaux]

Mind you there the buttons appear when you switch to learn mode - does this not happen in NR?


No, it does not work like that in NR. I had some talk about this with Ben some time ago and it's not that straightforward to change, so I don't believe it's high on the priority list.

For now, I simply put a dummy action (like a delay) on buttons. I find this a pretty simple solution and this does not bother me at all.

[Jlee]

Perhaps the new design tool could invisibly set an initial action of 1ms delay when a new button is created.

[Wilhelm]

Every Button has four icons, the inactive ones should show, when there is no action defined.
This is not a real problem, but it still is a bug. Why could this be difficult to change?

[Rob H]

That's a good point, I'd forgotten about that. Perhaps it's because of the STATE support?

[Wilhelm]

I think the state corresponds with selected and unselected, not with active and inactive, but I might be wrong.

[Rob H]

I'm fairly sure it's active and inactive

[Jlee]

I'm fairly sure it's active and inactive
That's 100% correct. Selected and unselected are exactly that - whether the button is pressed or not.

[barend]

Perhaps the new design tool could invisibly set an initial action of 1ms delay when a new button is created.

Hey JLee,
What's that new design tool?
Must've missed something? :oops:

[Rob H]

See this thread http://www.promixis.com/phpBB2/viewtopic.php?p=106465#106465

[Ben S]

Yes, inserting a default action of delay 0 is the best way to handle this. Because the active/inactive images are used as states (especially with the new editor where you can't define inactive images), this would be difficult to do by showing buttons in learn mode that aren't seen otherwise.