Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Equivalent of AfterRowColChange in List Boxes
Message
From
17/10/2008 08:20:48
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
 
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Vista
Network:
Windows 2008 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01354517
Message ID:
01355563
Views:
25
>>Hi Terry
>>
>>>On the contrary, that may be great. The only reason I'm using a listbox is because grids don't have the moverbars, and it's so I can reorder "sub-jobs" of a "job" in a job costing scheme. The rest of teh form features grids and it would be more in keeping to have a grid for this function. As it stands, I tried to disguise the list like a grid, with command button headers, usw.
>>
>>Hm, I use a set of buttons above my grid to move the records. I think about to incorporate the code provided by Marcia
>>
>>>Just one thing: Funnily enough I've never used create class or programmatically created classes in my code - always having prepared classes visually and dragged them onto the form. I can't seem to find any help on how to use this practically. For instance, I've run the create class code, as a prog, but nothing is apparently produced. How do I use this to create a permanent class that I can drag onto my form and then edit it visually?
>>
>>I guess you need an refresh. Beg your pardon for repeating old stuff, but I'm not sure where to start/stop
>>
>>You need to have a target. If you run the prg with a class definition like
>>
>>DEFINE CLASS MyClass as grid
>>*....
>>ENDDEFINE
>>
>>
>>it does nothing
>>
>>You need to instantiate an object from this class (AKA create an instance of the class) via ADDOBJECT or NEWOBJECT to a container (Form, Page, _SCREEN etc)
>>
>>set classlib to yourprg.prg
>>_screen.ADDOBJECT('ObjName','MyClass')
>>
>>Do you have set the object created visible? Objects created via createobject are ! visible by default.
>>
>>_screen.MyClass.visible = .t.
>>
>>
>>You may shorten this for tests into one prg:
>>
>>_screen.ADDOBJECT('ObjName','MyClass')
>>_screen.MyClass.visible = .t.
>>
>>DEFINE CLASS MyClass as grid
>>*....
>>ENDDEFINE
>>
>>
>>and run the prg.
>>
>>You can not drag / drop a prg based class
>>
>>I, myself do not use much prg based classes except Header and Column and some registry stuff. But it works fine to give an example on how a class should work if you can not provide the vcx. (Like in a pre section of UT)
>>
>>Other people do not agree in this and do all in prg based classes. There is a fear of loosing vcx memos, something I do not have seen the last 10 years, but there was a serious problem before.
>>
>>HTH
>>Agnes
>
>Sorry, Agnes
>
>I was so concentrating on this problem and others, I forgot to thank you for your trouble.
>
>Vielen Dank

Keine Ursache
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Previous
Reply
Map
View

Click here to load this message in the networking platform