Jump to content
You must now use your email address to sign in [click for more info] ×

dlampel

Members
 View Profile  See their activity

  • Posts

    83

  • Joined

  • Last visited

Reputation

25 Neutral

See reputation activity

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1.    Patrick Connor reacted to a post in a topic: Affinity Suite: Error Management
  2.    Leigh reacted to a post in a topic: Affinity Suite: Error Management
  3.    Dan C reacted to a post in a topic: Affinity Suite: Error Management
  4. dlampel
    To all who have participated in this conversation I want to report that I tested the issue (right-click in text frame when document floated to a second monitor) in Beta 2.4.0.2256 with success. No crash! Thank you to all those who contributed to this fix. By the way, just a reminder: An easy workaround is to keep the documents in the UI and float the control panels to the secondary monitor. This workflow I have been successfully using for the last few weeks (in v2.3).
  5.    Patrick Connor reacted to a post in a topic: Affinity Suite: Error Management
  6.    Leigh reacted to a post in a topic: Affinity Suite: Error Management
  7.    Patrick Connor reacted to a post in a topic: Affinity Suite: Error Management
  8.    dlampel reacted to a post in a topic: Affinity Suite: Error Management
  9.    Dan C reacted to a post in a topic: Affinity Suite: Error Management
  10. dlampel
    Just a quick follow-up to my last post. Using the 2.4 Beta I arranged the Publisher UI with an open document on my left-hand monitor, and all my control panels on my right-hand monitor. When I right-clicked on some text, the program did not crash. That is, by leaving the document in the UI, it did not crash.
  11. dlampel
    Dan, You mean, there might actually be a resolution to this at some point? Be still my heart! Seriously, I really do appreciate the efforts of the Affinity crew. Perfection in any computer program cannot and should not be expected, but it goes a long way to securing a user base when the team behind it will be as diligent as yours to ferret out the imperfections and address them. Thank you. By the way, until the fix is published I thought I might reverse my workflow to this. Instead of having all my panels remain in the UI and dragging documents to the other monitor, I might try (if possible; I may try this in the 2.4 Beta) keeping the documents in the UI and just place the panels in the other monitor--which means no docs will be forced to change DPI from the original UI.
  12.    Leigh reacted to a post in a topic: Affinity Suite: Error Management
  13. dlampel
    Thank you for all the helpful information. Frankly a lot of it was above my pay grade; difficult for me to understand--especially all the acronyms. But when I returned and reread (and looked up the meaning of the acronyms) I concluded you may be on to something. For my two monitors are not identical. The one on my right, displaying the Publisher program, is an older, slightly lower resolution monitor than the one on my left, to which I drag document windows. So I am going to dig into this possibility, following your suggestions, to see if it helps, and will report back. Thanks again for taking the time to help.
  14. dlampel
    I am not ungrateful for the work done on this situation by the Affinity crew, but, honestly, this is getting to be truly frustrating for me. Today I began working on a monthly newsletter, based on a tried and true template of my own creation. Did this, did that, imported/copied text, moved frames about, inserted graphics, etc. All handled perfectly--until I accidently right-clicked in a text frame. Crash. Disappear. C'mon guys, this is basic!
  15.    Leigh reacted to a post in a topic: Affinity Suite: Error Management
  16.    Leigh reacted to a post in a topic: Affinity Suite: Error Management
  17. dlampel
    I have been doing more testing and have discovered an environment that causes reproducible crashes. Tests were run in both 2.3.1 and 2.4 Beta with identical results. I tested with files created from long-standing templates of my own, current files not created from templates, and brand New files with Filler Text. The more recent tests were conducted after a reboot. My working environment is to have Publisher with a large number of open Panels displayed in my right-hand (physical) monitor, with the display and editing of my documents floated in my left-hand (physical) monitor. Here are the results: The right-click crash never occurred when documents were not floated to my left-hand monitor, but instead left inside the Publisher UI. The right-click crash usually, but not always occurred when the documents were floated in my left-hand monitor.
  18. dlampel
    Well, that didn't take long. Downloaded and installed the 2.4 Beta. Repeated the identical steps--with an identical result: Crash -> Disappear. By the way, this was not an old file in which I had experienced the same problem. This was a new file created since we last corresponded. I next opened a brand New File in 2.4 (not from one of my templates) and filled a new frame with Filler Text, right-clicked--no problem: context menu displayed properly. So I am wondering if the root of this problem lies in my templates, some of which I have been using for years, but I have regularly made new versions as Publisher has updated/upgraded the program. Just in case there is something to be gleaned from them at your end, I am attaching both the end document, and the template from which it was created. Reflect0885.afpub Reflections_2023-24_portrait_1 column_v2.2.aftemplate
  19. dlampel
    Leigh, I updated both of the drivers you recommended, as well as all that were recommended by the manufacturer (Dell). That was a day or two ago. I just now loaded Publisher 2.3.1, and opened a recent document. I changed from the Move Tool to the Frame Text Tool, clicked inside an existing paragraph, and right-clicked. The program froze, then a few seconds later disappeared. I just loaded Publisher again, and repeated the same steps. Crash. I am now downloading the 2.4 Beta, and will report back later.
  20. dlampel
    Not at all. I appreciate the efforts to ferret out the cause of these problems. Log.txt
  21. dlampel
    A timely follow-up: Just a moment ago I opened one of my newsletter templates, pasted in the text of the lead article, right-clicked on a word marked as misspelled (even though it wasn't), and Publisher paused for about 5 seconds, then disappeared.
  22. dlampel
    Thank you for your response, Leigh. I can understand the inability to replicate this problem, for it is certainly not consistent. But, to answer your question, yes, it still occurs from time to time even in 2.3 (Note: I am now back to running the Affinity EXE programs, instead of the apps. They seem more stable for me.). Attached is the Log.txt file you requested. I use a wired mouse (Logitech) without any third-party drivers or software--just your basic mouse. And this errant behavior never occurs in any other programs. Although it may not be pertinent to this bug, I am still (once in a while) experiencing the same inexplicable crash mentioned in my original post, which seems to occur more often than not when opening a second file. The program freezes for about 10-15 seconds, then disappears. Log.txt
  23. dlampel
    Pastor's Pen - Assurance and Perseverance_edit.docx
  24. dlampel
    Just a thought: Perhaps the right-click crashing has something to do with the content in the Clipboard. The content each time the program crashed was word processor text. Today, however, I have been working on an anniversary card. I had placed four pix on the page 1 layout board and wanted to move them all to page 2. I selected the four images, right-clicked, and selected Paste without incident. But when the Clipboard contained simple text, just right-clicking would crash the program. (Nothing wrong with the text; using CTRL-V it was placed without issue.)
  25. dlampel
    The drive that the program runs on--OS (C:)--has 765 GB free space, and the drive (partition) that contains the working document files has 420 GB free space.
  26. dlampel
    Dan, I didn't know if this would work, since I am now running the updated v2.2.1, but it did crash, as before. Always before Publisher would almost immediately disappear. This time, my clicking in Task Manager seemed to halt the process (locking up the program without making it disappear from memory), but once the second DMP file was written, it did disappear. The attached ZIP file contains the two (rather large) DMP files. Publisher-DMPs.zip
×
×
  • Create New...

Important Information

Terms of Use | 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.

 Accept Cookies  Reject Cookies