Hi,
I often get a frame crash when scrolling a page horizontally.
Error message: Crash in HScrollTrack: 2044
This happens when I’m working with a remote screen (or beamer, while giving
training…) or even on my laptop screen. I’m using Windows7 Ultimate running in
Parallels (lots of memory
I can tell you that you're not alone. :-(
I'm running the same environment. Horizontal scroll on an unsaved file
... boom. Never fails. I see this most often in structured mode, but I
do most of my work in that mode.
I always assumed it was my Apple Magic Mouse(TM), but perhaps not.
I don't
Hi Wim,
I recently posted a similar question. I also have Windows Ultimate with
lots of RAM (16 GB) and dual processors (Intel Core i7-4700MQ 2.4GHz).
FrameMaker 9 crashes when I scroll in the Open dialog. I didn't get a
definite answer. I was told to reinstall FrameMaker or to reinstall my OS.
I
Hi Vikram,
this is both in structured and unstructured mode.
Not only FM12, same in FM10 and FM11.
I’ll send you a screenshot later.
Vriendelijke groet / Kind regards,
Wim Hooghwinkel
June 19-20 Congility 2014 - Closing the loop with FontoXML
tel. +31652036811
Skype wimhooghwinkel
Twitter
Hi Alan,
I also had the impression it had to do with the mouse. But lately it aso
happened when my mouse was dead (battery…).
Especially when a book is open (or a ditamap) and some pods/panels, the
document screen gets smaller and can not show the complete page. Scrolling left
or right causes
My name is Amy Hamid, Recruiter with Intercom Consulting and Federal Systems, a
Government integrator in the DC Metro area. I'm contacting you about a
potential opportunity with our organization.
We are currently looking for a temporary (2-3 months) FrameMaker Developer who
would be able to
Makes me wonder if it is a buffer or video driver issue.
Grant
On June 24, 2014 at 8:39 AM Wim Hooghwinkel - idtp w...@idtp.eu wrote:
Hi Alan,
I also had the impression it had to do with the mouse. But lately it aso
happened when my mouse was dead (battery…).
Especially when a book is
OK, this really isn't a slam -- honest.
But you guys are complaining about buggy behavior in an operating
environment, an emulator, that is not supported by Adobe. And from the
sound of it, it's a pretty good bet that the device drivers for monitors or
UI devices and the lack of signalling
I think that the difference here is that this probably *only* happens
with FM. If it was all (or at least other) apps, then it would likely be
an OS or VM issue, but if it's just FM, then there's probably something
slightly incompatible being done in FM that Adobe should be aware of.
Granted,
At 10:57 -0400 24/6/14, Art Campbell wrote:
But you guys are complaining about buggy behavior in an operating environment,
an emulator, that is not supported by Adobe.
I'm sure this is true, Art, but I'm also fairly sure that it's an operating
environment that Adobe would nevertheless wish to
I'm pleased to hear this!
I would like to acknowledge Saibal and the rest of the FrameMaker team
for the amount of personal attention they provide to members of the
FrameMaker community. We often forget that FrameMaker is a deep, rich,
complex product, with many different business
11 matches
Mail list logo