Re: [Iup-users] How to help debug this segfault?

2015-08-11 Thread Antonio Scuri
Ok. Independent from language. The new IUP Tutorial is a good starting point, what's online already has more pages than the download version. Best, Scuri On Tue, Aug 11, 2015 at 9:04 AM, Jörg F. Wittenberger joerg.wittenber...@softeyes.net wrote: Am 10.08.2015 um 19:20 schrieb Antonio

Re: [Iup-users] Cocoa question

2015-08-11 Thread Antonio Scuri
It seems that the font module is not returning the correct size for the text. The iup*_font.c module is essential for a correct layout. Try different FONT attributes to see how this size difference behaves. Best, Scuri On Tue, Aug 11, 2015 at 9:07 AM, Eric Wing ewmail...@gmail.com wrote: On

Re: [Iup-users] How to help debug this segfault?

2015-08-11 Thread Jörg F. Wittenberger
Sorry for following up on my own message. I just considered the problem again and got stuck. Am 11.08.2015 um 14:04 schrieb Jörg F. Wittenberger: Am 10.08.2015 um 19:20 schrieb Antonio Scuri: Well, I really don't know. Just know that the calls are not actually active all at the same

Re: [Iup-users] How to help debug this segfault?

2015-08-11 Thread Antonio Scuri
Ok. Now I see. IupFlush is usually used when you need to processes messages after changing elements attributes that need to be updated by the system. I would recommend using IupMainLoop and something else for the database connections, not the way around using IupFlush. There are several

Re: [Iup-users] How to help debug this segfault?

2015-08-11 Thread Jörg F. Wittenberger
Am 11.08.2015 um 16:31 schrieb Jörg F. Wittenberger: Am 11.08.2015 um 16:27 schrieb Antonio Scuri: Maybe you can try the IDLE and see how it behaves. There is also another possibility. The IDLE callback is somewhat equivalent of while(IupLoopStep() != IUP_CLOSE) { do something }

Re: [Iup-users] How to help debug this segfault?

2015-08-11 Thread Antonio Scuri
Maybe you can try the IDLE and see how it behaves. There is also another possibility. The IDLE callback is somewhat equivalent of while(IupLoopStep() != IUP_CLOSE) { do something } But this is also high CPU consuming. So, to avoid this, you can try: while(IupLoopStepWait() !=

Re: [Iup-users] How to help debug this segfault?

2015-08-11 Thread Jörg F. Wittenberger
Am 11.08.2015 um 16:27 schrieb Antonio Scuri: Maybe you can try the IDLE and see how it behaves. There is also another possibility. The IDLE callback is somewhat equivalent of while(IupLoopStep() != IUP_CLOSE) { do something } Not too bad. Though that's essentially the loop my

Re: [Iup-users] How to help debug this segfault?

2015-08-11 Thread Antonio Scuri
Sorry, can't help more than that. And this problem will be the same in any toolkit you would use, not just IUP. Best, Scuri Em 11/08/2015 11:52, Jörg F. Wittenberger joerg.wittenber...@softeyes.net escreveu: Am 11.08.2015 um 16:31 schrieb Jörg F. Wittenberger: Am 11.08.2015 um 16:27 schrieb