Am I just going about this all wrong, or are the cut, paste, group, ungroup, copy group, copy multiple and paste multiple functions in PENG guaranteed to create a corrupt PCF? My PCFs are saving in corrupt state and causing PENG to crash when reloading the PCF.

I'm at the point where I'm doing a save-as of my PCF between every paste. I'm reusing a lot of navigation icons across all my pages, so I have a lot of multi-object pastes to do. It's 1am, I've lost my work 8 times and lost 3 hours effort and this is mainly a vent.

Are there problems with imported gallery objects too? I tried putting all my nav objects into the gallery and dragging them with actions onto the places I want them. That didn't work either.

Hopefully the PENG coder that was in here before will read this. I can't even really tell if I like the 3000 yet, because I haven't tried using it with my design because I can't finish it. I know PENG is in need of some major help, specifically with retaining font size data from cut to paste. I hate when I get a great design together on paper and the tools get in the way. Adobe Philips ain't. I just can't believe that anyone can write software that can't read its own files. Worse, XML is a rule-based syntax that can easily be checked for invalid structure or data range. I'd better shut up now before...

Can someone help me across the thin ice? Is there a bug list on PENG somewhere?

I recently submitted to Philips a bug and feature suggestion list with over 70 items on it.

With that said, I have worked three weeks solid in PENG and have never lost even 5 minutes' worth of work, despite cutting, copying, pasting, grouping and moving many many times. Because of reported issues I start a new filename every now and again, but so far I haven't needed it.

I haven't seen the "font size when pasting" issue, and I completely avoid the gallery function since I find it useless.

You are using PENG 1.1, right?

By saying "anything major" I realize my vent probably insulted most of the people here. I don't consider what I'm doing to be any more substantial than much of what has already been done and showcased here.

I'll shut up now, I was using 1.0.

Ah, that explains it... 1.1 was released specifically for file corruption issues.

Daniel, I suppose your list is not public?

Here are a view things I noticed:

- Double clicking a configuration file when ProntoEdit NG is already open, does not open the configuration file. The same is true when trying to view the configuration file from WinZip.

- The dimensions of panel/button are reported twice the actual size when page is zoomed into.

- Device Overview and Page Overview pages do not correctly show the contents of the System Page. Instead they show an image internal to ProntoEdit NG. This is obvious from the font used to display "Tools" and the grey level of the bitmaps.

- Three bitmaps are associated with the activity indicator. ProntoEdit NG shows the first bitmap; Pronto NG seems to show only the last bitmap. I assumed that Pronto NG would use the three bitmap to animate the activity indicator.

This message was edited by PS1 on 04/17/03 22:59.