Hello there, I have to progam apps for a CE.net device with a 800x600 screen. So of=20 course there is some need for a MDI-style surface, say: having Forms=20 showing inside a main form, not besides it, not under it (like in eVB3..)= =2E After some experimenting with adding S.W.F.Form Objects to the Controls=20 Collection of a bigger (main) form, which worked well (except some=20 strange behaviour at first tries), I "googled" for other developer=B4s=20 experiences with this technique - and found nothing (!). Seriously. So there comes my Question: Are there any known, serious drawbacks on=20 adding Forms to the Controls Collection? I know that this may be an evil = hack, but it works well for my needs as far as is tested it yet. There=B4= s=20 only something left: Some bad feeling in my belly an the concerns it may = break the whole app at some point in future... TIA Matthias
Yep, hell... Sorry, I don't really have a serious comment about your original post... just couldn't resisit... damn Fridays! (: P - Chris [quoted text, click to view] "Matthias Kerber" <pfennigfuchser@gmx.de> wrote in message news:bjsucb$24n$07$1@news.t-online.com... > > Matthias Kerber wrote: > > Hello there, > > hm.. silence.. > >
[quoted text, click to view] Matthias Kerber wrote: > Hello there,
hm.. silence..
Hello Matthias, Parenting a form by another form is not a supported scenario in the .NET Compact Framework v1.0. I would recommend avoiding doing this. Thank you, Sergiy. This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- | From: Matthias Kerber <pfennigfuchser@gmx.de> | Newsgroups: microsoft.public.dotnet.framework.compactframework | Subject: Experimental MDI Forms Question (will i go to hell?) | Date: Thu, 11 Sep 2003 21:54:41 +0200 | Organization: T-Online | Lines: 25 | Message-ID: <bjqk4l$vii$04$1@news.t-online.com> | Mime-Version: 1.0 | Content-Type: text/plain; charset=ISO-8859-1; format=flowed | Content-Transfer-Encoding: quoted-printable | X-Trace: news.t-online.com 1063310293 04 32338 Jj8PVB5XSlAJW 030911 19:58:13 | X-Complaints-To: usenet-abuse@t-online.de | X-ID: SxaOH0ZdoeBvI35caK53hMXN-c+NFk-yjivcaUerfHnWNuJMmUjPoT | User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.3) Gecko/20030312 | X-Accept-Language: de, de-at, en-us, en | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!newsmm0 0.sul.t-online.com!t-online.de!news.t-online.com!not-for-mail | Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.compactframework:33382 | X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework | | Hello there, | I have to progam apps for a CE.net device with a 800x600 screen. So of | course there is some need for a MDI-style surface, say: having Forms | showing inside a main form, not besides it, not under it (like in eVB3..). | After some experimenting with adding S.W.F.Form Objects to the Controls | Collection of a bigger (main) form, which worked well (except some | strange behaviour at first tries), I "googled" for other developer´s | experiences with this technique - and found nothing (!). Seriously. | So there comes my Question: Are there any known, serious drawbacks on | adding Forms to the Controls Collection? I know that this may be an evil hack, but it works well for my needs as far as is tested it yet. There´s | only something left: Some bad feeling in my belly an the concerns it may break the whole app at some point in future... | TIA | Matthias |
Don't see what you're looking for? Try a search.
|