Alessandro,
to get the length of an MP3 file (since gb.sdl.sound works primarily with
mp3s)
I would personally write an ID3Tag module to get the mp3's length and then
load it
through gb.sound.sdl afterward.
or if you want you could also explore the option of using an external player
for your
progr
2010/1/4 Doriano Blengino :
> My idea was to raise an event when a line has been read
Based on what I just posted to the developer's list, you will need to
be specific about what defines an end of line. For example:
NUL ^@ \0 Null character
ETX ^C End of Text
LF
2010/1/4 Benoît Minisini :
> I wish everyone an happy new MMX year, and I hope that this year will be the
Same to you.
> year of the Gambas 3 release! :-)
It should be, gb3 is good enough.
--
This SF.Net email is spons
Dear Gambas users,
Here is a new release of the stable version:
* Gambas now really works on ARM architecture.
* The SerialPort class does not eat CPU time pointlessly anymore.
* The Exist() and Dir() functions now work correctly for files located inside
the executable.
Here is the full Chan
2010/1/4 Doriano Blengino :
> My idea was to raise an event when a line has been
> read
As an optional setting, that would be absolutely brilliant and would
resolve a number of potential and real problems.
> I would like an event for every line,
I too would like an event for every line.
> an e
2010/1/4 Doriano Blengino :
> This is the TCP scenario: you send data, and don't know what the hell
> those data have done - only that it is arrived. Never tried to speak FTP
> to a server which talks HTTP? Or to speak HTTP to a CIFS server?
Yes, I have. Many, many times.
> There
> must be a hig
2010/1/4 Doriano Blengino :
> the normal syntax implies that the value you read is
> available just after; in this case, one should "declare" that he wants
> to read a line,
YES! YES! YES!
Pardon my excitement.
> The timeout, as seen in this discussion, could be settable for error
> raising pur
2010/1/3 Benoît Minisini :
>
>
> I'm not sure that the MSDN documentation is a good reference for socket
> programming:
>
> - The Microsoft documentation is often not connected to the reality it tries
> to describe.
>
> - The Windows socket implementation often behaves differently than the other
Ok, sorry.
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
> Argh!
> It is in plan for GB3?
>
Sorry, there is no solution at the moment. It seems the SDL library is not
developed anymore...
The gambas sound component should be redone based on another library,
architecture...
--
Benoît Minisini
---
Alessandro Rinaldi wrote:
>
> Argh!
> It is in plan for GB3?
>
The developers of gambas do not write/maintain SDL. You will have to ask
the SDL developers.
--
View this message in context:
http://old.nabble.com/sdl.sound-and-total-length-of-a-track-tp26998283p27007145.html
Sent from the
Argh!
It is in plan for GB3?
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribu
> I think the topic explains everything..
> With player functions I can only get the current position but not the
> total length...
> Any way to do it?
> Thanks!
> Alessandro
>
Alas the SDL library does not provide a way to get the length of the music
track.
--
Benoît Minisini
---
> Dear Benoit, thanks for the response.
>
> Please see attached mp3 file.
Hem. I don't see it at all...
--
Benoît Minisini
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon'
Benoît Minisini wrote:
>
>
>> >
>> > DrawingArea1 is locked on the main form.
>> >
>> > Thanks
>> > Andy
>>
>
Sorry, located not locked.
--
View this message in context:
http://old.nabble.com/qt4-draw-error-tp27005884p27006233.html
Sent from the gambas-user mailing list archive at Nabble.
> > I believe I have found a qt4 bug. Here is a very simply gambas 3 (svn
> > current to 1/2/10), this works perfectly find and as expected if i switch
> > to gtk.
> >
> > Error is, and it only outputted to the gambas console:
> >
> > QPainter::begin: Widget painting can only begin as a result of
Benoît Minisini wrote:
>
> It's not a Qt4, it's by design: they forbid drawing on a widget outside of
> a
> paint event, so that Qt4 code remains the same between X11, Windows and
> MacOSX.
>
> I think in the future I will enforce the same policy in Gambas for gb.gtk.
>
> There is no need o
> I believe I have found a qt4 bug. Here is a very simply gambas 3 (svn
> current to 1/2/10), this works perfectly find and as expected if i switch
> to gtk.
>
> Error is, and it only outputted to the gambas console:
>
> QPainter::begin: Widget painting can only begin as a result of a paintEven
I believe I have found a qt4 bug. Here is a very simply gambas 3 (svn
current to 1/2/10), this works perfectly find and as expected if i switch to
gtk.
Error is, and it only outputted to the gambas console:
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::se
Benoît Minisini ha scritto:
>> Benoît Minisini ha scritto:
>>
[lot of talk]
>>> The point of view of the client and the server are not the same:
>>>
>>> The client likes blocking socket. It usually asks or sends something to
>>> the server, waits for the answer, and so on...
Attached is a screenshot of what I'm talking about. I've tried both GTK
and QT toolkits, and it seems to do the same thing with both. Shouldn't
the entries "jump" from one to the next, and not let you stop anywhere
in-between, as is shown in the screencap? Any ideas?
BTW, Benoit, you've rek
Kadaitcha Man ha scritto:
> 2010/1/3 Doriano Blengino :
anyway, this is a truely complicated matter.
>>> It is only complicated if you believe that the socket should poke its
>>> nose into business it shouldn't :)
>>>
>>> If the connection goes belly up, the socket can, at b
> Benoît Minisini ha scritto:
> >> [lot of talk]
> >
> > The point of view of the client and the server are not the same:
> >
> > The client likes blocking socket. It usually asks or sends something to
> > the server, waits for the answer, and so on... It usually does one thing
> > at once.
> >
> >
Benoît Minisini ha scritto:
>> [lot of talk]
>>
>
> The point of view of the client and the server are not the same:
>
> The client likes blocking socket. It usually asks or sends something to the
> server, waits for the answer, and so on... It usually does one thing at once.
>
> On the contr
> [lot of talk]
The point of view of the client and the server are not the same:
The client likes blocking socket. It usually asks or sends something to the
server, waits for the answer, and so on... It usually does one thing at once.
On the contrary, the server should serve multiple client con
2010/1/3 Doriano Blengino :
> Kadaitcha Man ha scritto:
>> 2010/1/3 Doriano Blengino :
>>
>>> After a few minutes I suggested that a timeout could simplify things, I
>>> changed my mind. It would not be a totally bad idea but, as most other
>>> mechanisms, it has its problems. First, what is the ri
Kadaitcha Man ha scritto:
> 2010/1/3 Doriano Blengino :
>
>> After a few minutes I suggested that a timeout could simplify things, I
>> changed my mind. It would not be a totally bad idea but, as most other
>> mechanisms, it has its problems. First, what is the right timeout?
>>
>
> It is e
2010/1/3 Doriano Blengino :
> Kadaitcha Man ha scritto:
> After a few minutes I suggested that a timeout could simplify things, I
> changed my mind. It would not be a totally bad idea but, as most other
> mechanisms, it has its problems. First, what is the right timeout?
It is either 0 for no tim
Kadaitcha Man ha scritto:
> 2010/1/3 Doriano Blengino :
>
>
>> after a timeout occurs, one can only assume that
>> the entire write has failed, even if, in fact, some data has been
>> succefully written.
>>
>
> Yes, you are quite correct, but the problem of partial data transfer
> due to a
29 matches
Mail list logo