or the alternative of deprecating search paths. Anyone have an opinion here?
> My opinion is to deprecate search paths. That's what QStandardPaths::locate is
> for.
>
>
If this is about QDir::addSearchPath read on:
We use it for embedded projects to easily change asset paths between
developer
On 26/08/2013, at 01.36, Robert Knight wrote:
>> The time has come to focus on UI details, and this is where Qt gives me grey
>> hairs. I started out developing in Qt 4.8, and experienced several issues
>> that didn’t work on the Mac (From the top of my head: Overlays on video
>> widgets), or
On segunda-feira, 26 de agosto de 2013 17:34:33, Samuel Gaist wrote:
> > On segunda-feira, 26 de agosto de 2013 17:14:29, Samuel Gaist wrote:
> >> If I understood the problem correctly, it must be someone that is based
> >> i.e. in Europe and not working for an US company ?
> >
> > It can be someo
> On segunda-feira, 26 de agosto de 2013 17:14:29, Samuel Gaist wrote:
>> If I understood the problem correctly, it must be someone that is based i.e.
>> in Europe and not working for an US company ?
>
> It can be someone in Asia or Africa, Canada, Latin America, Australia too.
> Even Antarctica
On segunda-feira, 26 de agosto de 2013 17:14:29, Samuel Gaist wrote:
> If I understood the problem correctly, it must be someone that is based i.e.
> in Europe and not working for an US company ?
It can be someone in Asia or Africa, Canada, Latin America, Australia too.
Even Antarctica is permitt
On segunda-feira, 26 de agosto de 2013 13:53:38, Kurt Pattyn wrote:
> So, my question is now: should we consider this as a bug, and thus file a
> bug request in Jira, or can we live with it? Note that solving this issue
> could have an effect an QString as well, as it needs to handle those
> non-ch
On 26 août 2013, at 17:10, Thiago Macieira wrote:
> On segunda-feira, 26 de agosto de 2013 12:00:23, Florian Weimer wrote:
>> On 08/14/2013 05:16 PM, Thiago Macieira wrote:
>>> On quarta-feira, 14 de agosto de 2013 09:32:33, Florian Weimer wrote:
> I'm located in the US, so I'm not allowed to
On segunda-feira, 26 de agosto de 2013 12:00:23, Florian Weimer wrote:
> On 08/14/2013 05:16 PM, Thiago Macieira wrote:
> > On quarta-feira, 14 de agosto de 2013 09:32:33, Florian Weimer wrote:
> >>> I'm located in the US, so I'm not allowed to modify the SSL code. If
> >>> you're in the US, you're
--
Kai Köhne, Senior Software Engineer - Digia, Qt
Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius
Sitz der Gesellschaft: Berlin. USt-IdNr: DE 286 306 868
Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
Hi everybody,
this is just a friendly reminder on quality criteria we should pass for
new modules and new features that you'd like to have in the dev branch
(and thus 5.2).
Please make sure that all new functionality
- Compiles on all reference platforms
(If a module/feature is only for
Yay... Thanks so much!
Cheers,
Lars
On 8/26/13 3:28 PM, "Blasche Alexander"
wrote:
>Hi,
>
>All workflow changes have been applied. In addition, QTCREATOR and
>various other smaller projects use the Qt project workflow and issue type
>scheme now. There is no differences between them anymore.
>
>
Hi,
All workflow changes have been applied. In addition, QTCREATOR and various
other smaller projects use the Qt project workflow and issue type scheme now.
There is no differences between them anymore.
If you encounter any issues please let me know.
--
Alex
___
On Monday 26 August 2013 14:39:50 Kurt Pattyn wrote:
> On 26 Aug 2013, at 14:26, Christoph Feck
wrote:
> > What do you mean with "maintained as is"? The document you cite
> > does not mention anything related to invalid UTF-8.
>
> Unicode strictly requires no loss of information when going betwe
On 26/08/13 07:41, Koehne Kai wrote:
>> -Original Message-
>> From: development-bounces+kai.koehne=digia@qt-project.org
>> [...]
>>> For a tracing system to be useful and stand a chance of being adopted
>>> by the libraries used by Qt as well as Qt itself, it shouldn't be part of
>>> Q
On Friday 23 August 2013 08:36:07 Blasche Alexander wrote:
> I looked into the desired workflow changes for Jira (as discussed on this
> list) and am doing some general cleanups [...]
Thank you, thank you. Thank you. Thank you! :)
- Paul
PS,
Thank you very very very much!
_
On 26 Aug 2013, at 14:26, Christoph Feck wrote:
> What do you mean with "maintained as is"? The document you cite does
> not mention anything related to invalid UTF-8.
Unicode strictly requires no loss of information when going between the
different representations.
Currently the QTextCodec c
On Monday 26 August 2013 13:53:38 Kurt Pattyn wrote:
> QTextCodec *codec = QTextCodec::codecForName("UTF-8")
> codec->toUnicode(someUtf8StringContainingNonCharacters, …);
>
> When toUnicode is called with a string containing Unicode
> non-character codes, QTextCodec returns a conversion error.
> [
Hi,
when implementing web sockets, I encountered a problem with the QTextCodec
class.
This is a code snippet:
QTextCodec *codec = QTextCodec::codecForName("UTF-8")
codec->toUnicode(someUtf8StringContainingNonCharacters, …);
When toUnicode is called with a string containing Unicode non-character
On 08/14/2013 05:16 PM, Thiago Macieira wrote:
> On quarta-feira, 14 de agosto de 2013 09:32:33, Florian Weimer wrote:
>>> I'm located in the US, so I'm not allowed to modify the SSL code. If
>>> you're in the US, you're not either. And now here's an interesting
>>> question: are people working for
Hi all,
We have now managed to update qt5.git with fix for QTBUG-31803. Builds are
ongoing and offline packages should be ready today. We will start verification
immediately when packages are available.
http://download.qt-project.org/snapshots/qt/5.1/5.1.1/backups/ will contain
also these same
20 matches
Mail list logo
