Modero

If you just convert the G3 file to G4, and not using any of the features of G4, it should be easy to integrate.

The difference is just in notation of the device address, where you may have to modify your code in some details:

DEFINE_CALL 'MyCall'(PANEL,<any more parameters>)
{
}

In general, this will create a compiler error, because it's not possible to pass the Number:Port:System structure thru the Integer PANEL.

If you don't use more than one Port of the G4 panel, just define the panel in the old way

DEFINE_DEVICE
MyPanel = 10001

The master will add the :1:0 internally. This is not that styleguide, but will work.

If your G3 file has more than "Device Used 1", after converting to G4 you'll get more ports to your G4 file.

DEFINE_DEVICE
(* G3 panel *)
(*
MyPanel_A = 128
MyPanel_B = 129
MyPanel_C = 130
MyPanel_D = 131
*)
// converted to G4
MyPanel_A = 10001:1:0
MyPanel_B = 10001:2:0
MyPanel_C = 10001:3:0
MyPanel_D = 10001:4:0

In this situation, it's better to modify your calls.

DEFINE_CALL 'MyCall'(DEV PANEL,<any more parameters>)
{
}


The basic commands for the panel are still the same (TEXT, @PPN/@PPF,PAGE, etc).
Only one difference in the basic commands is 'PAGE-' (page command without a page name). This will tell the panel to do a "Previous" pageflip.

Regards,
Marc

DHawthorne wrote:

You can "fake" old G3 routines into accepting G4 device numbers without modification by simply using .NUMBER after the device name if you are working in NetLinx. Soo you could use the old "DEFINE_CALL 'MyCall'(PANEL,<any more parameters>)" by calling it with "CALL 'MyCall'(dvPanel.NUMBER, <parameters>)".

Eh... you are right, I forgot that simple way