Re: [Iup-users] IupScanf / IupGetParam Bug

2015-05-31 Thread John Spikowski
On Fri, 2015-05-29 at 10:12 -0300, Antonio Scuri wrote: > But what is the bug? IupGetparam is widely used around here. > 'Bug' was Windows programmers dealing with "\n". ;-) -- ___

Re: [Iup-users] IupScanf / IupGetParam Bug

2015-05-30 Thread John Spikowski
I compiled the iupscanf example and it seems to work but it looks like it's revealing the other problem I reported with screen init. (see attached screenshot) On Fri, 2015-05-29 at 10:12 -0300, Antonio Scuri wrote: > But what is the bug? IupGetparam is widely used around here. > > > Best, >

Re: [Iup-users] IupScanf / IupGetParam Bug

2015-05-29 Thread Antonio Scuri
But what is the bug? IupGetparam is widely used around here. Best, Scuri On Fri, May 29, 2015 at 7:31 AM, John Spikowski wrote: > Antonio, > > One of the OxygenBasic compiler forum member discovered a bug with > IupScanf and I suggested using the recommended IupGetParam function > instead. A

[Iup-users] IupScanf / IupGetParam Bug

2015-05-29 Thread John Spikowski
Antonio, One of the OxygenBasic compiler forum member discovered a bug with IupScanf and I suggested using the recommended IupGetParam function instead. As it turns out, they both don't seem to work. Can you verify on your end? John -- Quote: Char