Then maybe a panel of it's own, like the layer panel in graphic programs (i don't like things that popup and disappear every time I click something, must be an allergy to javascript ad popups in browser :) ).

So, something that enables us more (easyer) access to the properties of the widgets on a page. Agreed. (I still vote for the tree though ;) ).

I wish the database could be updated so it can store macros or key sequences.

For example, i think many would appreciate if there was an "On" available even if the discrete command is lacking on a device. And if that "On" could be stored with the device in the DB.

Instead of simulating a connection with extenders, it would be very useful if network communication is simulated!

As someone mentioned earlier, a prontoscript helper would be nice. Some of the simpler scripts could be in the editor. An example could be tuner presets with channel logos; you could select the query command from your rs-232 database, enter the possible responses and set which image should be showed for this response. Not the hardest of all scripts to write, but pretty time consuming depending on the number of presets.

Maybe someone should change the title of this thread (the author) to PEPV4 feature request being as PEPV3 feature lockdown is likely to already have been done.

How about a animated gif converter, or a built-in Animation Macro. Something to make the placements of animations on a page a little easier. It could be just like the battery icon customization.

limit it to one per page.
Use only a defined amount of frames like 15.
Limit the time between frames to 1/10 a second to 10 seconds.
Define it to repeat indefinitely or a fixed number.
Add a option to remain visible after playback or vanish.

Maybe a Animation/Macro area could be called upon from a page as an action ?

I am not looking to animate every button press , but a little sparkle now and then couldn't hurt.

Provide a check-box flag that sets all devices to "Extender = 'No'".

This will allow a lot (not all) logic and GUI testing with the simulator.

Allow a one-way "Virtual Serial over IP" and/or "Virtual Power Sense over IP" support for certain networked devices (vs. physical connections via extender) as another option in the device configuration. Even in its simplest form it would allow easy migration from IR/Serial to IP control with minimal changes in the system configuration in many practically interesting cases.

vertial serial over ip is possible already , its called one shot ip controll your find it on the Pronto website.

You can do something quite similar to this with a little bit of scripting and multiple image frames. The Page Script and assignable repeatInterval work quite nicely for this.

Since the Pronto website (including the professional area) is not exacly search-friendly, could you please specify where on the website one can find the relevant information?

Never mind - found it. Unfortunately, this is not exactly what I meant. It requires manually re-implementing at least some code for every single command basically from scratch.

What I meant is something much simpler - you are able to change the configuration of an already working and configured serial device so that it can be "attached" to a "Virtual Serial" port (which simply is a configurable TCP and/or, possibly, UDP endpoint provided by the controlled device capable of one-way control and power state reporting) instead of an actual serial port / power sense on RFX9600. It would allow trivial switching from IR/SR to direct IP control without any Pronto Script and physical connections to the extender at all.

So are you wanting to say change a serial port on and amplifier to a ethernet port?

Then send serial codes over ethernet?

Yes, something like that - say, the higher-end Denon AVRs connected to Ethernet can be controlled over IP using basically the same command strings as when using serial. So, switching from physical serial to "vitrual serial over IP" should be really simple and should only involve very simple configuration changes.

I think the simple answer is to alow IP strings to be stored in the Database .