Proclaim works fine on our macs, but for our PC the Program keeps saying it needs to close (CRASH). PLEASE HELP!!!
It would be helpful to get some more information from you. Namely, what were you doing prior to the crash? Did the crash happen on opening Proclaim?
Also, if you could post your log files to this thread per the instructions here: http://community.logos.com/forums/t/39446.aspx
Thanks,
Normally that is the only thing we use on this computer regularly. On that day, we pulled up proclaim and realized we were in the wrong presentation and proceeded to open the right one, then the program crashed. Since then, rebooting the computer, rebooting Proclaim or anything will produce the same results in a crash. Can't even get proclaim open.
8267.Proclaim.log
After having examined your data, we have some ideas as to how this crash may have occurred. Our developers are looking into the issue.
We have fixed your data on our end. You should be able to load that presentation on your PC successfully. We are evaluating fixes to prevent this issue from occurring in the future.
Still not working and really need this for Sunday!!!
4174.ProclaimError.log
0876.ProclaimCrash.txt
7723.Proclaim.log
I went back through your data and found another piece of bad data in a presentation. I fixed that on our end and synced up the change.
The problem here is that the Mac client allows you to set a Lineheight of a negative number, which is not valid and will crash the Windows application.
Be sure not to enter any negative numbers in the Customize window.
I'm not sure where any negative numbers are??? Were not using any negative numbers. Unless a date of 2-10-12 is considered negative?
The negative numbers appeared in several of your content items, in the Lineheight field that you can access in the Customize window.
I looked for negative numbers and am not understanding at all. In order for me to not use them I need to understand why they are!
Line height can be set to negative values when customizing text fields on the Mac, causing a crash due to invalid data on Windows. This is a bug that will be fixed.
