> Looking at the pcf, PowerPro has created the problem by leaving out 
> the first line in the command list Attach:  ShowXDir in one data 
> structure while leaving the count of items at 3 in  another.  I 
> don't know how this inconsistency could have happened.
> 
> If this happens again, please post the bad pcf again to see if the 
> error is the same.
> 
> Was this bar visible when the error occured?
> 
> Do you manipulate contents of bar with cl. or format item in a 
> script? 

I got it again, same error message and I'm sure it's the same problem.

See the 3 files here ("corruptdave.pcf", and "!Auto back of dave.pcf" are
both corrupt. "Previous auto backup of dave.pcf" is not):
http://groups.yahoo.com/group/power-pro/files/0_TEMP_/

One interesting thing of note. The time stamp on the dave.pcf (which was
corrupt was 2:43. The time stamp on the !Autobackup of dave.pcf was 2:46. I
ended up having to restore to the !Previous auto backup of dave.pcf to get a
working file. I wonder how a back was done before hitting OK?

Again, this corruption occurred when I was creating a new CommandList -
"_Bar: Winzip" ( last time I had imported a new commandlist and renamed it
), so I'm thinking it has something to do with create a new commandlist
(event triggers, that maybe updates the pcf - timer maybe?) and then you ok
out of the pproconf.exe and you get the corruption. I only did about 5
different things during that configuration session, and replicating it
exactly did not re-produce the problem :(

FYI the steps I did was:
-Open configuration with *Configure Commandlist
-Clicked new Commandlist item. Typed in the name, hit OK.
-Enabled Autoshow as bar
-Created new item, of Format context =winzip. Hit ok to go back to
Commandlist window.
-Re-opened that item, set properties to hidden and OK again.
-With that item selected, choose new after button. 
-Set it to just Keys (with no parameters) - On a side note I was trying to
record keys, and was unable to get it to see the keys I was typing. It
actually completely disables all keyboard input, and the only way to get it
to unlock is Ctrl+alt+del. But I don't think this problem is related to the
pcf corruption because the problem is still there (I think only a reboot
fixes this, as I've had record keys act like this before) but replicating
steps doesn't reproduce a corrupted .pcf.
-Ok'd my way out.

Hope that helps with tracing the problem Bruce. Thanks!
Let me know when you have the files, so I can remove =)

David Troesch  |  Atlanta, GA  |  ICQ# 2333123
Carpe Diem - "Seize the Day"
Funstuff: Happiness can't buy you money.



Attention: PowerPro's Web site has moved: http://www.ppro.org 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/power-pro/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to