On Sun, 5 Sep 2010 07:01:04 +0200
Felipe Monteiro de Carvalho wrote:
> On Sun, Sep 5, 2010 at 6:39 AM, Peter E Williams
> wrote:
> > Questions:
> > 1) Does the Memo1, OK_Button and Cancel TButton need to be in a
> > TGroupBox???
> > 2) Also, should the TImage be in a TGroupBox???
>
> I think th
On Sun, 05 Sep 2010 19:18:49 +1000
Peter E Williams wrote:
> Hi Felipe and All,
>
> On Sun, 2010-09-05 at 07:01 +0200, Felipe Monteiro de Carvalho wrote:
> > On Sun, Sep 5, 2010 at 6:39 AM, Peter E Williams
> > wrote:
> > > Questions:
> > > 1) Does the Memo1, OK_Button and Cancel TButton need t
On Mon, 6 Sep 2010 10:03:22 +0200
Graeme Geldenhuys wrote:
> On 6 September 2010 05:44, Hans-Peter Diettrich wrote:
> >
> > This is how most *other* GUI designers work, lacking any useful *visual*
> > form designer.
>
> fpGUI being the exception. :-) It has a useful Visual Forms Designer,
> and
On 6 September 2010 05:44, Hans-Peter Diettrich wrote:
>
> This is how most *other* GUI designers work, lacking any useful *visual*
> form designer.
fpGUI being the exception. :-) It has a useful Visual Forms Designer,
and outputs Object Pascal code in the code unit itself, not in some
external l
On 6 September 2010 02:31, Dimitri Smits wrote:
> you've got to love the IDE experts like GExperts in Delphi. There you define
> your form as you want it to be through the editor and then "export to code".
> In other words, a kind of "dfm"-writer that writes creation-initialization
> code in obj
Dimitri Smits schrieb:
you've got to love the IDE experts like GExperts in Delphi. There you
define your form as you want it to be through the editor and then
"export to code". In other words, a kind of "dfm"-writer that writes
creation-initialization code in objpas/fpc-code to the clipboard.
Hi,
you've got to love the IDE experts like GExperts in Delphi. There you define
your form as you want it to be through the editor and then "export to code". In
other words, a kind of "dfm"-writer that writes creation-initialization code in
objpas/fpc-code to the clipboard.
maybe an idea for
Hi Alberto and All,
On Sun, 2010-09-05 at 22:24 +0300, Alberto Narduzzi wrote:
> > I would guess something like:
> > { this code is all untested and typed straight into my email client }
> >
> > procedure create_formA(
> > Image_filename : string; StringList1 : TStringList );
> > var
> > For
> FormA := TForm.Create; // Are there any parameters here
use:
FormA := TForm.Create(Application); if you want the form to be freed
when the program ends automatically
FormA := TForm.Create(nil); if you want to control where the form will be freed
> Splitter1.Align := alRight;
> // d
I would guess something like:
{ this code is all untested and typed straight into my email client }
procedure create_formA(
Image_filename : string; StringList1 : TStringList );
var
FormA : TForm;
(...)
wouldn't it be better to define the form within the IDE, with all of its
components;
Hi Felipe and All,
On Sun, 2010-09-05 at 07:01 +0200, Felipe Monteiro de Carvalho wrote:
> On Sun, Sep 5, 2010 at 6:39 AM, Peter E Williams
> wrote:
> > Questions:
> > 1) Does the Memo1, OK_Button and Cancel TButton need to be in a
> > TGroupBox???
> > 2) Also, should the TImage be in a TGroupBox
On Sun, Sep 5, 2010 at 6:39 AM, Peter E Williams
wrote:
> Questions:
> 1) Does the Memo1, OK_Button and Cancel TButton need to be in a
> TGroupBox???
> 2) Also, should the TImage be in a TGroupBox???
I think that to use the splitter you need to group the elements using
a panel. I vaguely remember
Hi All,
This is a rough mock-up of a TForm that I need to create at runtime
only.
+--+
| Form caption |
+--+
|+--+S+---+|
|| |P|
13 matches
Mail list logo