[Lazarus] Joint scrolling of parallel memos ?
Hi, Let a form be with two same-size same-options no word-wrap Tmemo fields. One text is loaded in each memo, say two linguistic versions. My intention is to make a joint scrolling of the two memos (accepting approximations by the end of the texts if they do not have the same number of lines) So, - is there a simple way to impose that scrolling in one memo will apply also in the other one ? - if not, can we detect the extent of the displayed text in one memo (resulting from user's input) and apply it in the other memo ? - if not, can we at least find out what is the first line displayed, helping manual re-sync ? Thank you for suggestions, Etienne (Lyon, France, in real life). -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] how to set two memos for parallel text editing ?
Dear list, I want to edit two textfiles in a parallel way, so that visible portion of text one in memo1 has always same lines extent as the visible portion of text two in memo2, say lines n1 to n2. Of course WordWrap must be false, so that one_text_line=one_visible_line Then, how to manage that scrolling or arrowing up in one memo will also scroll up the other one ? Intercept event yes, but how to issue/code a scrolling order for memo that does not have focus ? Thanks for hints, Etienne. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] newbie
Dear all, I do not see why win32 lazarus should be the default on a win64 platform. The most suitable build to the platform were one works must be the default. Taking the best out of each particular platform is an implicit in the promise : Write once ... compile everywhere The allocatable memory is an improovement in win64 over win 32 (and linux64 over linux32) Regards, Etienne. Message: 8 Date: Mon, 27 Jan 2014 11:17:03 +0100 From: Kostas Michalopoulos badsectorac...@gmail.com Subject: Re: [Lazarus] newbie ... IMO since most people wont care about 64bit executables, it is better to only give that [64bit] download as an alternative option in 64bit Windows systems, not as the default (and only) option. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Help with algorithm
Greetings from Lyon, France,
In this kind of transformation, a *reverse* procedure to fill in the
result from the source is typically needed with signature like
type TReverseProj = object
// parameters to memorize
procedure set( { some parameters} );
procedure reverse(target_line, target_column :integer ; var
source_line, source_column :integer);
end;
procedure TReverseProj.set( { some parameters} );
begin
// setting the parameters for the reverse transformation
end;
procedure TReverseProj.reverse(target_line, target_column :integer ; var
source_line, source_column :integer);
begin
// applying the reverse transformation
end;
It is likely that the source position for same_line_next
column_in_target can be written more simply that the full reverse (to
be checked in equations, write on a paper reverse for (i,j) and (i,j+1)
and see what is the difference).
To take benefit of this the last returned position must be memorized in
the object and a routine added with signature like
procedure TReverseProj.shift_tarjet_cell(var
source_line_for_shifted_cell, source_column_for_shifted_cell :integer);
begin
// shifting source according to the shift in cell
end;
So the full reverse will be called only at the begin of each line
For generality calculation and storage must be handled in floating point
(single, double...) ; just the result is rounded.
Regards,
Etienne.
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] circular reference etc.
in a famous French langage dictionnary there was once upon a time a perfect
circular reference
étourneau (see) sansonnet
sansonnet (see) étourneau
such a circular reference is a deadlock in semantic, with one meaning depending
from the other and recursively from itself
it causes compilation failure
an endless loop is for sure different, where at least the semantic is clear
repeat { nothing } until false;
it causes execution hang
regards,
Etienne.
P.S. both étourneau and sansonnet are indeed the same thing (a bird) , as one
can check : http://translate.google.com/?#en|fr|starling
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
