Sanel Zukan wrote:
> Hi,
>
>> I submitted STR#1662 to address this:
>> http://www.fltk.org/str.php?L1662
>>
>> ..as I think all pointer returns should document the
>> return value's memory implications.
>
> Thanks for the submission, so it can stand as note for those who do
> further changes :)
>
Hi,
> I submitted STR#1662 to address this:
> http://www.fltk.org/str.php?L1662
>
> ..as I think all pointer returns should document the
> return value's memory implications.
Thanks for the submission, so it can stand as note for those who do
further changes :)
I'm fully agree with you. Also, do
Greg Ercolano wrote:
>> No, since is pointer to the internal data. If you use some specific fonts
>> that fltk does not provide as internal ones, probably you can cache some
>> of them :)
>
> If the docs don't cover this, they probably should [..]
I submitted STR#1662 to address this:
Sanel Zukan wrote:
>> Like the subject asks: Do I need to delete what fltk::font(const char
>> *,int) returns?
>> Or am I supposed to leave it be because FLTK2 is caching it to share with
>> others.
>> I do repeatedly call this function a lot. So, I may implement a Font *
>> cache of my own if
> Like the subject asks: Do I need to delete what fltk::font(const char *,int)
> returns?
> Or am I supposed to leave it be because FLTK2 is caching it to share with
> others.
> I do repeatedly call this function a lot. So, I may implement a Font * cache
> of my own if FLTK2 is not doing it.
FLTK2
Like the subject asks: Do I need to delete what fltk::font(const char *,int)
returns?
Or am I supposed to leave it be because FLTK2 is caching it to share with
others.
I do repeatedly call this function a lot. So, I may implement a Font * cache
of my own if FLTK2 is not doing it.
6 matches
Mail list logo
