4 replies to this topic

[Michael Clark]

when reading a large set of verses that have been tiped, there doesn't seem to be a way to scroll to the bottom, so you loose the rest of the verses unless you go directly back to the bible section.  Can this be addressed in your next update?

[APsit190]

Hi Michael,

Windows tooltips were not really designed for displaying large amount of text like one uses in e-Sword. The fact that one can take advantage of the Tooltip method within Windows do this is merely a freak accident that really is like added bonus. Tooltips, from the Developer's (Programmer's) perspective are primarily there to give helpful tips on what a component, i.e., a particular button, is there for, and perhaps brief information of what to do. It's for this reason why the Tooltip component within Windows does not have a Scrollbar component and method added to it.

 

Just some technical information.

 

When Programmers program for tooltips to be used in the software (program/app) they are developing, they are using what is called System Resources, and tooltips are components that come from the Operating System. So, when coding (programming) for tooltips to pop up, they have to be declared as a variable for the program to be able to pop them up. But its important to remember, it has to use the Operating System's resources; so when declared, and the code is written for it, then it will pop up when the mouse goes over a link, button, tab, or menu component/item.

 

So. with that information, I'm sorry to say that Rick cannot include a Scrollbar in the Windows Tooltip because it is not a part of the Operating System's resource.

 

Blessings,

[BH.]

Actually APsit190 - it is not hard to create your own popup tooltip window  with scrollbars on the Windows platform.  A more relevant issue is the size of the text to be displayed.  It is probably not wise to select a whole chapter.  Think of Psalms 119.  

[APsit190]

Actually APsit190 - it is not hard to create your own popup tooltip window  with scrollbars on the Windows platform.  A more relevant issue is the size of the text to be displayed.  It is probably not wise to select a whole chapter.  Think of Psalms 119.  

 

Hi Brent,

That is true. What is also true is that one is then not using the System's resources to load up the text, but has created a form for which the text can be loaded into it by a MouseHover event. (See Visual Studio documentation for C# Events and Methods).

 

Usually when using the System resources for tooltips, the code used for declaring a new tooltip is (C#)

System.Diagnostics.Windows.Forms.ToolTip  tltToolTip1= new ToolTip(); (or something similar to whatever programming language one is using.) However, the "System.Diagnostics.Windows.Forms" part I don't use. I just use, e.g.,  ToolTip tltBibles = new ToolTip(); Then there after that I write the code for that particular variable.

 

However, with all that said, I think that having a separate form as a popup in which the text is loaded may work better than a tooltip, and then add in a MouseLeave event to close the form. For the form to remain open the mouse pointer has to remain over the form. Moreover, even when it comes to very long chapters, using your Psa 119 as an example, would not be a real problem because the text is loaded into a form which has a TextBox or a RichTextBox which is capable to handle large amount of text. You can see this concept in MySword.

 

Blessings,

Edited by APsit190, 06 April 2015 - 08:34 PM.

[BH.]

I'll still stick with my main premise, and that is scripture popups should be of reasonable size...