For the record, I want to say "Thanks" to Philips for continuing to support the ProntoNG/TSU3000 via firmware and software updates. That being said, this forum is unquestionably the best place to let Philips find out what the most active portion of it's user community wants.

Here's my suggestion. While the ProntoNG simulator built into the ProntoEditNG software is handy for checking the cosmetic appearance of buttons and where they take you graphically, I have an idea to add more functionality.

If a pop-up text window was added, it could display the HEX codes that fire on each button press in the simulator. Obviously since the simulator is loaded with the PCF, the codes are available within it. (Unless the codes are somehow extracted from the PCF before being loaded in the sim??) I doubt it would be terribly difficult to display them in a popup window with a big scrolling text box adding a TAB or linefeed between each sent code.

I think this could help a great deal with troubleshooting timings, etc. Anybody else have other thoughts or suggestions?

I like the suggestion

There are lots of things that could be done to make the simulator a more useful tool. For example, it could check the hex codes against a database of known codes and provide a simulated action sequence. Philips has not indicated a desire to produce high quality edit software, so I doubt that you will see much improvement.

well here has been big improvements, Timers before and now press duration. So I think you are overly negative.


On the other hand what you are asking for would be cool, but I don't think it is practical and not sure how much more it will add. Let's be honest, for what you want they will need to either know what each possible code does, or be able to read and interpret labels. The only way it would work to some percent would be with UDB codes. On the other hand a macro might seem to work (i.e. sending 2,3,1) but you would not know if it works in real life because the emulator device might change to 231 but it might need delays to get the real device to go to 231. ON the other hand if a box says IR-Sat-2, IR-Sat-3,IR-Sat-1 you know you are sending the right codes, it can also help with complex macros for example M1= 1,2,3 M2=4,5,6 M3=M1, delay. M2 the box could say 1,2,3 wait the delay and then 4,5,6 so you know the macro is or is not doing what is intended

If they do add i1patrick's feature, I would ask that there is a symbol or colour distinction between codes and links and that all the info is passed (device - page - button)

This could indeed be tricky to implement.

I have seen advised, and I always use, a master panel with all the codes for a particular device in it. Then I create the panels with artwork that the user presses, and alias every button to the panel with the commands.

To do what is suggested, the emulator would have to note what command should be emitted, go to that panel, locate the hex code for that alias, and then display it. Sounds like quite a trick to me.

do you mean the original suggestion or the second one? The original suggestion is already happening for the emulator to show jumps and delays it needs to know the whole structure. I also don't think showing the HEX will be useful

ok, let's say

B1:
link to D1-P1-B2
delay 0.2
link to D1-P2-B3

B2:
jump D3-P1
IR code: d-b-s-c
link to D1-P2-B4

B3:
learnt IR

B4:
beep
learnt IR

where D_n is the name of the device,P_n is the name of the page and B_n the name of a button

the output would look either like

A)


------------------------
D1-P1-B2
- - - d-b-s-c
- - - D1-P2-B4
- - - - - - - - - learnt IR
D1-P2-B3
- - - learnt IR
------------------------
with delays/beeps/jumps only shown on the emulator

or

B)
------------------------
D1-P1-B2
- - - jump D3-P1
- - - d-b-s-c
- - - D1-P2-B4
- - - - - - - - beep
- - - - - - - - learnt IR
delay 0.2
D1-P2-B3
- - - learnt IR
------------------------

Technical details.

The display of IR sequence firing may be difficult in that the NG remotes store screen presses and locations in a queue. That's why the images immediately revert to the unpressed image as soon as a button is released. Then, there's a separate "thread" that services this queue. When the item is serviced, the IR is transmitted. That's why in the next release they are adding the "duration" feature as there is absolutely little connection with the length of a button press and the IR code that is xmitted.

If this is a new wish list for Philips, for PENG and PPENG, I have a few:

Within the button properties page, increase the size of the Action window in both directions, so one can view 6-8 actions without scrolling in the up down or left right direction. The mouse hover feature is nice (to see a complete action) but is still cumbersome. There is plenty of room within this dialog box to expand it. Or make the window scalable and let people scale it the way they want.

Dave D'Arche

I second Dave's comments regarding the button properties page. However I think what is really needed is to replace the the properties window with a properties "palette" at the right side of the main window.

This palette would change its content to reflect whichever item is currently selected. Think of the PSP8 Materials and layers palette, to get an idea of what I mean (or for the programmers out there, think of the M$ Visual Studio properties pane).

It has been mentioned elsewhere, but wouldnt it be great to be able to right-click an item, select "Show Links..." and have a list window pop up showing all items linking or jumping-to the selected item. Come on Philips, you know you want to ...

Lyndel,

Not sure I understand this one. What is the logic then that allows the Pronto to recognize and process a 'press and hold'?

Lyndel, not sure exactly what you mean.

do you mean that if Mac1 has 10 steps and Mac2 has 5 steps Mac3=Mac1, mac2 wont be evaluated to 15 steps but just 2 steps and the mac1 will be evaluated when it is it's time and the same for mac2?

On the other hand what ever you meant, the request is to at some point after you press the button that you get a list of all the steps, if there is more then just the IR codes and labels can be easily used, I don't see how the way they are treated will matter. At some point mac1 needs to be broken down in its 10 parts and at that point they (assuming there is access to labels) put the IR on screen even if it is more messy like

D1-P1-B2
delay 0.2
D1-P2-B3

D1-P1-B2 :
jump D3-P1
d-b-s-c
D1-P2-B4

D1-P2-B4 :
beep
font color=green> learnt IR

D1-P2-B3 :
learnt IR