Preview Problem

[scottsimmonds]

I have been using FP for a year now and love the program. A problem has croped up in the last day or so. Perhaps I changed a setting

Editing an existing doc - when I go to preview my changes dont show up.

I add characters, tags and breaks and nothing shows up in preview!

Any ideas???

[Kezzie]

I have exactly the same problem. The preview just isn't updating. I thought maybe something had somehow got corrupted so I deleted 1st page 2000 and redownloaded it and reinstalled it but I have the same problem still. Has anyone any ideas of what I should do to be able to have the preview automatically updating?

Thanks for any help.

Kezzie :-) :o)

[tapestry]

::smiles::

I have the same problem. I was hoping there would have been a post here, addressing it to tell me what I am doing wrong or what I can do to fix it. I've also reinstalled, but that hasn't helped.

I'll keep looking to see if anyone has posted a fix .. or, if you're out there and know how to fix this, please .. post a reply.

Thanks,

tap

[Marilou]

I have the same problem while previewing. But is helps if I just close down FP and then open it again, annoying though!

[Maglor]

I had the same problem and it turned out to be some bad html code in the page I had created so if you check that it is only one site at fault that could be the answer.

[ByteWizard]

I have a theory about the problems the current FP is having. I believe it leaks memory and the program needs gobs of memory to operate well.

I would be interested in knowing how much memory those of you have who are having these strange problems. I only have problems when I have way too many programs in the task bar. Close a few and FP behaves well again.

When you close a program and re-open it again, AND it was mis-behaving before you closed it down and after re-starting all is well again. ->->->Memory leak!

Not sure what language it is written in?? Anyone know? Probably C++ or if we are lucky, assembler.

[DCElliott]

Should be able to test the memory leak theory. If you have a NT based system just bring up the task manager (ctrl+shft+esc) and check the processes tab. Keep an eye on the memory allotted to FP. When mine starts it asks for about 13MB - I've got a 128MB system so it is fairly happy. Even with two browsers and a mail client and PhotoPaint running there seems to be no problem.

FP asks for about 3MB more when it opens the preview window - which isn't bad considering a regular browser takes more than 10MB. I can't really duplicate what would happen on a Win 95|98|Me system because I've got Win2K and it is much better at memory management, including cleaning up after leaky applications. So . . . anyone else want to test the hypothesis?

[ByteWizard]

In my experience memory leak usually raises its' ugly head when you have an application open and active for quite some time and generally doing a repetitive task. Part of the task involves grabbing a small amount of memory to be used in a subroutine possibly employing an array. When the memory is given back to the operating system, some faulty coding is leaving a chunk of memory unrecoverable. Now nobody can use it. You do this often enough and you wind up with a horribly fragmented non-contiguous memory pool. Things begin to slow down and then chunks of the display began to act strange from corruption in that area of memory. Pretty soon all systems shut down and the patient is dead.

Using task manager to kill off the task and re-start and all is well. Sometimes the situation will get bad enough that the O/S memory becomes corrupted and you reach for the "Big Red Button"

In order to watch the task manager and check the bugger in action would be to check ever so often as you go about using the program taking note of memory changes.

OK, we catch it gobbling memory. We just spent a bunch of time and no source to look at. Those who twiddle the bits will have to ultimately find some of these erratic behaviors.

[ScottInTexas]

Me Too! I figure if enough people add to this post someone in the know will tell us how to fix it.

[ScottInTexas]

For some reason the file that is created for preview is left in the directory. In the directory where the files you are editing are located there is a file with the same name preceded by a ~. Delete this file and try again.

When you preview a file this temp file is created and when you go back to the editor it is deleted. Some bug crops up that prevents the deletion and what you see previewed is the same file as before.

[GDS]

This problem occurs for me when I exceeds a filesize of approx. 1000-2000 lines of code. My workaround, is to save the file, and then when previw from browser, delete the ~prev prefix, and reload. Not exactly elegant solution, but it works in a way.

This is, in my opinion, the most annoying bug in 1st page 2000.
If this bug was fixed now, I can live happily with 1st page 2000 for another year or so.

GDS