[bt-devel] Proposed change for BibleTime
Daniel Owens
dcowens76 at gmail.com
Sun Nov 18 06:52:13 MST 2018
Gary,
Thanks for responding.
Just to clarify: I cannot copy within a verse, but that would be most desirable. Copying a range of verses can be done through the copy command, as you say. I am not at my computer now, but I believe it works because I tried.
The cantillation issue relates to one of the display filters, like words of Christ in red, footnotes, etc., which you can toggle on and off. I will check later whether the copy command works with that.
Daniel
> On 17 Nov 2018, at 7:42 PM, Gary Holmlund <gary.holmlund at gmail.com> wrote:
>
> Daniel,
>
> I am aware of this issue. Selecting text across a range of verses is mutually exclusive with the continuous scrolling feature. It might be possible for me to change it to allow selection within a verse, but not across multiple verses.
>
> I did change the copy command to allow choosing 1 or more verses and copying them. Does this not work for your case?
>
> I don't understand cantillation and how select/copy works with this. Could you explain this further?
>
> Gary
>
>
>> On 11/17/18 5:20 PM, Daniel Owens wrote:
>> Gary,
>>
>> I noticed a change in BT, and I am not sure if it is related to what you're doing to add continuous scrolling or not. Previously I could select and copy a short snippet of text by clicking and dragging along the text. Currently I cannot select the text at all. Are you aware of that?
>>
>> I ask because this is a feature I particularly like to use with Hebrew, since BT allows the user to hide the cantillation, which is super helpful when quoting a word or phrase in Hebrew.
>>
>> Daniel
>>
>>
>>> On 10/15/18 8:27 AM, Gary Holmlund wrote:
>>> Daniel,
>>>
>>> The "space" bar acts as a pause toggle for auto scroll. In the menus under "View/Scroll" you will see the 3 actions and their shortcuts. The shortcuts can be changed using "Settings/Config".
>>>
>>> As for Retina, I suspect the newer versions of Qt are the source of the improvement.
>>>
>>> Thanks for the feedback,
>>>
>>> Gary
>>>
>>>
>>>> On 10/15/18 7:04 AM, Daniel Owens wrote:
>>>> Gary,
>>>>
>>>> I renamed my sword folder, as you suggested, and installed some modules. That was the source of the problem. I have made a few of my own modules over the years, some of which may not work, and that may have been the source of the crash?
>>>>
>>>> I knew I must be forgetting something. I just now tested auto scrolling. It worked fine. The one thing I discovered from a user experience perspective is that I felt like I needed a stop button so that if I was scrolling at a higher speed I could quickly stop it. Maybe there already is a shortcut for that. I wonder if at some point it would be helpful to have buttons on the window for scroll down or up and stop. Or a right-click menu button? Just a thought.
>>>>
>>>> I am delighted to test on a Mac. Off-topic: Did you do something to improve BT's display on Retina? It seems sharper than it used to. It looks really good! Maybe that happened awhile ago, but it was a fun discovery this morning.
>>>>
>>>> After testing on the Mac in all the same ways that I tested in Windows, I discovered that it started up just fine, even with all of my modules that caused the crash on Windows. I am not sure how to explain that. But everything worked. I did get a crash while scrolling quickly through the Abbott-Smith lexicon, but I was not able to repeat the crash. Unhappily I did not capture the feedback from OSX before the program restarted. If it happens again, I will capture it before reopening.
>>>>
>>>> This is excellent. I will just keep using this version and let you know if I have any troubles.
>>>>
>>>> Daniel
>>>>
>>>>> On 10/14/18 5:12 PM, Gary Holmlund wrote:
>>>>> Daniel,
>>>>>
>>>>> Thanks for the report. I also have seen a crash during install, but did not capture the details. I will try this again. You did not mention how you avoided the crash on startup you previously had. Also, did you try the auto scroll?
>>>>>
>>>>> If you are able, could you also test a MacOS version. It will be the first time I have build BibleTime on a Mac, but it seems correct to me. If you can test it download it from here:
>>>>>
>>>>> http://sourcearchives.com/BibleTime-2.11.2_xx3.dmg
>>>>>
>>>>> Gary
>>>>>
>>>>>
>>>>>> On 10/14/18 12:42 PM, Daniel Owens wrote:
>>>>>> Gary,
>>>>>>
>>>>>> I tried out the new build in every way I could think, checking all types of modules (except glossaries), trying out parallel works, including different languages Bibles and commentaries, etc. I particularly was interested in trying ESV with Hebrew in parallel, scrolling from Malachi to Matthew, which Hebrew would not have. I was not able to cause any crashes, except occasionally when installing modules, after modules finished installing, BT would quit. But that was not in every case, and I would not think that was at all related to the continuous scrolling.
>>>>>>
>>>>>> Daniel
>>>>>>
>>>>>>> On 10/10/18 5:08 PM, Gary Holmlund wrote:
>>>>>>> Daniel,
>>>>>>>
>>>>>>> On the previous message I told you the wrong directory to find the "Sword" directory.
>>>>>>>
>>>>>>> On your command window type:
>>>>>>>
>>>>>>> echo %APPDATA%
>>>>>>>
>>>>>>> It will probably say:
>>>>>>>
>>>>>>> C:\Users\garyh\AppData\Roaming
>>>>>>>
>>>>>>> This is where the "Sword" dir is. Sorry for the confusion.
>>>>>>>
>>>>>>> Gary
>>>>>>>
>>>>>>>
>>>>>>>> On 10/10/2018 12:55 PM, Gary Holmlund wrote:
>>>>>>>> Daniel,
>>>>>>>>
>>>>>>>> So, I believe you saw this message in your splash screen.
>>>>>>>>
>>>>>>>> "Initializing the SWORD engine..."
>>>>>>>>
>>>>>>>> That was the last message? This puts the code in "initBackend" which deals with Sword and the works you have installed.
>>>>>>>>
>>>>>>>> The "Sword" directory in your home directory contains the works. Could you renamed "Sword" to something else like "Sword.save". After restarting BibleTime, if it starts up the "Sword" directory would be recreated. You would have to download some works to be able to go farther.
>>>>>>>>
>>>>>>>> If BibleTime does start after renaming the directory, perhaps you could zip up the "Sword.save" and send it to me so I could try it on my computer.
>>>>>>>>
>>>>>>>> Gary
>>>>>>>>
>>>>>>>>
>>>>>>>>> On 10/10/2018 11:36 AM, Daniel Owens wrote:
>>>>>>>>> Yes, so I checked to make sure I had installed the correct version by reinstalling it. Then I ran in debug mode, but the debug file, which was created today, was an empty text file. That's odd, right?
>>>>>>>>>
>>>>>>>>> Daniel
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On 10/10/18 1:16 PM, Gary Holmlund wrote:
>>>>>>>>>> Daniel,
>>>>>>>>>>
>>>>>>>>>> The newer vesion has "xx2" in the name instead of "xxx". Are you sure you installed the correct one?
>>>>>>>>>>
>>>>>>>>>> If yes, please start BibleTime from an command window in debug mode.
>>>>>>>>>>
>>>>>>>>>> cd \Program Files (x86)\BibleTime\bin
>>>>>>>>>>
>>>>>>>>>> .\BibleTime.exe --debug
>>>>>>>>>>
>>>>>>>>>> After it hangs look in your home directory for a file named "BibleTime Debug.txt". It may have some clues about this issue.
>>>>>>>>>>
>>>>>>>>>> Gary
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On 10/10/2018 11:03 AM, Daniel Owens wrote:
>>>>>>>>>>> Gary,
>>>>>>>>>>>
>>>>>>>>>>> It still hangs in the splash screen while initiating the sword engine. I tried completely removing the BibleTime folder, which was left after the uninstall. Still, it hangs.
>>>>>>>>>>>
>>>>>>>>>>> Daniel
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On 10/8/18 7:26 PM, Gary Holmlund wrote:
>>>>>>>>>>>> Daniel,
>>>>>>>>>>>>
>>>>>>>>>>>> I found that during startup BibleTime was looking for the javascript directory in its installation. We are no longer using javascript and the directory does not exist. Sorry for that problem.
>>>>>>>>>>>>
>>>>>>>>>>>> I have a corrected download for you. It also fixes a couple of minor issues I found.
>>>>>>>>>>>>
>>>>>>>>>>>> http://http://sourcearchives.com/BibleTime-2.11.2_xx2-win32.exe
>>>>>>>>>>>>
>>>>>>>>>>>> btGary
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 10/08/2018 11:28 AM, Daniel Owens wrote:
>>>>>>>>>>>> Yo
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> bt-devel mailing list
>>>>>>>>>>>> bt-devel at crosswire.org
>>>>>>>>>>>> http://www.crosswire.org/mailman/listinfo/bt-devel
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> bt-devel mailing list
>>>>>>>>>> bt-devel at crosswire.org
>>>>>>>>>> http://www.crosswire.org/mailman/listinfo/bt-devel
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> bt-devel mailing list
>>>>>>> bt-devel at crosswire.org
>>>>>>> http://www.crosswire.org/mailman/listinfo/bt-devel
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> bt-devel mailing list
>>>>>> bt-devel at crosswire.org
>>>>>> http://www.crosswire.org/mailman/listinfo/bt-devel
>>>>>
>>>>> _______________________________________________
>>>>> bt-devel mailing list
>>>>> bt-devel at crosswire.org
>>>>> http://www.crosswire.org/mailman/listinfo/bt-devel
>>>>
>>>>
>>>> _______________________________________________
>>>> bt-devel mailing list
>>>> bt-devel at crosswire.org
>>>> http://www.crosswire.org/mailman/listinfo/bt-devel
>>>
>>> _______________________________________________
>>> bt-devel mailing list
>>> bt-devel at crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/bt-devel
>
> _______________________________________________
> bt-devel mailing list
> bt-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/bt-devel
More information about the bt-devel
mailing list