On 7/31/2018 10:35 AM, Savageduck wrote:
On Jul 31, 2018, Neil wrote
(in article ):

On 7/30/2018 3:01 PM, Savageduck wrote:
On Jul 30, 2018, Neil wrote
(in article ):

On 7/30/2018 10:21 AM, Savageduck wrote:

If the Win10 update has screwed with PSE 15, the same issue with PSE 13
would not be unusual. Naturally MS will probably admit no fault, and expect
Adobe to come up with a fix for their screw up. Then they will screw up
something else with their next update.
I think your analysis misses a major issue that has existed with apps
since Windows 3.0. It is not at all uncommon for app developers to
disregard MS specifications, even for Adobe apps. The result is that
while an app may run on the current version of Windows, the next
upgrade/update would cause it to become unreliable or fail completely.

Another issue, though not relevant to this situation, is that some users
who don't understand the changes that a newer Windows OS introduces try
to run older apps on the newer OS and experience problems or failures.

In either case, the problems are not caused by MS, but by those
disregarding published requirements for the OS.

That raises the question; why should developers have to chase their tails if
they have delivered an app, any app, that conforms to current OS specs, only
to have their app functions undermined by a fractional OS update?
The problem that I described is that the apps *don't* conform to
"current OS specs"... they may RUN on the current OS, but are not
compliant with the published specs. I've seen this kind of problem
created by code that ignores the specs and compilers that were out-of-date.

That still sounds like a failure on the part of MS. It seems that every Win
update brings fresh issues, from broken printer drivers, to stuff such as
Paul’s PSE 15 issue.

It seems to me that PSE is the problem, since both the current and
earlier version 13 failed in (presumably) the same way.

While Paul might have a responsibility to have PSE updated to match the
current incremental Win10 update, one should consider that it was an
incremental, not a major Win10 update that seems to have broken both editions
of PSE he uses.

It is a presumption that I would not count on that a spec will only be
implemented in a "major Win10 update". If the current version of PSE
runs on the current OS version, that says all that one needs to know
about where the problem lies.

Most developers plan and work on updates for their software in concert with
Beta releases of OS updates/upgrades.
That doesn't mean that they create compliant apps because Beta releases
don't always incorporate all aspects that are in the OS specifications
but the final release does. Developers have to stay "in step" by making
sure their apps are compliant, and while many do, some don't, choosing
not to fix the app until it's broken by a newer OS version. As I see it,
the issue is that it's critical to stay compliant now that Win10
delivers new OS versions frequently and without user interaction.

From the perspective of a macOS user it still looks like a uniquely Win10
issue. Fortunately for me Win10 is a non-issue, I have not used Windows of
any vintage since I retired in 2009. That does not mean that I cannot
appreciate Paul’s dilemma.

Isn't the perspective of non-Windows users pretty irrelevant when
addressing these kinds of issues? I'm speaking from decades of
experience with Windows and all kinds of apps, including some Adobe
apps, that have taught me to look into these issues from a fact-based
perspective that included reading MS' published specs. I still follow
these programming-related matters on a _daily_ basis.

--
best regards,

Neil