× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



FYI, the VARPG language has changed in the meantime, so you could use
freeform and you can also use dotted name notation

So this statement

      C            Eval      %SetAtr('Main':'Container':'Width') =
      C                             (%NewWidth * .5) - 12
could look like this
               C            Eval      Main.Container.Width =
      C                             (%NewWidth * .5) - 12

or like this
        Main.Container.Width = (%NewWidth * .5) - 12;

This makes it a bit easier to work with VARPG


Claus Weiss Visual AD tools, email: weiss@xxxxxxxxxx
Dept 522 IBM Canada Lab tie 969-3987 Phone(905)413-3987 FAX(905)413-4850
Greetings from Toronto
WDSc for iSeries homepage: ibm.com/software/awdtools/iseries
WDSc newsgroup: news://news.software.websphere.studio400     |   VARPG
newsgroup: news://news.software.ibm.com/ibm.software.varpg,


                                                                           
             Booth Martin                                                  
             <booth@xxxxxxxxxx                                             
             om>                                                        To 
             Sent by:                  Websphere Development Studio Client 
             wdsci-l-bounces@m         for iSeries <wdsci-l@xxxxxxxxxxxx>  
             idrange.com                                                cc 
                                                                           
                                                                   Subject 
             03/27/2007 03:26          Re: [WDSCI-L] VARPG                 
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
                 Websphere                                                 
                Development                                                
             Studio Client for                                             
                  iSeries                                                  
             <wdsci-l@midrange                                             
                   .com>                                                   
                                                                           
                                                                           




Can you explain a bit more, please?

1-Memory becomes less and less of an issue every year, but parts, so far
as I know, do not take up memory until they are used.
2-Not sure what this means.  I suspect though that it may mean that you
are trying to apply green screen design to GUI solutions, and are
cramming a lot of stuff onto one window?
3-Painting issues?  I believe you, but of all the problems I ever faced
with VARPG, painting was negligible.

(Just as a additional comment, if anyone wants to see some screen shots
of VARPG windows, written in the same *RPG* that you already know,
here's a link to some shots I posted a few years ago.)

http://tinyurl.com/dx7bc

As you look at them, realize that they are written in *RPG*.  For some
reason no one really believes that until they see their own first
application.

Here's a snippet of code; now tell me that you don't already know VARPG.
   :) One piece of information: BegAct means Begin Action.  Everything
is event driven, there is no loop.  So, until the user does something,
nothing happens.  But when the user does do something, just that event
is acted upon.
       *
       * Declare display size System attributes
      D%DSPHEIGHT       S              4  0
      D%DSPWIDTH        S              4  0

       * Declare %NewHeight, and %NewWidth event attributes. These will
       * contain the width and height of the window after it is has been
       * resized.
      D%NEWHEIGHT       S              4  0
      D%NEWWIDTH        S              4  0
       * The new mode of a window: ( 2 = minimized)
      D%NewMode         S              1  0


*-------------------------------------------------------------------=
       *   Sample to resize a window                    Sub Routine =
*-------------------------------------------------------------------=
      C   ResizeSr BEGSR
       * Do not do if the new mode is "Minimized":
      C            If        %NewMode = 2
      C            Else
       * Set Container:
      C            Eval      %SetAtr('Main':'Container':'Width') =
      C                             (%NewWidth * .5) - 12
      C            Eval      %SetAtr('Main':'Container':'Left') = 4
      C            Eval      %SetAtr('Main':'Container':'Height')

      C                      (%NewHeight * .5) - 10
      C            Eval      %SetAtr('Main':'Container':'Top') = 4
       * Set Calendar:
      C            Eval      %SetAtr('Main':'Calendar':'Width') =
      C                      (%NewWidth * .5) - 12
      C            Eval      %SetAtr('Main':'Calendar':'Left') =
      C                      (%NewWidth * .5)
      C            Eval      %SetAtr('Main':'Calendar':'Height') =
      C                      (%NewHeight * .5) - 10
      C            Eval      %SetAtr('Main':'Calendar':'Top') = 4

      C            EndIf
      C            ENDSR

*-------------------------------------------------------------------=
       *    Set on last record:
*-------------------------------------------------------------------=
      C     MAIN   BEGACT    DESTROY       MAIN
      C            Eval      *InLR = *On
      C            ENDACT

*-------------------------------------------------------------------=
       *    Resizing a Window                                        =
*-------------------------------------------------------------------=
      C     MAIN   BEGACT    RESIZE        MAIN
      C            Exsr      ResizeSr
      C            ENDACT



Justin Taylor wrote:
My object-oriented comment referred to the fact that in VA-RPG, all
screen fields (parts in VA-RPG speak) must exist at compile time.

Which means:
1. All parts take up memory (more of an issue with PC apps)
2. Parts cannot be laid out via code, so overlapping parts are a pain
(not a problem with DDS)
3. Showing and hiding parts results in some strange painting issues (not
an issue with 5250)

--
---------------------------------
Booth Martin
http://www.Martinvt.com
---------------------------------
--
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.