Jump to content

JoyAllen

Members
  • Content Count

    6
  • Joined

  • Last visited

About JoyAllen

  • Rank
    Newbie

Recent Profile Visitors

212 profile views
  1. I am working on Win 10, with a Wacom tablet. Sometimes things are fine, usually after the machine has been rebooted. But during a session, suddenly the node cursor goes black. I stop seeing the yellow snapping suggestion, and I only see the result of a drag or node create after it has finished.Is there a list somewhere of what all the different cursors mean? Is there some way of getting out of this mode without closing the app and rebooting the machine. I have to say I never had this issue before V 1.7. Two versions in from 1.7.0 and it is still not fixed.
  2. OK, I got a bit excited. My apologies for being a bit rude. I had a task I'd been putting off, so I was frustrated in my good intentions. This morning, things seem to be back to normal. For the record, it is a Win 10 Home machine, v 1803, os build 17134.829. product version is 1.7.0.367. I was using my Wacom tablet and stylus. Periodically I do have problems with the tablet, particularly with the cursor not updating to the correct one for the tool being used. A reboot generally fixes things. For now I will get back to work. If I have further problems that seem related, I may post again. Thank you for your attention to my problem.
  3. Response is super slow, I can't drag objects, I have to click twice to place a node with the pen - my product has gone from being a great tool to being unusable. Drawing with the pencil I get a straight line from first click to last. Cursor over an object shows incorrectly as a transform handle. It's broken!!
  4. Sounds like a plan - OK I tried that, and it made no difference at all. Has anyone looked at the exception?
  5. I have an intuos 3 WACOM tablet. I can use the pen to start creating a new file, but as soon as that is done the product crashes. Here is the text of the exception... System.OverflowException was unhandled HResult=-2146233066 Message=Arithmetic operation resulted in an overflow. Source=Serif.Affinity StackTrace: at Serif.Affinity.Application.HandlePointerInput(MSG msg) at Serif.Affinity.Application.ComponentDispatcher_ThreadFilterMessage(MSG& msg, Boolean& handled) at System.Windows.Interop.ComponentDispatcherThread.RaiseThreadMessage(MSG& msg) at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) at System.Windows.Application.RunDispatcher(Object ignore) at System.Windows.Application.RunInternal(Window window) at Designer.Application.Main(String[] args) InnerException: That should be pretty easy to track down, I would think. I use a laptop, and if I start Designer and just use the glide pad on the laptop I have no problems, so its just the tablet. But until this is fixed, my 60 bucks is money down the drain folks - I can't do graphic design with a glide pad, not really. Joy Allen
  6. Windows 10, latest build, on an oldish Toshiba laptop. I have a WACOM tablet, an Intuos 3 which I attach via USB. Leaving the tablet disconnected, first trial is just using the glide pad on the laptop. Another issue with a WACOM tablet..... Here's what I did .. Detach tablet. Start Designer from a tile. I previously turned off the welcome screen with its ugly sample graphics. File New - new document dialog, with all the default settings. Click OK. New document appears. Try a few things, all seems good. I attach the tablet, and Designer immediately crashes. Leaving the tablet attached, start Designer again. File>New, OK as before, but using the stylus on the tablet. Get a document. As soon as I move the pointer using the stylus, Designer crashes. The detail of the exception is pasted below - luckily I have VS 2010 installed on this machine. System.OverflowException was unhandled HResult=-2146233066 Message=Arithmetic operation resulted in an overflow. Source=Serif.Affinity StackTrace: at Serif.Affinity.Application.HandlePointerInput(MSG msg) at Serif.Affinity.Application.ComponentDispatcher_ThreadFilterMessage(MSG& msg, Boolean& handled) at System.Windows.Interop.ComponentDispatcherThread.RaiseThreadMessage(MSG& msg) at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) at System.Windows.Application.RunDispatcher(Object ignore) at System.Windows.Application.RunInternal(Window window) at Designer.Application.Main(String[] args) InnerException: I'm pretty sure I tried using the tablet with the beta, so this is surprising.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.