Re: fixed textheight affects scrolling?
Girls! Time to take this spat off list, please. I don’t want to see this. Remember the admonition about politics religion and cheese? On Sat, Jul 11, 2020 at 03:03 Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > To all, > > sorry for this, I should have kept if off-list and I apologize, but this > is my last mail in this respect! > > > @Curry, > > > Am 11.07.2020 um 00:04 schrieb Curry Kenworthy via use-livecode < > use-livecode@lists.runrev.com>: > > > > Klaus: > > >... > > > any news about "FieldTrip"? This is not funny anymore. > > > I turned 64 last month and I would really like to get > > > something for my money before I die! > > Klaus, let me say that your "National Socialist" approach > > No idea what that may be, but it is surely not nice. > I do my best, but in the end I am not a native english speaker. > > > to harassing me, every single chance you get, is also not funny anymore! > > I dared to ask about 3 (THREE) times in the last seven years, not at every > single chance I got. > The first time I did, you even made fun of me, also not very kind. > > > Nor is giving people the FALSE and fake impression that you did not get > a product for your money. > > I got a one BETA and no update since 2013. > > > I resent that slur, along with your continued harassment and > mean-spirited, inaccurate disinformation campaign. It is as fundamentally > flawed as your field test code. Maybe a pattern? > > Oh my, that is very close to the wind and a cheap tit-for-tat response! > > > FT was delivered. > > > You got the LC 6 product you paid for. > > One BETA was delivered! > I bought it at a time where I did not have much money, but wanted to > support everything related to LC > so I am not very happy that no final version has been delivered since. > > I personally don't find it OK to sell software, take the customers money > and deliver one beta version of that software in years. > But you do. > > > LC pulled out the rug shortly after; LC 7 stopped working with some > existing code, and not the other way around. Technically 7 was supposed to > work with the existing code, and the team was working through BC issues, > but ah well. My flagship products were more fortunate (with a lot of help > from myself in testing and reporting issues) but LC 7 was released before > that could happen for FT. > > Interesting, so it is LCs fault in the end. > If I only had known this before! > > > Since then, WordLib and WordReport have remained higher priorities. FT > will be revived and updated; looking forward to it very much. But that will > be AFTER the other flagship addons are updated. Not before. Harassment > won't change that. Nor will falsehoods or bad behavior. > > (Hint: currently WordReport is first in line!) > > > > I cleared up your little scrolling field mystery for you, and in return, > this is how you act?! Now, let's see how logical you can be, Klaus. Take a > good look at the length of this message. I'm keeping it as short as > possible, but obviously it still takes some time to carefully answer your > careless slur. > > > > That does NOT speed up anything, including FT. But it does waste > valuable time and slow things down. It's not furthering the outcome you > seek. It also destroys goodwill and friendship, and it spreads falsehood. > On top of that I'm handicapped and I don't have free time to waste. All bad > results of these little slurs about FT and myself. > > Please, let's dial it back a notch! > You don't want to make me responsible for all of your personal problems > and even your handicap, do you? > > > I would appreciate polite inquiries, or reminders, but this is way out > of line. Every time I post here, you do this. > > Not true, see above... > > > You keep calling for my attention, and you got it. > > So, here's what I'll do. If you keep up this "National Socialist" style > of harassment, I'll just pay a little more attention to your posts and > correct more of the inaccurate statements that you make about LC code and > technologies. I will also refer back to this post to save time, so that my > corrections are as efficient as your falsehoods. > > I've had to make "Klaus corrections" about other LC matters (regular LC > how-to and facts/tips, not about FT) on a regular basis over the years, > usually very quietly off-list! > > And another laughable, untenable and very cheap tit-for-tat response! > > > But I'll be happy to make more public corrections, more often, if > needed. Or if you lay off the harassment, then as a natural result (math, > time) everything will happen a little faster, including FT. The choice is > yours. > > > Best wishes, > > > > Curry Kenworthy > > I find your response rather "Mimimi" and highly exaggerated in many parts > and I really start to feel sorry for you. > But don't worry, I will not bother you again. > > > Klaus > > -- > Klaus Major > https://www.major-k.de > kl...@major-k.de > > > ___ > u
Re: fixed textheight affects scrolling?
To all, sorry for this, I should have kept if off-list and I apologize, but this is my last mail in this respect! @Curry, > Am 11.07.2020 um 00:04 schrieb Curry Kenworthy via use-livecode > : > > Klaus: > >... > > any news about "FieldTrip"? This is not funny anymore. > > I turned 64 last month and I would really like to get > > something for my money before I die! > Klaus, let me say that your "National Socialist" approach No idea what that may be, but it is surely not nice. I do my best, but in the end I am not a native english speaker. > to harassing me, every single chance you get, is also not funny anymore! I dared to ask about 3 (THREE) times in the last seven years, not at every single chance I got. The first time I did, you even made fun of me, also not very kind. > Nor is giving people the FALSE and fake impression that you did not get a > product for your money. I got a one BETA and no update since 2013. > I resent that slur, along with your continued harassment and mean-spirited, > inaccurate disinformation campaign. It is as fundamentally flawed as your > field test code. Maybe a pattern? Oh my, that is very close to the wind and a cheap tit-for-tat response! > FT was delivered. > You got the LC 6 product you paid for. One BETA was delivered! I bought it at a time where I did not have much money, but wanted to support everything related to LC so I am not very happy that no final version has been delivered since. I personally don't find it OK to sell software, take the customers money and deliver one beta version of that software in years. But you do. > LC pulled out the rug shortly after; LC 7 stopped working with some existing > code, and not the other way around. Technically 7 was supposed to work with > the existing code, and the team was working through BC issues, but ah well. > My flagship products were more fortunate (with a lot of help from myself in > testing and reporting issues) but LC 7 was released before that could happen > for FT. Interesting, so it is LCs fault in the end. If I only had known this before! > Since then, WordLib and WordReport have remained higher priorities. FT will > be revived and updated; looking forward to it very much. But that will be > AFTER the other flagship addons are updated. Not before. Harassment won't > change that. Nor will falsehoods or bad behavior. > (Hint: currently WordReport is first in line!) > > I cleared up your little scrolling field mystery for you, and in return, this > is how you act?! Now, let's see how logical you can be, Klaus. Take a good > look at the length of this message. I'm keeping it as short as possible, but > obviously it still takes some time to carefully answer your careless slur. > > That does NOT speed up anything, including FT. But it does waste valuable > time and slow things down. It's not furthering the outcome you seek. It also > destroys goodwill and friendship, and it spreads falsehood. On top of that > I'm handicapped and I don't have free time to waste. All bad results of these > little slurs about FT and myself. Please, let's dial it back a notch! You don't want to make me responsible for all of your personal problems and even your handicap, do you? > I would appreciate polite inquiries, or reminders, but this is way out of > line. Every time I post here, you do this. Not true, see above... > You keep calling for my attention, and you got it. > So, here's what I'll do. If you keep up this "National Socialist" style of > harassment, I'll just pay a little more attention to your posts and correct > more of the inaccurate statements that you make about LC code and > technologies. I will also refer back to this post to save time, so that my > corrections are as efficient as your falsehoods. > I've had to make "Klaus corrections" about other LC matters (regular LC > how-to and facts/tips, not about FT) on a regular basis over the years, > usually very quietly off-list! And another laughable, untenable and very cheap tit-for-tat response! > But I'll be happy to make more public corrections, more often, if needed. Or > if you lay off the harassment, then as a natural result (math, time) > everything will happen a little faster, including FT. The choice is yours. > Best wishes, > > Curry Kenworthy I find your response rather "Mimimi" and highly exaggerated in many parts and I really start to feel sorry for you. But don't worry, I will not bother you again. Klaus -- Klaus Major https://www.major-k.de kl...@major-k.de ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: fixed textheight affects scrolling?
Klaus: > oh, I really had no idea that setting the hilitedline will also > scroll that line into view!? 8-) > That makes my custom scrolling stuff completely obsolete. Yep, LC does auto-scroll when you set hilitedline! Very handy. I would say "redundant" in this case, rather than obsolete. There is still value in being able to scroll a field with similar calculations. For example, someone might want to have the hilited line in the vertical center of the field, or always at the top when possible. Just a matter of getting the calcs right. Not very difficult. But it does require a valid test, or valid setup, without conflating the two actions. > any news about "FieldTrip"? This is not funny anymore. > I turned 64 last month and I would really like to get > something for my money before I die! Klaus, let me say that your "National Socialist" approach to harassing me, every single chance you get, is also not funny anymore! Nor is giving people the FALSE and fake impression that you did not get a product for your money. I resent that slur, along with your continued harassment and mean-spirited, inaccurate disinformation campaign. It is as fundamentally flawed as your field test code. Maybe a pattern? FT was delivered. You got the LC 6 product you paid for. LC pulled out the rug shortly after; LC 7 stopped working with some existing code, and not the other way around. Technically 7 was supposed to work with the existing code, and the team was working through BC issues, but ah well. My flagship products were more fortunate (with a lot of help from myself in testing and reporting issues) but LC 7 was released before that could happen for FT. Since then, WordLib and WordReport have remained higher priorities. FT will be revived and updated; looking forward to it very much. But that will be AFTER the other flagship addons are updated. Not before. Harassment won't change that. Nor will falsehoods or bad behavior. (Hint: currently WordReport is first in line!) I cleared up your little scrolling field mystery for you, and in return, this is how you act?! Now, let's see how logical you can be, Klaus. Take a good look at the length of this message. I'm keeping it as short as possible, but obviously it still takes some time to carefully answer your careless slur. That does NOT speed up anything, including FT. But it does waste valuable time and slow things down. It's not furthering the outcome you seek. It also destroys goodwill and friendship, and it spreads falsehood. On top of that I'm handicapped and I don't have free time to waste. All bad results of these little slurs about FT and myself. I would appreciate polite inquiries, or reminders, but this is way out of line. Every time I post here, you do this. You keep calling for my attention, and you got it. So, here's what I'll do. If you keep up this "National Socialist" style of harassment, I'll just pay a little more attention to your posts and correct more of the inaccurate statements that you make about LC code and technologies. I will also refer back to this post to save time, so that my corrections are as efficient as your falsehoods. I've had to make "Klaus corrections" about other LC matters (regular LC how-to and facts/tips, not about FT) on a regular basis over the years, usually very quietly off-list! But I'll be happy to make more public corrections, more often, if needed. Or if you lay off the harassment, then as a natural result (math, time) everything will happen a little faster, including FT. The choice is yours. Thanks Klaus! Happy 64th birthday. Best wishes, Curry Kenworthy Custom Software Development "Better Methods, Better Results" LiveCode Training and Consulting http://livecodeconsulting.com/ ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: fixed textheight affects scrolling?
Hi Curry, > Am 10.07.2020 um 21:30 schrieb Curry Kenworthy via use-livecode > : > > Klaus: > >> set the scroll of fld "fonts" to tLine*tTH + the height of fld "fonts" >> set the hilitedlines of fld "fonts" to tLine > > The test is invalid; the 2nd quoted line overrides the 1st. oh, I really had no idea that setting the hilitedline will also scroll that line into view!? 8-) That makes my custom scrolling stuff completely obsolete. > Therefore you don't see the results of your scrolling code. > To debug your scroll calc, first comment out the set hilitedlines. > Easy testing: use an ask, input either line # or font name. > (To test hilite, either forget about scroll calc, or do it AFTER.) > Watch out about adding versus subtracting field height. > Why add? See above, no scolling neccessary anymore! > No more mysteries. Or at least fewer. :) > > Best wishes, > > Curry Kenworthy Best Klaus P.S. I know you may still find me impertinent by asking this after more than seven years, but any news about "FieldTrip"? This is not funny anymore. I turned 64 last month and I would really like to get something for my money before I die! -- Klaus Major https://www.major-k.de kl...@major-k.de ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: fixed textheight affects scrolling?
Klaus: set the scroll of fld "fonts" to tLine*tTH + the height of fld "fonts" set the hilitedlines of fld "fonts" to tLine The test is invalid; the 2nd quoted line overrides the 1st. Therefore you don't see the results of your scrolling code. To debug your scroll calc, first comment out the set hilitedlines. Easy testing: use an ask, input either line # or font name. (To test hilite, either forget about scroll calc, or do it AFTER.) Watch out about adding versus subtracting field height. Why add? No more mysteries. Or at least fewer. :) Best wishes, Curry Kenworthy Custom Software Development "Better Methods, Better Results" LiveCode Training and Consulting http://livecodeconsulting.com/ ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: fixed textheight affects scrolling?
Hi all,
> Am 09.07.2020 um 11:40 schrieb Klaus major-k via use-livecode
> :
>
> Hi Mark,
> ...
Hi friends,
strange phenomenon, maybe I am missing something!?
LC 9.6 on macOS 10.14.6
I have two fields with all available fonts and each line is formatted
directly
in the appropriate font it reads.
I set the FixedLineHeight for ONE field to 28, doesn't matter actually.
Now I want to select a specific line in the fields with this script:
---
on mouseUp pMouseButton
set the wholematches to TRUE
put lineoffset("Lucida Grande",fld "fonts") into tLine
## Which is 366 in my fields!
put the effective textheight of fld "fonts" into tTH
set the scroll of fld "fonts" to tLine*tTH + the height of fld "fonts"
set the hilitedlines of fld "fonts" to tLine
end mouseUp
---
Works fine for the field WITHOUT fixedlineheigt and selects the line ->
Lucida Grande
However the same script used with the field WITH fixedlineheight, it
selects -> Lucida Grande Bold
which is the line AFTER "Lucida Grande" and actually line 367!?
What am I overlooking?
Thanks for any hints!
>>
>> I suspect the fact it works in the non-fixedline height case is serendipity
>> in this specific case - if line height isn't fixed then each line will have
>> a different height based on the fonts (although most will be the same if the
>> fontSize is the same)...
>> LineOffset is 1-based - so the first line has scroll 0ish (ish because of
>> field margins etc.) - that's probably the issue with your existing code.
>> There's an easier way I think though which should be independent of any
>> field styling (size, font, wrapping)...
>> You can get the formattedTop of a line - which gives you the card-relative y
>> co-ordinate of the top of the including the fields top and scroll. So this
>> should do the trick:
>> set the scroll of field "fonts" to the scroll of field "fonts" + \
>> the formattedTop of line tLine of field
>> "fonts" - \
>> the top of field "fonts"
>> The adjustment is necessary because the scroll value is relative to the
>> top-left of the 'content' of the field.
>>
>> Hope this helps!
>>
>> Mark.
>
> thank you very much!
> But even with this new script LC scrolls to and selects -> Lucida Grande only
> if "fixedlineheight" is UNchecked!?
further observation:
I removed the formatting of the "fonts" field, set all lines to "Arial" and now
everything (my original script and Marks script)
works as advertized even WITH "fixedlineheight" checked!?
So I think these many different fonts in a field are somehow "puzzling "LC (and
me :-).
Or maybe not, I have no idea...
Best
Klaus
--
Klaus Major
https://www.major-k.de
kl...@major-k.de
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: fixed textheight affects scrolling?
Hi Mark,
> Am 09.07.2020 um 11:22 schrieb Mark Waddingham via use-livecode
> :
>
> On 2020-07-09 09:54, Klaus major-k via use-livecode wrote:
>> Hi all,
>>> Am 08.07.2020 um 17:51 schrieb Klaus major-k via use-livecode
>>> :
>>> Hi friends,
>>> strange phenomenon, maybe I am missing something!?
>>> LC 9.6 on macOS 10.14.6
>>> I have two fields with all available fonts and each line is formatted
>>> directly
>>> in the appropriate font it reads.
>>> I set the FixedLineHeight for ONE field to 28, doesn't matter actually.
>>> Now I want to select a specific line in the fields with this script:
>>> ---
>>> on mouseUp pMouseButton
>>> set the wholematches to TRUE
>>> put lineoffset("Lucida Grande",fld "fonts") into tLine
>>> ## Which is 366 in my fields!
>>> put the effective textheight of fld "fonts" into tTH
>>> set the scroll of fld "fonts" to tLine*tTH + the height of fld "fonts"
>>> set the hilitedlines of fld "fonts" to tLine
>>> end mouseUp
>>> ---
>>> Works fine for the field WITHOUT fixedlineheigt and selects the line ->
>>> Lucida Grande
>>> However the same script used with the field WITH fixedlineheight, it
>>> selects -> Lucida Grande Bold
>>> which is the line AFTER "Lucida Grande" and actually line 367!?
>>> What am I overlooking?
>>> Thanks for any hints!
>
> I suspect the fact it works in the non-fixedline height case is serendipity
> in this specific case - if line height isn't fixed then each line will have a
> different height based on the fonts (although most will be the same if the
> fontSize is the same)...
> LineOffset is 1-based - so the first line has scroll 0ish (ish because of
> field margins etc.) - that's probably the issue with your existing code.
> There's an easier way I think though which should be independent of any field
> styling (size, font, wrapping)...
> You can get the formattedTop of a line - which gives you the card-relative y
> co-ordinate of the top of the including the fields top and scroll. So this
> should do the trick:
> set the scroll of field "fonts" to the scroll of field "fonts" + \
> the formattedTop of line tLine of field
> "fonts" - \
> the top of field "fonts"
> The adjustment is necessary because the scroll value is relative to the
> top-left of the 'content' of the field.
>
> Hope this helps!
>
> Mark.
thank you very much!
But even with this new script LC scrolls to and selects -> Lucida Grande only
if "fixedlineheight" is UNchecked!?
Best
Klaus
--
Klaus Major
https://www.major-k.de
kl...@major-k.de
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: fixed textheight affects scrolling?
On 2020-07-09 09:54, Klaus major-k via use-livecode wrote:
Hi all,
Am 08.07.2020 um 17:51 schrieb Klaus major-k via use-livecode
:
Hi friends,
strange phenomenon, maybe I am missing something!?
LC 9.6 on macOS 10.14.6
I have two fields with all available fonts and each line is formatted
directly
in the appropriate font it reads.
I set the FixedLineHeight for ONE field to 28, doesn't matter
actually.
Now I want to select a specific line in the fields with this script:
---
on mouseUp pMouseButton
set the wholematches to TRUE
put lineoffset("Lucida Grande",fld "fonts") into tLine
## Which is 366 in my fields!
put the effective textheight of fld "fonts" into tTH
set the scroll of fld "fonts" to tLine*tTH + the height of fld
"fonts"
set the hilitedlines of fld "fonts" to tLine
end mouseUp
---
Works fine for the field WITHOUT fixedlineheigt and selects the line
-> Lucida Grande
However the same script used with the field WITH fixedlineheight, it
selects -> Lucida Grande Bold
which is the line AFTER "Lucida Grande" and actually line 367!?
What am I overlooking?
Thanks for any hints!
I suspect the fact it works in the non-fixedline height case is
serendipity in this specific case - if line height isn't fixed then each
line will have a different height based on the fonts (although most will
be the same if the fontSize is the same)...
LineOffset is 1-based - so the first line has scroll 0ish (ish because
of field margins etc.) - that's probably the issue with your existing
code.
There's an easier way I think though which should be independent of any
field styling (size, font, wrapping)...
You can get the formattedTop of a line - which gives you the
card-relative y co-ordinate of the top of the including the fields top
and scroll. So this should do the trick:
set the scroll of field "fonts" to the scroll of field "fonts" + \
the formattedTop of line tLine of
field "fonts" - \
the top of field "fonts"
The adjustment is necessary because the scroll value is relative to the
top-left of the 'content' of the field.
Hope this helps!
Mark.
--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: fixed textheight affects scrolling?
Hi all,
> Am 08.07.2020 um 17:51 schrieb Klaus major-k via use-livecode
> :
>
> Hi friends,
>
> strange phenomenon, maybe I am missing something!?
> LC 9.6 on macOS 10.14.6
>
> I have two fields with all available fonts and each line is formatted
> directly
> in the appropriate font it reads.
>
> I set the FixedLineHeight for ONE field to 28, doesn't matter actually.
>
> Now I want to select a specific line in the fields with this script:
> ---
> on mouseUp pMouseButton
> set the wholematches to TRUE
> put lineoffset("Lucida Grande",fld "fonts") into tLine
> ## Which is 366 in my fields!
>
> put the effective textheight of fld "fonts" into tTH
> set the scroll of fld "fonts" to tLine*tTH + the height of fld "fonts"
> set the hilitedlines of fld "fonts" to tLine
> end mouseUp
> ---
>
> Works fine for the field WITHOUT fixedlineheigt and selects the line ->
> Lucida Grande
> However the same script used with the field WITH fixedlineheight, it selects
> -> Lucida Grande Bold
> which is the line AFTER "Lucida Grande" and actually line 367!?
>
> What am I overlooking?
> Thanks for any hints!
Ideas? Anyone? No?
Best
Klaus
--
Klaus Major
https://www.major-k.de
kl...@major-k.de
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
