Font metrics is essential in IUP layout computation. The iup*_font.c
module is one of the most important driver module. Without
iupdrvFontGetStringWidth, iupdrvFontGetCharSize,
and iupdrvFontGetMultiLineStringSize IUP will simply not work.
I'm going to have to think about this. Each
System limitation are common. The idea is to try to fit IUP rules to the
system rules. But first we assume a generic approach, if things go wrong
then see what are the system limitations.
Set RASTERSIZE of the dialog to 500x550, these value must appear at
cocoaDialogLayoutUpdateMethod,
or at
On 8/11/15, Antonio Scuri sc...@tecgraf.puc-rio.br wrote:
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.
I have something that is
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
On 7/27/15, Eric Wing ewmail...@gmail.com wrote:
On 7/26/15, Antonio Scuri sc...@tecgraf.puc-rio.br wrote:
Take a look at the iupgtk_image.c. The necessary conversions can be
copied
from there.
iupdrvImageCreateImageRaw() and iupdrvImageGetRawData()
are opposite functions I doubt that
On 7/26/15, Antonio Scuri sc...@tecgraf.puc-rio.br wrote:
Take a look at the iupgtk_image.c. The necessary conversions can be copied
from there.
iupdrvImageCreateImageRaw() and iupdrvImageGetRawData()
are opposite functions I doubt that you will be able to reuse
code.
Certainly 0x is an invalid valid value it is not what
the system expects. In your case the native parent will be the dialog.
ih-parent-handle is not necessaryly the native parent, the
function iupChildTreeGetNativeParentHandle(ih) will return you that.
Best,
Scuri
On Sat, Jul
On 7/25/15, Antonio Scuri sc...@tecgraf.puc-rio.br wrote:
Certainly 0x is an invalid valid value it is not what
the system expects. In your case the native parent will be the dialog.
ih-parent-handle is not necessaryly the native parent, the
function
On 7/23/15, Antonio Scuri sc...@tecgraf.puc-rio.br wrote:
Hi,
In the iup/test folder there are several small applications that covers
many aspects of every control. The dialog.c test does not depends on any
other control.You can show just the dialog without any control inside. This
is
Hi,
In the iup/test folder there are several small applications that covers
many aspects of every control. The dialog.c test does not depends on any
other control.You can show just the dialog without any control inside. This
is essential to test specific diaog features.
Very interesting
I found a Mac/Cocoa repo of Iup linked to on the main page. It is from
2010. I also noticed the 3.0 release from 2010 had those exact same
files. They now seem to be removed from the official repo.
If I wanted to take an initial stab at getting some minimal Cocoa
backend working with Iup, how
On 7/22/15, Antonio Scuri sc...@tecgraf.puc-rio.br wrote:
Hi,
That cocoa driver was actually maintained outside the official
repository. It was a brave initiative by Heesob Park, but he did not have
the time necessary to complete it. So I leave it outside.
If you want to give it a try
Hi,
That cocoa driver was actually maintained outside the official
repository. It was a brave initiative by Heesob Park, but he did not have
the time necessary to complete it. So I leave it outside.
If you want to give it a try that's great news. I would love to help you
understand the
Hi Antonio,
A member (Armando I. Rivera (AIR)) of our All BASIC developer forum is
revitalizing an Apple GUI library Claro. It looks like a great candidate
for a Apple OSX IUP driver.
http://www.allbasic.info/forum/index.php?topic=347.msg4379#msg4379
John
On Wed, 2015-07-22 at 18:00 -0300,
14 matches
Mail list logo
