Re: [fpc-pascal] getopts unit vs CustApp parameter handling

2016-05-05 Thread Graeme Geldenhuys
On 2016-05-04 10:24, Michael Van Canneyt wrote: > It would be, but you had better update your interface, various things > have been added. I’ve updated the Interface last night to match that of FPC Trunk. https://github.com/graemeg/fpGUI/blob/develop/src/corelib/fpg_cmdlineparams.pas I was abou

Re: [fpc-pascal] getopts unit vs CustApp parameter handling

2016-05-04 Thread Graeme Geldenhuys
On 2016-05-04 10:24, Michael Van Canneyt wrote: > It would be, but you had better update your interface, various things > have been added. I assume you mean FPC 2.6.4 (what I used) verses FPC 3.x. Thanks for the tip, I’ll take a look tonight and update the code appropriately. Regards, Graeme _

Re: [fpc-pascal] getopts unit vs CustApp parameter handling

2016-05-04 Thread Michael Van Canneyt
On Wed, 4 May 2016, Graeme Geldenhuys wrote: On 2016-05-03 11:02, Michael Van Canneyt wrote: They serve the same purpose, but function differently. Simply use the one whose interface you like best. I'm used to the command line parameters handling of CustApp, but none of my applications are

Re: [fpc-pascal] getopts unit vs CustApp parameter handling

2016-05-04 Thread Graeme Geldenhuys
On 2016-05-03 11:02, Michael Van Canneyt wrote: > They serve the same purpose, but function differently. > > Simply use the one whose interface you like best. I'm used to the command line parameters handling of CustApp, but none of my applications are TCustomApp based. Plus CustApp gives no code

Re: [fpc-pascal] getopts unit vs CustApp parameter handling

2016-05-03 Thread Michael Van Canneyt
On Tue, 3 May 2016, Graeme Geldenhuys wrote: Hi, Is the getopts unit deprecated or not recommended for usage? It is not deprecated. The reason I ask is because I see CustApp has similar functionality to the getopts unit, but the custapp has it’s own implementation - it doesn’t use the get