Editing content.opf with clips; Editing visibility

[DiapDealer]

Originally Posted by KevinH

Then problem is even stranger. Linux Mint Cinamon with Adwaita and Qt 5.4.2 works according to DiapDealer's tests. But you are saying that Ubuntu-GNome with Adwaita and Qt 5.5.1 does NOT work. But eschwartz's version of Adwaita (see his link) does not have issues.

If that is true the only guaranteed QStyle to work on Linux seems to be the built-in Qt one ("fusion").

I wonder what QStyle - Doitsu's ClearLooks theme uses?

What a mess!

KevinH

To be honest ... Adawaita's not working for me either. When forcing a Qt style, the only one that works on my system is -style GTK+. Forcing any other style results in the exact same abomination that I assume is the result of missing styles (or missing Qt plugins for the style).

I'm out of my depth, really. I have no interest in creating/shipping a standard Sigil theme, to be quite honest.

[eschwartz]

@KevinH,

The Adwaita I linked is a compiled Qt plugin, not QGtkStyle translating the Gtk Adwaita CSS-based theme.

The ArchWiki does warn that QGtkStyle can be broken depending on the theme used (and do note that my Arch Linux box has been updated to Gtk 3.20 with gnome-themes-standard 3.20 as well -- which provides the gtk2 adwaita theme as well).


So... lots of moving parts, and the Year of the Linux Desktop is nowhere in sight as usual, but now we see one of the reasons why.
Also, you can probably blame the Gtk developers. They are at fault for enough these days -- this is most likely them too.

[KevinH]

varlog

If you are using Qt 5.5.1 with Ubuntu you might like to look at this bug report from Calibre that Kovid posted about today:

https://bugs.launchpad.net/calibre/+bug/1534936

It shows that Qt 5.5.1 and Ubuntu seems to have many issues.

KevinH

Originally Posted by varlog

Ubuntu-Gnome with Adwaita.

[varlog]

Originally Posted by KevinH

...
https://bugs.launchpad.net/calibre/+bug/1534936
...
KevinH

It is related to 15.10/Unity as far as I can see, I have 14.04/Gnome and Calibre is OK - so it's probably only fuzzy involved. Thanks anyway.

I know now enough to avoid this problem if I get really mad. Thanks.

[eschwartz]

Fortunately, we now know enough to be able to respond to bugreports with the statement "Your desktop theme is broken".

I suppose that *might* have to be enough.

[varlog]

Originally Posted by eschwartz

Fortunately, we now know enough to be able to respond to bugreports with the statement "Your desktop theme is broken".

I suppose that *might* have to be enough.

My desktop theme is OK, just the way standard Qt generalizes it is not perfect. This is my conclusion anyway.

[eschwartz]

Originally Posted by varlog

My desktop theme is OK, just the way standard Qt generalizes it is not perfect. This is my conclusion anyway.

to-may-to, to-mah-to

[varlog]

Originally Posted by eschwartz

to-may-to, to-mah-to

OK. thanks to Google I've understood this. Just don't say that Linux ¬(Just Works) .

[eschwartz]

I never said linux Just Works.

I did say I wish it did, and suggested that the continuedly aggressive failure to do so is why we are still waiting decades later for "The Year of the Linux Desktop".

[varlog]

Originally Posted by eschwartz

... still waiting decades later for "The Year of the Linux Desktop".

I'm not waiting and so do you.
My post says something different .

[KevinH]

varlog,

I have now reworked yet again large pieces of the pure xml handling in OPFResource, XMLResource, CleanSource, and xmlprocessor.py.

It tries to now leave untouched anything that is well-formed in its own right for pure xml.

So will you please make a pull from master and rebuild and still let me know if you still have trouble using clips when hand-editing in the content.opf.

Thanks,

KevinH

[varlog]

Same thing - my clip lands at the end of the file. Got some embedded Python error, too:

....xmlprocessor.py", line 192, in repairXML
    newdata = Opf_Parser(newdata).rebuild_opfxml()

AttributeError: 'Opf_Parser' object has no attribute 'rebuild_opfxml'

after this on right-click sometimes instead of context menu some dialog box appears - unreadable because filled with cut out fragment of actual Sigil window - forcing me to kill Sigil.

sorry...

[KevinH]

My bad,

Did not commit the new version of opf_newparser.py that has that rebuild_opfxml method.

I just committed it. A new pull should stop the error messages.

That said, I have been testing with clips and hitting return and then pasting clips and the current cursor position somehow gets lost (even on my Mac) but only randomly.

Somehow the cursor position is getting reset when focus is lost but not always for me.
Now that I can recreate this at least randomly, I will try to to trck down what is doing that.

I did notice that after hitting return, if I focus outside the tab and then focus back inside the tab and re-establish the cursor, the clip works as expected 100% of the time (or at least I could not get it to fail).

KevinH

[varlog]

Error is gone, the out-in trick works for me too.

[KevinH]

varlog

Originally Posted by varlog

Error is gone, the out-in trick works for me too.

Please try a new pull and build. I added a workaround to restore/reset the cursor position when focus is lost and an auto save is done.

Hopefully that will do the trick.

KevinH