882 replies to this topic

[BH.]

and continuing that theme:

how about T3/NT turning those symbols WHITE - instead of deleting them - the first time through, so they're still there if the tooltip tool is run a second time....

I have been thinking of removing the reference blocking character only when a module is made, not when a file is tooltipped. Thus, the reference blocking characters are not removed at all from the original file. This just means I need to insert the code to remove the reference blocking in all the module generating functions instead of one place, but it is probably worth it.

Edited by BH., 18 January 2012 - 03:43 PM.

[Josh Bond]

A HA! Proves it! I'm not a programmer. I do not use those curly braces languages.

If current text == /* stop tooltipping...resume when text = */

Throw in some egyptian hieroglyphs that APL likes, and that code's ready to compile!!

[BH.]

If current text == /* stop tooltipping...resume when text = */

Throw in some egyptian hieroglyphs that APL likes, and that code's ready to compile!!

Compile??? What's that? :-)
APL is an interpreted language. Ah - it does generate some p-code the first time a piece of code is run. I edit T3/4 while they are running!

[BH.]

I have been thinking of removing the reference blocking character only when a module is made, not when a file is tooltipped. Thus, the reference blocking characters are not removed at all from the original file. This just means I need to insert the code to remove the reference blocking in all the module generating functions instead of one place, but it is probably worth it.

So - looking at the issue, if one say is working on a Topic module, once you have tried to generate a TOPX file, the reference blocking text goes away, and at that point, if you make edits, and save it, they are lost. I'm not sure what the most ideal way to handle this is...

[journey]

So - looking at the issue, if one say is working on a Topic module, once you have tried to generate a TOPX file, the reference blocking text goes away, and at that point, if you make edits, and save it, they are lost. I'm not sure what the most ideal way to handle this is...

I'm not a programmer, so I have no idea how difficult this idea might be. Could a backup - maybe "bku" of the RTF file be made at the same time that the topic file is being created. You would then have the reference blocking saved and could go back to it in making changes.

[patchworkid]

Hi BH,

Can you please help me make return on all ÷ text

here is a sample of what i am talking about :  help with return s.rtf   4.82K   4 downloads

I need to do a double return on all ÷ this is in one lump (I need them in their own single line.

thanks
Patchworkid

[BH.]

I'm not a programmer, so I have no idea how difficult this idea might be. Could a backup - maybe "bku" of the RTF file be made at the same time that the topic file is being created. You would then have the reference blocking saved and could go back to it in making changes.

There are ways. The thing is you do not want to step on the perogative of the end user, or generate a huge amount of unnecessary data. You can yourself just SAVE the file before generating a module. If you don't loke the results, just reload the saved file. If I were to automatically save a file right before generating a module, that iis not necessarily what an end user would have expected. Perhaps the solution is that I save the data, generate the module and then restore the data back. That is probably what I should do. The trick is then I need to be able to detect if an error occurred because of bad formatting and to gracefully recover. (I'm just thinking out loud).

[BH.]

Hi BH,

Can you please help me make return on all ÷ text

here is a sample of what i am talking about :  help with return s.rtf   4.82K   4 downloads

I need to do a double return on all ÷ this is in one lump (I need them in their own single line.

thanks
Patchworkid

I have a rough draft of a "multi-line" find and replace. Maybe I'll post it a little later and let you try it . It should work for this OK.

[BH.]

========================================
Version 0.80- 1/19/2012
========================================
-- Fixed - Removed duplicate shortcut on Scripture+Mark References
-- Expiremental - Turn off Match Case in Find and Replace when first empty - (note to self - this is a kludge.)
-- New - Rough draft of a Multi-line Find and Replace, see Edit menu, shortcut Ctrld+Shift+R
-- New - Copy verse list to Clipboard - Copies ALL verses. (probably needs tweaking to all good, only bad...)
-- New - Copy and Paste work on Verse List pane.
-- Change - Removed Text Control built in Font Name box, and built new one on Format Bar. It has better response to keyboard input.

[ebulerdo]

-- New - Copy and Paste work on Verse List pane.

Thanks!