1.0.2rc3 is Released

August 8, 2011 – 1:34 am

The source can be downloaded here.

Here are the debian binaries (.deb) files:
i386
amd64.

v1.0.2rc3 Sunday, August 7 2011
Changes
+Fixed xdg compliance, based on patch by Victor Ananjevsky.
+Fixed Status Icon missing on execute Action.
+Fixed Capture Hyperlinks only
+Added Ignore Whitespace only
+Added Trim Whitespace
+Added Trim Newlines
+Fixed Actions having HTML markup in the clipboard entry.
+Fixed goption warning (pending verification).
+Updated Russian (Alexander Kazancev).
+Updated Catalan translation, position type. (Fuertes::Benjami)

I still have work to do, but many of the annoying bugs are gone.
Search-as-you-type still doesn’t work with all languages. I need to get with some friends of mine who have a different keyboard to debug this.

The documentation on the Ctrl/Shift right click behavior on the history just now made it into SVN. It will show up in rc4. I’m seriously considering adding a ‘permanent’ history list - perhaps with a drag/drop between the current history and the new one - and it would come up with a different hot key, or perhaps with menu item on the normal history menu. Still figuring this one out. Someone suggested this idea, and it occurred to me that I would use it a lot.

Enjoy!

  1. 8 Responses to “1.0.2rc3 is Released”

  2. Plans for a GTK3 port?

    rickyrockrat: Not at this time. The nice thing about Parcellite currently is that it works all the way back to Gutsy. I like to move nice and slow. I’m not at all sure it won’t compile with GTK3 as-is. Care to test it for me? I’ll give you the line you need to mess with for configure to work.

    By Taylor001 on Aug 10, 2011

  3. Oh come on! Forget about release candidate and bump the third version up!

    Parcellite is rock solid!

    By lzap on Aug 12, 2011

  4. thanks! use it at work every day!

    By John on Aug 15, 2011

  5. Noticed one issue that caused me to downgrade back to rc2. Text is fine, but for some reason files need to be copied twice before they can be pasted/moved.

    RickyRockRat: This should be fixed in RC5. Sorry for the trouble!

    By Mike on Aug 19, 2011

  6. Is there a reason that the maximum allowed history is 100? I imagine that some people like this because of privacy reasons, but I am the only one using my computer and would benefit from a larger history. But maybe there is some programming issue that I don’t know about.

    I also like the idea of a permanent history.

    In any case, thank you for everything. Parcellite is working great now and I agree that you have squashed all of the annoying bugs.

    Thanks,

    G

    By Gerard on Aug 28, 2011

  7. Gerard,
    No reason on the 100 limit. For me, it’s impractical to have more, but I think I change that spin box to go up to 1000 or so. What limit is reasonable? I hate to leave it free form, since someone will inevitably put it at 1G, then wonder why their computer grinds to a halt every time you hit parcellite history.

    It helps if you turn on the Ignore white space only.

    By rickyrockrat on Sep 4, 2011

  8. +1 for increasing history limit! I’ve just done it changing two lines in the sources (preferences.c, L182 and L522), so now it’s 1000 and I happily use 500 setting =)

    One thing annoying me though: sometimes I pop up the history and it’s all starkly red! Become normal again if some item is chosen.

    rickyrockrat: Turn off ’search as you type’. Red indicates the entry is not found. I suspect you accidentally hit a key while history is up.

    By Allis on Sep 4, 2011

  9. rickyrockrat,

    good point of at least having *some* limit. I have been thinking about what would be a reasonable limit and can’t think of a logical argument. I would personally like up to at least 1000.

    An alternative, although it would be more complicated to program, would be to have an archive. The last entry in parcellite could be labeled “Archive” that when it is selected it displays older items. The user could specify an option to determine whether the archive is searched in search as you type. This seems like too much work though.

    Thank you!
    rickyrockrat: I like that idea a lot. I think ‘archive’ could be a separate history file, so it doesn’t have to be loaded, and editing would have a check box to move from one history to another. Also solves the persistent history idea, which initially would have been huge code changes. Good idea. Thanks

    By Gerard on Sep 5, 2011

You must be logged in to post a comment.