
Recherche avancée
Autres articles (53)
-
Participer à sa traduction
10 avril 2011Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
Actuellement MediaSPIP n’est disponible qu’en français et (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir
Sur d’autres sites (8733)
-
libavfilter/scale : Populate ow/oh when using 0 as w/h
14 juin 2017, par Kevin Marklibavfilter/scale : Populate ow/oh when using 0 as w/h
The input width and height is known at parse time so there's no
reason ow/oh should not be usable when using 0 as the width or
height expression.Previously in "scale=0:ow" ow would be set to "0" which works,
conveniently, as "scale=0:0" is perfectly valid input but this breaks
down when you do something like "scale=0:ow/4" which one could
reasonably expect to work as well, but does not as ow is 0 not the
real value.This change handles the 0 case for w/h immediately so the ow/oh
variables work as expected. Consequently, the rest of the code does
not need to handle 0 input. w/h will always be > 0 or < 0.The second explicit (int) cast ensures that ow/oh appear as integers
as a user might expect when dealing with pixel dimensions.Signed-off-by : Kevin Mark <kmark937@gmail.com>
Signed-off-by : Ronald S. Bultje <rsbultje@gmail.com> -
rtpdec : fix issue with conversion from unsigned to signed
20 février 2015, par Gilles Chanteperdrixrtpdec : fix issue with conversion from unsigned to signed
When receiving an RTCP packet, the difference between the last RTCP
timestamp and the base timestamp may be negative. As these timestamps
are of the uint32_t type, the result becomes a large integer. Cast
the difference to int32_t to avoid this issue.The result of this issue is very large start times for RTSP
streams, and difficulty to restart correctly after a pause.Signed-off-by : Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Signed-off-by : Martin Storsjö <martin@martin.st> -
Revert "Disable warnings for casting pointers to integers, there is nothing wrong...
20 novembre 2021, par Andreas RheinhardtRevert "Disable warnings for casting pointers to integers, there is nothing wrong with that."
This reverts commit 5258f64a14713499cf84840b3ab3a1ee7cdcaeb8.
The premise of said commit (that conversions from pointer to int
are ok) is wrong : C99/C11 6.3.2.3 5 : "Any pointer type may be converted
to an integer type. [...] If the result cannot be represented in the
integer type, the behavior is undefined." (C90 6.3.4 contains a similar
restriction.) So don't disable -Wpointer-to-int-cast.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>