Postinit
  Home FAQ Contact Sign in
 
 Advanced search
MATCHING GROUPS



more...
POPULAR GROUPS

more...
found 182 articles for 0.303 sec
Hi Bart, On Mon, 22 Sep 2008, at 10:18:27 [GMT +0200] (which was 10:18 where I live) you wrote about: 'VO SP2 - error (SQL)' > I've just installed SP2, touched all entities and rebuild my application. > When running the application, I get the following error message : > Error Code: 13 [NO EXPORTED METHOD] > Subsystem Base > Funcion: SEND > Argument: ITQKLEMMEN:DESTROY > Callstack:     

Group: comp.lang.clipper.visualobjects · Group Profile · Search for Postinit in comp.lang.clipper.visualobjects
Author: Robert van der Hulst
Date: Sep 22, 2008 08:29

A closer look in the SDK tells me that if the owner window is a handle it is just passed on through to the super:init, which eventually is the window:init, so it should work as long as it is allowed for a win32 window to have a .net window as parent. Just try it and see what happens... The SDK that I've been looking in is the SDK for VO2.8 sp1. Mathias ninad...@gmail.com skrev: On Sep
Show full article (0.78Kb)
What you are quoting is the help file. As part of the VO install there is a folder SDK where the source code of VO is. There you can see how the owner is set in the Init (or other methods) John ninadunn@gmail.com schreef: > On Sep 10, 6:20 pm, Mathias <mathias.hakans...@consultec.se> wrote: >> You are not telling ut what kind of window "TheWindow" is. A peek in >> the Window:Init in     

Group: comp.lang.clipper.visualobjects · Group Profile · Search for Postinit in comp.lang.clipper.visualobjects
Author: Mathias
Date: Sep 11, 2008 01:29

On Sep 10, 6:20 pm, Mathias <mathias.hakans...@consultec.se> wrote: You are not telling ut what kind of window "TheWindow" is. A peek in the Window:Init in the SDK tells me that you can submit the owner window as a handle (data type: ptr). The SDK automatically encapsulates the handle in a class called _ForeignWindow. oWindow := TheWindow{oParent} Mathias ninad...@gmail
Show full article (2.36Kb) · Show article thread
Amusing definition of 'unusable' <g>. I agree that its features are a little hidden and it still has bugs. When used on tab controls it is frightful for resizing etc however it can be forced to work. It is very flexible now that it is unbundled to being a stand-alone control but you just have to be careful about owners, menus and the message pump. It will never be as good as the one with     

Group: comp.lang.clipper.visualobjects · Group Profile · Search for Postinit in comp.lang.clipper.visualobjects
Author: John Martens
Date: Sep 10, 2008 22:54

On Mon, 1 Sep 2008 20:01:18 +0200, E®!k \\/!sser <nospam@nospam.com> wrote: Hello Erik, You can code it in the postinit of the window. SELF:oSplitter := __SplitView{SELF,-1,Point{0,0},SELF:Size,TRUE,TRUE,SPLIT_VERTALIGN} Good you've managed to find something about it! The new feature is only documented in the What's new list. It is not only missing in the control window but also absent
Show full article (2.15Kb) · Show article thread
Dick, > That should be a possible solution, but the splitview control isn't > part of the available controls in the window os it's unusable. I > remember Robert once said he forgot to include it and I would rather > not wait until the end of the North American summer.... Unusable? You can code it in the postinit of the window. SELF:oSplitter := __SplitView{SELF,-1,Point{0,0},SELF:Size     

Group: comp.lang.clipper.visualobjects · Group Profile · Search for Postinit in comp.lang.clipper.visualobjects
Author: ninadunn
Date: Sep 10, 2008 14:40

Jorge I use the bBrowse with the characteristics default I know there are ways to improve their presentation, make more "modern" I subclassed bBrowser many years ago to get a uniform colour scheme throughout the application, setting default values for everything, method/access/assign to turn the selectionbar hilite on/off & change it's colour depending on the value show, etc...
Show full article (1.84Kb) · Show article thread
I am very happy to hear your success! Craig -------- "Geoff Chambers" <gchambers02@msn.com> wrote in message news:88749110-1113-4621-88c8-5be4c21c0b88@59g2000hsb.googlegroups.com... >I would first like to say hello to all the attendees at Geoff > Schaller's Master Class Workshop. Hope you have been as successful > with your training as I have. > > I took the class because I made the decision     

Group: comp.lang.clipper.visualobjects · Group Profile · Search for Postinit in comp.lang.clipper.visualobjects
Author: Geoff Schaller
Date: Sep 5, 2008 17:47

Martin, The short answer is no. However what is it that you are seeking to fix? Mostly the Init is only control and menu creation based on a resource dialog so there is nothing that you really need to control with a block. A better way might be to create an error handler in the PreInit() and then undo it in the PostInit(). That way it can be done at a class level and can give you a form
Show full article (1.10Kb) · Show article thread
    

Group: comp.lang.clipper.visualobjects · Group Profile · Search for Postinit in comp.lang.clipper.visualobjects
Author: D.J.W. van Kooten
Date: Sep 1, 2008 22:52

Show full article (0.46Kb) · Show article thread
    

Group: comp.lang.clipper.visualobjects · Group Profile · Search for Postinit in comp.lang.clipper.visualobjects
Author: E®!k \/!sser
Date: Sep 1, 2008 11:01

Show full article (0.56Kb) · Show article thread
    

Group: comp.lang.clipper.visualobjects · Group Profile · Search for Postinit in comp.lang.clipper.visualobjects
Author: Stephen Quinn
Date: Aug 23, 2008 21:58

Show full article (1.11Kb) · Show article thread
    

Group: comp.lang.clipper.visualobjects · Group Profile · Search for Postinit in comp.lang.clipper.visualobjects
Author: Craig Dawson
Date: Aug 14, 2008 15:28

Show full article (2.39Kb) · Show article thread
    

Group: comp.lang.clipper.visualobjects · Group Profile · Search for Postinit in comp.lang.clipper.visualobjects
Author: Geoff Schaller
Date: Aug 13, 2008 14:55

Show full article (1.02Kb) · Show article thread
1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 · 9 · next