![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
As you know, a Paradox "application" consists of many parts: scripts, forms, reports, and libraries. What you may not know is that most of these are actually Windows DLLs. This means that, courtesy of Windows, they are neatly self-contained and inherently shareable. But independence, as any new kid in college will tell you, does have its drawbacks. How can you enable the various independent forms to share information easily? The answer is: libraries. A library (.LSL, .LDL) is a unit that contains only executable (ObjectPAL) code. It also contains its own set of global variables. Any form(s) in your Windows session can open the same library at the same time, and when they do so, they all access a single common /instance/ of that library. Thus, the same instance-data: the same global variables. Now, there's unfortunately no way for a form to _directly_ access a library's variables, but you can provide a pair of /methods/ to do so... assume: var globals DynArray[] AnyType endVar Now: method getValue(key String) AnyType return globals[key] endMethod and: method setValue(key String, toValue AnyType) globals[key] = toValue endMethod A library is a great place to put "most of your application," because not only does it allow a single copy of the code to be shared, it also allows all kinds of common data to be kept there. There's only one caveat: the library must not be closed, even for a moment. One way to do that is to have a "main menu" form open the library, and then for the form to remain open throughout the life of the application. |
#3
| |||
| |||
|
|
What you may not know is that most of these are actually Windows DLLs. IMO, that's an old myth. When I asked Dan Alder about this a couple of years ago, he said, forms, and libraries have the structure of a DLL, but they aren't really DLLs. |
#4
| |||
| |||
|
#5
| |||
| |||
|
#6
| |||
| |||
|
|
Have you tried storing graphic images in a Library (as in DLL'ss) which can be shared with Forms? For win versions < XP the graphics look fine within paradox, when they are |
#7
| |||
| |||
|
#8
| |||
| |||
|
|
Who is Mike Robinson? |
#9
| |||
| |||
|
|
"Jean Friedberg" <jfriedberg (AT) mycomcast (DOT) com> wrote in message news:43e3bac3$1 (AT) pnews (DOT) thedbcommunity.com... Who is Mike Robinson? Mike *is* Sundial.. |
#10
| |||
| |||
|
|
If the Image file is already stored in a Paradox Object (such as a Paradox Library), then there won't be any further resolution degradation. I found a way to store Image files in a Paradox Library and call them into one or more Form(s) Graphic objects. Very much like using a DLL. ) |
!![]() |
| Thread Tools | |
| Display Modes | |
| |