Beta testers for calibre 2.0 needed

[kovidgoyal]

https://github.com/kovidgoyal/calibr...65c50c3729a5bb

[DNSB]

Originally Posted by theducks

There is something wierd going on.
I disconnected the second monitor. REBOOTED
Started Calibre
Attached my TAB2
Opened the Task Manager
Column heads: Job Status Progress Running_Time JOB

Only Job has info and I can't resize column widths

NB Same cols on 32 bit XP, same lack of resize
BUG

Not sure if this is related but when I started playing with the beta, I had some odd issues with the Job Manager where columns couldn't resize, running and start time did not show, etc.

I ended up (Windows 7 x64) uninstalling Calibre 1.203.1 and blowing away the user directories (calibre and calibre_cache). After the reinstall everything worked okay again. As I commented then, I hit the patient in the head with an axe and it got better.

Regards,
David

[kovidgoyal]

Well, I have changed the name of the preference used to store the jobs dialog's column layout, which will take care of the problem of any stored stale data.

[theducks]

Originally Posted by kovidgoyal

Well, I have changed the name of the preference used to store the jobs dialog's column layout, which will take care of the problem of any stored stale data.

Thanks. Was there a small hack I could do to get status and progress back without wiping all the other settings? ( I assume the stale data is in hiding somewhere in the config folder)

[kovidgoyal]

It is in gui.json, look for "jobs view column layout2"

[theducks]

Originally Posted by kovidgoyal

It is in gui.json, look for "jobs view column layout2"

Thanks,
I had peeked there before, obviously, I did not know what I was really doing

[kacir]

I use AutoKey program for automating certain tasks.
One example is searching for author in Calibre in such a way that it doesn't matter whether I have firstname lastname or lastname, firstname.

Program that is run when I press F2 in my AutoKey is:

#### Beginning of the Script for F2 hotkey ####
import re

contents = clipboard.get_clipboard()

# re.sub(pattern, repl, string, count=0, flags=0)
output = re.sub(r'([^ ,]*),? (.*)', r'authors:"\1" and authors:"\2"', contents)

keyboard.send_keys(output)
#### End of the Script for F2 hotkey ####

It works in a simple way:
I find somewhere (Calibre itself, or Internet or any text) name of the author, I copy the name such as:
Hugo, Victor
to the clipboard, then I go to Calibre, position cursor to the Search bar and press F2. I get the following
authors:"Hugo" and authors:"Victor"
Well, I *used* to get that. In Beta when I use this script, I get
authors.;hugo; and authors.;victor;
In any other program where I can enter text this works OK.

My system:

Spoiler:

kacir@Petra:~ > calibre-debug -g
calibre 1.205 isfrozen: True is64bit: True
Linux-3.11.0-12-generic-x86_64-with-debian-wheezy-sid Linux ('64bit', 'ELF')
('Linux', '3.11.0-12-generic', '#19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013')
Python 2.7.8
Linux: ('debian', 'wheezy/sid', '')

I can (and probably will) find a workaround by extending my script from four lines to eight ;-), but this behavior might indicate some problem.

I used to have this tiny hack built into Calibre as modification to the "find similar books" function, and I have even tried to persuade you to put it into main trunk.

[kovidgoyal]

keyboard handling is done entirely by Qt, no calibre code involved, not much I can do about it.

[BetterRed]

Originally Posted by kacir

I use AutoKey program for automating certain tasks.
One example is searching for author in Calibre in such a way that it doesn't matter whether I have firstname lastname or lastname, firstname.

@kacir - there's a plug-in that does something like that ==>> [GUI Plugin] Clipboard Search

I did a few tests on the Qt5'd version the other day on Windows 7, under calibre 1.48 64-bit & calibre 1.205 portable, seems to work as advertised. The Qt5d version is released, so you can install via Prefs->Plug-ins->Get New.

BR

[arspr]

Wow, I missed this thread although I had noticed that I could not run from source since last weekend..., (well, I could because I kept my version old enough, not merged with the tracking master branch). Some message about Qt5whatever missing...

Originally Posted by kovidgoyal

Just a heads up for people running from source. I have now merged the qt5 branch into master. This means that if you want to run from source, you have to use the beta version of calibre.

There's something strange here. I've installed the beta version, I've updated my source and now I cannot run from source because PyQt4 is missing...

I upload three screenshots:

• The Qt4 error Calibre gives on launch.
• A snapshot of Git GUI. So you can see the version I'm using. (Remember my changes are irrelevant about this issue, they're just about how non-linear items are managed/displayed).
• A screenshot of dnGREP running through calibre source. In fact, there seem to be a lot of "PyQt4" in the code.

Am I doing something wrong?

[chaley]

Originally Posted by arspr

Am I doing something wrong?

This happened to me as well. The problem is that the generated user interface files are not regenerated. Recursively delete all *_ui.py files and you will be fine.

[arspr]

Originally Posted by chaley

This happened to me as well. The problem is that the generated user interface files are not regenerated. Recursively delete all *_ui.py files and you will be fine.

Solved



Nevertheless, with the transition, if this is going to automatically happen I suppose you should add a clear warning in the manual, release notes or wherever, about this issue. Or possibly a lot of noobs, like myself, are going to ask the same question.

[gers1978]

I'm using the portable beta on Windows 7, and when I open Preferences the window is tiny and can't be manually resized, I had to use the Maximize button to see all the preferences.

[kovidgoyal]

Strange the preferences window is fully resizable for me on windows 7

[gers1978]

Originally Posted by kovidgoyal

Strange the preferences window is fully resizable for me on windows 7

Ok, just tried again, and indeed it is resizable now, not sure what happened before.

Also not sure why it open so tiny in the first instance, but all good now.