Am Donnerstag, den 18.03.2010, 21:16 +0100 schrieb Fabien Bodard: > simplis use a public function > in the parent form > > Public sub MyFunction > end > > Then in your component > > Dim o as object > > o = me.parent > > o.MyFunction > > > 2010/3/18 Charlie Reinl <karl.re...@fen-net.de>: > > Am Donnerstag, den 18.03.2010, 20:12 +0100 schrieb Doriano Blengino: > >> Charlie Reinl ha scritto: > >> > >> >Salut, > >> > > >> >is it possible to run from a (gambas2) component, a Sub/Function of the > >> >component using the 'parent' program? > >> > > >> >Something parent.NewsFromMyComponent(TRUE) like I would do with public > >> >elements on a form: MyForm.NewsFromTheSecondForm(Me.Width) > >> > > >> > > >> > > >> > > >> Mmm... it is really not clear what you want to do - anyway, I think you > >> should use events: they are portable, clean and safe. > >> > >> If, instead, you are writing a component which should be aware of other > >> controls in the same form, or the same parent, without the intervention > >> of the main program, you can travel the "Parent" property. > >> > >> If you really want to peek & poke with fantasy, take a look at the > >> Object and Class classes (don't remember the exact names). You can > >> discover all the loaded classes, and invoke any method discovered at > >> runtime. But it may be a bad idea... > >> > >> If this does not help, give more information. > >> > >> Regards, > >> Doriano > > > > my project (from now on called 'the program') > > use a in gambas2 written component (from now on called 'the > > component' [which is by it's own, also a executable]). > > 'the component' is embedded on a form of 'the program'. > > So the "parent" is known. > > What I want is calling a Sub/Function, declared in 'the program', out > > from 'the component' ..... calling back to the caller. > > > > Better now ? > > > > Charlie > >
Salut Doriano & Fabian, I attached a (no, two) gambas2 project(s), which does now, all I expected to find when I started for that. Finally what I need is a user "named" Interface which comes back to the caller which is the users project, who had called my component. First I planed that the component has to be embedded (for the parents stuff) but now I found out, I can call back, if the called, knows the Name of the caller (and the method to call). That gives me and the user a lot of freedom. The reason, why EVAL work with intern method only if you give the name of the owner (ME.Name) is an extra job for Benoît! Amicalement Charlie [OperatingSystem] OperatingSystem=Linux KernelRelease=2.6.24-27-generic DistributionVendor=Ubuntu DistributionRelease="Ubuntu 8.04.4 LTS" [System] CPUArchitecture=i686 TotalRam=506932 kB [Gambas] Gambas1=gbx-1.0.17 Gambas1Path=/usr/bin/gbx Gambas2=2.20.1 Gambas2Path=/usr/local/bin/gbx2 Gambas3=2.99.0 Gambas3Path=/usr/local/bin/gbx3
callBackProg.tar.bz2
Description: application/bzip-compressed-tar
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
