As we can see from the answers to my question, some users are very happy on Zim running on Windows 64-bit, but some others don't. The copy-paste problem seems to be restrict to a group of users. Why? What are the differences between them?

Maybe there is a flaw in the way GTK2 interacts with windows 64-bit clipboard, but maybe GTK2 is not the only culprit for this problem. Chances are that a detail in system configuration, or maybe a 3rd party application, which is not present in all systems, is conflicting with Zim's clipboard operation.


As a debug procedure I would suggest closing all 3rd party applications running in background in search of possible source of conflict with Zim's copy and paste operation. Applications such as memory optimizers and performance boosters are potential suspicious, but any other silly application can be the bandit. Also consider checking plugins, add-ons and extensions of other main applications. Disable all and re-enable them one by one.

I know this is a bit tedious and time consuming task, but if you find the culprit that will be your passport to heaven after years living in hell.

Just to illustrate my point, maybe 2 years ago, I reported a bug on Zim's Ctrl+D shortcut which sometimes failed. Maybe Jaap remembers the case. By that time I was absolutely sure that there was a bug in Zim code. But, after a week or two, just by chance, I found a conflict between Zim and a dictionary which had a shortcut Ctrl+D+D. Running each application in separate, Zim or dictionary, they performed well, but running both applications together, the dictionary interfered in Zim's behavior. In that case, the solution was just change the dictionary shortcut to Ctrl+C+D.

mtibbi
===========


Em 24/04/2017 19:35, Brendan Kidwell escreveu:
I see from my debug log file ...

DEBUG: Action: copy
DEBUG: Clipboard requests data as 'UTF8_STRING', we have a parsetree
DEBUG: Clipboard requested text, we provide 'plain'
DEBUG: Clipboard requests data as 'text/x-zim-parsetree', we have a
parsetree
DEBUG: Clipboard requests data as 'text/html', we have a parsetree
DEBUG: Clipboard requests data as 'HTML Format', we have a parsetree

we are getting to here
https://github.com/jaap-karssenberg/zim-desktop-wiki/blob/master/zim/gui/clipboard.py#L416
, each time I type CTRL-C, and apparently sometimes putting null or an
empty string into the selectiondata.set_text() method, because Free
Clipboard Viewer 3.0 shows NO "Text" fragment on the clipboard sometimes.

If I watch Free Clipboard Viewer 3.0, it seems I get a random selection
of various fragment types present and not present, each time I copy to
the clipbpard.

I'm putting this into the ticket in Launchpad.

On Mon, Apr 24, 2017, at 17:41, Brendan Kidwell wrote:
*Jaap*, I tried "Free Clipboard Viewer 3.0" just now ad on the very
first try when I copied to the clipboard it looked like Steve's
"bad.png". There was actual HTML data in the "HTML Format" and
"text/html" fragments, but there was no plaintext fragment. Thus, when
I paste to a plaintext widget in another program, there is nothing to
paste.

After repeating the Copy command on the exact same selected text, I
got plaintext.

I am going to try to build a 64-bit package tonight from the
unreleased 0.66 code and see if it behaves any better (assuming there
are 64-bit builds of all the dependencies which I can use), but I'm
not expecting it to change anything.


On Mon, Apr 24, 2017, at 10:07, Steve Chadsey wrote:
I am using Windows 8.1 64-bit and this issue has been an annoyance
for as long as I can remember (at least 2 years) throughout multiple
Zim releases.
I've installed a visual clipboard viewer, "Free Clipboard Viewer 3.0"
which immediately shows the clipboard contents whenever something is
copied.  I'll run the program, then highlight something in zim and
attempt a copy with "Ctrl+C".  When something is successfully copied,
the viewer will show something like the attached "ok.png".  When
something is not copied, I'll see something like "bad.png".  I can
highlight some text in zim and hit "Ctrl+C" repeatedly and see the
contents of the clipboard contain nothing somewhere between 30-50% of
copy attempts.

I would be happy to help troubleshoot further since the problem is
very reliably reproducible on my environment.
Thanks,

On Sun, Apr 23, 2017 at 5:18 PM, Marcio Tibirica
<marcio.tibir...@gmx.com <mailto:marcio.tibir...@gmx.com>> wrote:

    This seems to be a HUGE problem that can put in risk the future
    of Zim on the windows platform. Does anyone know if all Zim users
    in 64-bit Windows environment are having the same problem?

    mtibbi
    ===========


    Em 23/04/2017 00:40, Brendan Kidwell escreveu:

        This isn't definitive evidence, but the only Windows that
        I've used Zim
        with for years has been Windows 8.1 64-bit and Windows 7
        64-bit. At
        least once per week I get bit by the copy-didn't-do-anything
        bug or some
        other clipboard exception. I can't provide a list of steps to
        reproduce
        and I can't come up with any ideas for how to make the
        problem go away.

        I will continue to act as the maintainer the Windows build of
        Zim with
        the most recent release of GTK 2 each time, but honestly this
        is the
        main reason I've moved by work diary out of Zim and into
        PiggyDB. (I am
        required to use Windows 7 64-bt for my job.)

        Any help in fixing this would be appreciated. I know next to
        nothing
        about GTK 2 and I am not going to be the person who solves it.


        On Sat, Apr 22, 2017, at 14:15, Marcio Tibiriçá wrote:

            Hi Udo,

            Your case is really weird. Maybe something related to
            64-bit core?
            I have used Zim in both Win7 and Win10 without having
            problems with
            copy and paste to other applications. But in my case both
            machines are
            32-bit.
            Maybe somebody else running Zim on Win 64-bit can bring
            some clue on
            your issue.

            mtibbi




        _______________________________________________
        Mailing list: https://launchpad.net/~zim-wiki
        <https://launchpad.net/~zim-wiki>
        Post to     : zim-wiki@lists.launchpad.net
        <mailto:zim-wiki@lists.launchpad.net>
        Unsubscribe : https://launchpad.net/~zim-wiki
        <https://launchpad.net/~zim-wiki>
        More help   : https://help.launchpad.net/ListHelp
        <https://help.launchpad.net/ListHelp>


    _______________________________________________
    Mailing list: https://launchpad.net/~zim-wiki
    <https://launchpad.net/~zim-wiki>
    Post to     : zim-wiki@lists.launchpad.net
    <mailto:zim-wiki@lists.launchpad.net>
    Unsubscribe : https://launchpad.net/~zim-wiki
    <https://launchpad.net/~zim-wiki>
    More help   : https://help.launchpad.net/ListHelp
    <https://help.launchpad.net/ListHelp>




--
Steve Chadsey <schad...@gmail.com <mailto:schad...@gmail.com>>
_________________________________________________
Mailing list: https://launchpad.net/~zim-wiki
Post to     : zim-wiki@lists.launchpad.net
<mailto:zim-wiki@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Email had 2 attachments:

 *
    |bad.png|
      19k (image/png)
 *
    |ok.png|
      23k (image/png)

_________________________________________________
Mailing list: https://launchpad.net/~zim-wiki
Post to     : zim-wiki@lists.launchpad.net
<mailto:zim-wiki@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~zim-wiki
Post to     : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~zim-wiki
Post to     : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Reply via email to