Codeview & Preview window sync broken - Page 2

KevinH · 07-30-2019, 12:13 PM

Actually, we can enable qDebug output to a file in Sigil on Windows but it would take a specific build change.

We can do that if need be.

Springbok · 07-30-2019, 12:42 PM

I am sure you guys have debugging tools for yourself to keep the work you are doing with Sigil, but I meant the utilities that"damn users" would understand too.

It is OK, I'll play with it together with Mister L, take it as a challenge. And of course I am open for any suggestions from you I should try.

DiapDealer · 07-30-2019, 12:58 PM

No. He meant we can literally create a special build of Sigil for you that will output debug content to a file that you can then get back to us.

KevinH · 07-30-2019, 01:08 PM

As for not updating when clicking on images, I took a look at that code in detail and that is not a bug. Preview to CodeView has always worked that way even under webkit. The javascript uses the document selection anchor to determine its position (that is how it always works). Clicking on an image will not change cursor/selection position. So the position returned is always unchanged until you click someplace in the text. Clicking on the image caption, clicking immediately before the image, clicking immediately after the image work because the document selection is then changed.

There really is no other position to reference as images are not part of the text to select.

Springbok · 07-30-2019, 01:11 PM

And this is a way I understood. It requires however some work of you guys so until other people do not come with the same problem (so far it is only me and Mister L) it is probably not worth an effort. Let's play with it and see.

Thank you all for the contribution, I am done for today.

DiapDealer · 07-30-2019, 01:16 PM

Quote:

Originally Posted by Springbok

And this is a way I understood. It requires however some work of you guys so until other people do not come with the same problem (so far it is only me and Mister L) it is probably not worth an effort. Let's play with it and see.

Thank you all for the contribution, I am done for today.

Actually. It's very little trouble at all for us to create a special build with some debugging turned on. The builds are automatic. We make a few tweaks, wait for the build to get done, and send you a download link to it. Bada-boom, bada-bing. Two users or two-hundred ... we'd like to get it sorted.

Springbok · 07-30-2019, 01:29 PM

I like this bada-boom, bada-bing...

If this is not to much hussle for you guys that perhaps this could be a good idea. Prepare then this build for download and I play with it tomorrow while you guys sleep. I would only need few simple instructions for what I should do exactly.

KevinH · 07-30-2019, 02:15 PM

I have already enabled a bunch of debug. I will push it to master of Sigil now.

KevinH · 07-30-2019, 02:19 PM

Enabled a bunch of sync related debug output and pushed it to master.

DiapDealer · 07-30-2019, 02:58 PM

I'll PM them a link to the Appveyor download (with instructions to get the logging-to-a-file going).

Mister L · 07-30-2019, 04:03 PM

Quote:

Originally Posted by KevinH

As for not updating when clicking on images, I took a look at that code in detail and that is not a bug. Preview to CodeView has always worked that way even under webkit. The javascript uses the document selection anchor to determine its position (that is how it always works). Clicking on an image will not change cursor/selection position. So the position returned is always unchanged until you click someplace in the text. Clicking on the image caption, clicking immediately before the image, clicking immediately after the image work because the document selection is then changed.

There really is no other position to reference as images are not part of the text to select.

Ha okay. Very good to know. Frustrating, but good to know.

Quote:

Originally Posted by DiapDealer

Actually. It's very little trouble at all for us to create a special build with some debugging turned on. The builds are automatic. We make a few tweaks, wait for the build to get done, and send you a download link to it. Bada-boom, bada-bing. Two users or two-hundred ... we'd like to get it sorted.

Quote:

Originally Posted by KevinH

I have already enabled a bunch of debug. I will push it to master of Sigil now.

Quote:

Originally Posted by KevinH

Enabled a bunch of sync related debug output and pushed it to master.

Quote:

Originally Posted by DiapDealer

I'll PM them a link to the Appveyor download (with instructions to get the logging-to-a-file going).

You guys are amazing. Thanks for all your hard work. I'll be very happy to try a debugging version and send you the logs, just let me know what to do.

DiapDealer · 07-30-2019, 04:48 PM

Quote:

Originally Posted by Mister L

I'll be very happy to try a debugging version and send you the logs, just let me know what to do.

PM sent.

Mister L · 07-30-2019, 05:20 PM

Quote:

Originally Posted by DiapDealer

PM sent.

PM received. Did you get my reply? I couldn't download the file, got an error message saying "Project not found or access denied". :/

On the bright side I am pretty sure I created the necessary variable:
WINDOWS_SIGIL_DEBUG_LOGFILE=
F:\exes\sigil\__sigil_debug\sigil-logfile.txt

Mister L · 07-30-2019, 05:56 PM

Ok, I've installed the debug version and stuff is getting written to the logfile.

No bug yet but it's late here so that's all for now.

Ironically I am now between projects as I finished the one I was working on earlier but I will just play around randomly doing stuff that looks like work and see what eventually happens.

DiapDealer · 07-30-2019, 06:44 PM

Feel free to delete the logfile if you happen to close Sigil before the disconnect happens. That way, we can try to keep the size down. If nothing happened that session, you may as well start the next session with an empty log file, in other words.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Preview to CV sync broken?	theducks	Sigil	5	02-13-2019 06:20 PM
Clicking in preview window not working	mrmikel	Editor	3	01-17-2014 10:29 AM
Preview Window Zoom	GrannyGrump	Sigil	16	06-16-2013 11:23 PM
Syncing bug in preview window	sellew	Sigil	13	02-26-2013 02:10 PM
Preview window - two small points	exaltedwombat	Sigil	12	02-21-2013 06:48 PM

07-30-2019, 12:13 PM	#16
KevinH Sigil Developer Posts: 8,156 Karma: 5450818 Join Date: Nov 2009 Device: many	Actually, we can enable qDebug output to a file in Sigil on Windows but it would take a specific build change. We can do that if need be.

07-30-2019, 12:42 PM	#17
Springbok Enthusiast Posts: 30 Karma: 10 Join Date: Jan 2018 Device: Kindle Touch	I am sure you guys have debugging tools for yourself to keep the work you are doing with Sigil, but I meant the utilities that"damn users" would understand too. It is OK, I'll play with it together with Mister L, take it as a challenge. And of course I am open for any suggestions from you I should try.

07-30-2019, 12:58 PM	#18
DiapDealer Grand Sorcerer Posts: 28,039 Karma: 199464182 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	No. He meant we can literally create a special build of Sigil for you that will output debug content to a file that you can then get back to us.

07-30-2019, 01:08 PM	#19
KevinH Sigil Developer Posts: 8,156 Karma: 5450818 Join Date: Nov 2009 Device: many	As for not updating when clicking on images, I took a look at that code in detail and that is not a bug. Preview to CodeView has always worked that way even under webkit. The javascript uses the document selection anchor to determine its position (that is how it always works). Clicking on an image will not change cursor/selection position. So the position returned is always unchanged until you click someplace in the text. Clicking on the image caption, clicking immediately before the image, clicking immediately after the image work because the document selection is then changed. There really is no other position to reference as images are not part of the text to select.

07-30-2019, 01:11 PM	#20
Springbok Enthusiast Posts: 30 Karma: 10 Join Date: Jan 2018 Device: Kindle Touch	And this is a way I understood. It requires however some work of you guys so until other people do not come with the same problem (so far it is only me and Mister L) it is probably not worth an effort. Let's play with it and see. Thank you all for the contribution, I am done for today.

07-30-2019, 01:29 PM	#22
Springbok Enthusiast Posts: 30 Karma: 10 Join Date: Jan 2018 Device: Kindle Touch	I like this bada-boom, bada-bing... If this is not to much hussle for you guys that perhaps this could be a good idea. Prepare then this build for download and I play with it tomorrow while you guys sleep. I would only need few simple instructions for what I should do exactly.

07-30-2019, 02:15 PM	#23
KevinH Sigil Developer Posts: 8,156 Karma: 5450818 Join Date: Nov 2009 Device: many	I have already enabled a bunch of debug. I will push it to master of Sigil now.

07-30-2019, 02:19 PM	#24
KevinH Sigil Developer Posts: 8,156 Karma: 5450818 Join Date: Nov 2009 Device: many	Enabled a bunch of sync related debug output and pushed it to master.

07-30-2019, 02:58 PM	#25
DiapDealer Grand Sorcerer Posts: 28,039 Karma: 199464182 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	I'll PM them a link to the Appveyor download (with instructions to get the logging-to-a-file going).

07-30-2019, 05:56 PM	#29
Mister L Groupie Posts: 173 Karma: 91148 Join Date: Jun 2010 Device: Sony 350	Ok, I've installed the debug version and stuff is getting written to the logfile. No bug yet but it's late here so that's all for now. Ironically I am now between projects as I finished the one I was working on earlier but I will just play around randomly doing stuff that looks like work and see what eventually happens.

Advert

Advert

07-30-2019, 06:44 PM	#30
DiapDealer Grand Sorcerer Posts: 28,039 Karma: 199464182 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Feel free to delete the logfile if you happen to close Sigil before the disconnect happens. That way, we can try to keep the size down. If nothing happened that session, you may as well start the next session with an empty log file, in other words.