[Gambas-user] gb3: gb.opengl - dynamically dimensioning a public 2D array of texture IDs

2011-08-03 Thread Kevin Fishburne
Previously I needed to create a 2D array of texture IDs. I couldn't get it to work worth a damn, so what I did instead was to create a texture Structure, then create an array of those structures. It works extremely well and allows me to store more information about each texture: ' Texture defin

Re: [Gambas-user] gb3: public array that is dimensioned later

2011-08-03 Thread Kevin Fishburne
On 08/03/2011 09:03 PM, Benoît Minisini wrote: >> On 08/03/2011 08:09 PM, Benoît Minisini wrote: On 08/03/2011 07:00 PM, Kevin Fishburne wrote: > I need to create a public array in a module but specify its dimensions > in a procedure later. Is this possible, and how would it be done >>

[Gambas-user] gb.report gambas3

2011-08-03 Thread herberth guzman
goodnight community would like to help me with gb.report I managed to do some reports in gambas3 but only funsion me with code creating them, I would like to design a graphical report and you look as designed, if you design a report to run it when you looks misconfigured. And also I have the probl

Re: [Gambas-user] gb3: public array that is dimensioned later

2011-08-03 Thread Benoît Minisini
> On 08/03/2011 08:09 PM, Benoît Minisini wrote: > >> On 08/03/2011 07:00 PM, Kevin Fishburne wrote: > >>> I need to create a public array in a module but specify its dimensions > >>> in a procedure later. Is this possible, and how would it be done > >> > >> I forgot to mention, I'd like it to be

Re: [Gambas-user] gb3: public array that is dimensioned later

2011-08-03 Thread Kevin Fishburne
On 08/03/2011 08:09 PM, Benoît Minisini wrote: >> On 08/03/2011 07:00 PM, Kevin Fishburne wrote: >>> I need to create a public array in a module but specify its dimensions >>> in a procedure later. Is this possible, and how would it be done >> I forgot to mention, I'd like it to be a 2D array, thou

Re: [Gambas-user] gb3: public array that is dimensioned later

2011-08-03 Thread Benoît Minisini
> On 08/03/2011 07:00 PM, Kevin Fishburne wrote: > > I need to create a public array in a module but specify its dimensions > > in a procedure later. Is this possible, and how would it be done > > I forgot to mention, I'd like it to be a 2D array, though I could write > workaround code if it has t

Re: [Gambas-user] gb3: public array that is dimensioned later

2011-08-03 Thread Kevin Fishburne
On 08/03/2011 07:00 PM, Kevin Fishburne wrote: > I need to create a public array in a module but specify its dimensions > in a procedure later. Is this possible, and how would it be done I forgot to mention, I'd like it to be a 2D array, though I could write workaround code if it has to be 1D. -

[Gambas-user] gb3: public array that is dimensioned later

2011-08-03 Thread Kevin Fishburne
I need to create a public array in a module but specify its dimensions in a procedure later. Is this possible, and how would it be done? -- Kevin Fishburne Eight Virtues www: http://sales.eightvirtues.com e-mail: sa...@eightvirtues.com phone: (770) 853-6271

Re: [Gambas-user] Issue 75 in gambas: Split function problem

2011-08-03 Thread gambas
Updates: Status: Invalid Labels: -Version Version-2.22.0 Comment #1 on issue 75 by benoit.m...@gmail.com: Split function problem http://code.google.com/p/gambas/issues/detail?id=75 This behaviour is by design. Read the Split() documentation, and use its fourth optional argument

[Gambas-user] Issue 75 in gambas: Split function problem

2011-08-03 Thread gambas
Status: New Owner: Labels: Version Type-Bug Priority-Medium OpSys-Any Dist-Any Arch-Any Desktop-Any GUI-Any New issue 75 by fabio.st...@gmail.com: Split function problem http://code.google.com/p/gambas/issues/detail?id=75 Split function problem Version: 2.21 Revision: Operating system: Li

Re: [Gambas-user] gb3: gb.opengl will not render alpha channel of 2D texture

2011-08-03 Thread Laurent Carlier
Le Lundi 1 Août 2011 10:47:14, Benoît Minisini a écrit : > > Glu.Build2DMipmaps() could segfault if it receives a NULL image. Anyway, in > revision #3958, you don't have to do all that trick: image alpha channel > should be correctly taken into account in OpenGL APIs. > > Regards, Good catch! +