Just to echo one of the comments at the top of this thread - having the Pronto icon be the way that you get to the setup screens is really bad. Since no other way is provided to get to the setup screen (that I can find), you have to have the Pronto icon on your screens. That would be OK if you could control where it appeared.
Pete

Well, I guess you can tell I'm busy converting my ccf files right now, because here's another problem. The Volume +/-, Channel +/- and Mute button commands don;t flow through from the system level any more. In other words if I link the Volume button to my AMp Volume+ button in the System Properties screen, it's not there on the Volume+ screen for any of my devices.

Not an insurmountable problem, but it means that when I change my amp, I will have to change the Volume +/- and Mute button defs for every device on the Pronto instead of just on the System Properties.

Pete

I've come across one thing that helps in this situation (and in changing bitmaps, etc.). This may have been present in the older versions of ProntoEdit, but I wasn't aware of it. When you double-click an item, the properties window opens up, in which you can change all of an item's attributes. But, if you now click on another item (without closing the properties window), the properties window changes to display the attributes of the item just clicked. This helps changing the bit maps of items (as well as other attributes) immensely. What I have done is set up a few macros (with one of the many PC macro programs) that removes the old bit maps, imports the new ones, and even moves to and clicks on the next button I want to edit. This way I can rapidly change the bitmaps on buttons with only a single keystroke per button. Much faster and easier on the wrist. Changing the volume +/- buttons can be handled similarly.

Even without a macro program you can fairly easily change the volume buttons by leaving the properties window open and clicking through the various devices to be changed. When you go to create a link for each of these, the links window will default to what was selected previously. So, once the properties window is open, click on the device, click on the Create Link, hit return and that should do it for each device.

Paul

If you're still in the design stage, there is a workaround for this. On some hidden panel (well, looks like it has to be a hidden device at this point), create buttons that alias your Amp's Vol +/- and Mute. Then, point all your hard Vol +/- and Mute buttons to the buttons on the hidden device. Then when your amp changes, you just need to change the buttons on the hidden device. All the hard buttons can be left alone.

Thanks for the suggestion on getting around the volume button problem. I guess my real point was why on earth did they remove the functionality in the first place - it's an important feature of ProntoEdit that's gone from PENG. Hopefully it's just an omission/bug that will get fixed.

Unfortunately, I ran into a much more serious problem that has made me decide to stop using PENG. After spending several hours yesterday redesigning my old screens and doing frequent saves, I came back later and tried to open my new config file and got a page fault error from PENG. I can no longer access the file I spent hours of work on.

Clearly, this is still a beta version of PENG and is not to be trusted.

Pete

That's why I make a back up of the file every time I save... :-)

Well making a backup of the file wouldn't have helped - the file was corrupted during the save process, so the best I could have done was to go back to a backup from the previous save which would have been several hours old.

In any ca

I think the 3000 was built on the NEO platform (since PENG looks and acts a lot like NE and the PCF format is a zipped XML file and a folder full of bitmaps). So if the NEO did not have the functionality, then the 3000 did not loose it :-)

but I do agree that some of the stuff that we had on the Pronto is missed

The Pronto II Simulator is in fact a "neo simulator" it even has the same icon as the neo in the program files folder...

Does this make anyone else worry that the 3000 will have the same problem the Neo has with learning IR codes?...

Daniel, how well does your prototype remote handle learning?

I guess I've never seen the Neo, so wasn't aware the 3000 was based on it rather than the standard Pronto.

phaworth: not a big deal, but does help in putting things in perspective.



a bit, but the problems with the NEO might be HW and not SW (at least that is what I am hoping :-) )

If anybody has problem in opening a saved PCF file, please mail me the PCF file ([email protected]) so that I can take a look into it and try to identify the problem.