Re: Odd behavior on member save -- WDSCI-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

All:

I would argue strenuously that having to manually "clear the cache" is just a work-around or circumvention for a readily apparent design defect.

A true cache should be totally transparent to the user, and should never require manual intervention, e.g. to tell the sottware to "clear the cache".

This is also a very common design flaw with most (or all?) web browsers.

The software that manages the "cache" should be able to detect changes in the corresponding objects (or files) on the host system, and automatically update the copy in the cache, as and when needed, to match any changes on the host.

Mark S. Waterbury

> On 1/27/2014 12:30 PM, Stuart Rowe wrote:

Found this setting under LPEX Editor/Save -- maximum line length = 0 (I
hope that means unlimited).
Simlar setting found under each open member LPEX Editor/<tempfilepath>
Maximum Line length = 92. Cannot imagine where that came from. Set to
112. Member saves fine. Close, Open, reverts to 92.

I wonder where it comes from?

"The Cache", I'll have to assume, since clearing that (thanks Thomas)
cleared up the issue.

Stu

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.