On samedi 8 novembre 2008, Doriano Blengino wrote:
> Benoit Minisini ha scritto:
> > On samedi 8 novembre 2008, Doriano Blengino wrote:
> >> birchy ha scritto:
> >>> Bugzilla from [EMAIL PROTECTED] wrote:
> One of the rules of good programming is making the less possible
> things public
>
Benoit Minisini ha scritto:
> On samedi 8 novembre 2008, Doriano Blengino wrote:
>
>> birchy ha scritto:
>>
>>> Bugzilla from [EMAIL PROTECTED] wrote:
>>>
One of the rules of good programming is making the less possible things
public
>>> I totally agree with t
Doriano Blengino wrote:
> there should be a way to make public just the needed things
Perhaps an easy solution would be to add a public/private checkbox to the
Properties of each control?
--
View this message in context:
http://www.nabble.com/Values-between-forms..-tp20387230p20397519.html
Sen
in Form1 you could create :
PUBLIC SUB ChangeTextBox(Value as String)
Text1.Text = Value
END SUB
and in form 2:
PUBLIC SUB Button_Click()
Form1.ChangeTextBox(form2Textbox.text)
End Sub
On Fri, Nov 7, 2008 at 10:18 AM, Oscar Cascante Fonseca <
[EMAIL PROTECTED]> wrote:
> Hi, i am new in
On samedi 8 novembre 2008, Doriano Blengino wrote:
> birchy ha scritto:
> > Bugzilla from [EMAIL PROTECTED] wrote:
> >> One of the rules of good programming is making the less possible things
> >> public
> >
> > I totally agree with this, but if we have a project rich with progress
> > bars and oth
birchy ha scritto:
> Bugzilla from [EMAIL PROTECTED] wrote:
>
>> One of the rules of good programming is making the less possible things
>> public
>>
>
> I totally agree with this, but if we have a project rich with progress bars
> and other graphical displays, it is not uncommon to write a
On samedi 8 novembre 2008, birchy wrote:
> Bugzilla from [EMAIL PROTECTED] wrote:
> > One of the rules of good programming is making the less possible things
> > public
>
> I totally agree with this, but if we have a project rich with progress bars
> and other graphical displays, it is not uncommon
Bugzilla from [EMAIL PROTECTED] wrote:
> One of the rules of good programming is making the less possible things
> public
I totally agree with this, but if we have a project rich with progress bars
and other graphical displays, it is not uncommon to write a class or module
to handle them. Perhap
On samedi 8 novembre 2008, birchy wrote:
> Doriano Blengino wrote:
> > I suppose that that option does what you
> > want... or I am missing something?
>
> Yes, it does exactly what i want. The reason i asked if it could be set as
> default is because MOST projects need to reference form controls fr
Doriano Blengino wrote:
> I suppose that that option does what you
> want... or I am missing something?
Yes, it does exactly what i want. The reason i asked if it could be set as
default is because MOST projects need to reference form controls from class
modules. Making them public at all times
birchy ha scritto:
> Doriano Blengino wrote:
>
>> You have to set project option: "Controls of the forms are public".
>>
>
> I recently discovered this while trying to access Form controls from a class
> module. Is it possible to make all controls Public by default (like in VB)?
>
I neve
Doriano Blengino wrote:
> You have to set project option: "Controls of the forms are public".
I recently discovered this while trying to access Form controls from a class
module. Is it possible to make all controls Public by default (like in VB)?
--
View this message in context:
http://www.nab
Oscar Cascante Fonseca ha scritto:
> Hi, i am new in gambas..
>
> I don't find in the archives any post about how to pass values between
> forms.
>
You have to set project option: "Controls of the forms are public".
Then, you can access controls of a form from another form, i.e., in
Form2.Butt
Hi, i am new in gambas..
I don't find in the archives any post about how to pass values between
forms.
Ej:
Form1 with a textbox control
Form 2 with a button control
When you click in Form2.button, the Form1.textbox.text change.
Could somebody help me?
Thanks.
14 matches
Mail list logo
