On Oct 29, 2013, at 7:58 PM, Calogero Mauceri wrote:
> The Qt documentation states that QDir::currentPath() returns "The
> application working directory". Shouldn't the workind directory be
> initialized with the path the application was launched from?
No, it will be initialized with whateve
Hi!
Dunno if this has been brought up before, but there's also this weird bug
still present in Qt 4.8.5 for Mac OS X:
https://bugreports.qt-project.org/browse/QTBUG-23673
The simple patch I attached to the bug fixes it for me and others... anyway,
it would be great if that got fixed in 4.8.6 :
On 05 Nov 2013, at 17:01, Matt Broadstone wrote:
>
> Cool,
> I've been in touch with the macports patch author and he submitted a number
> of his patches this morning for review. I'm sure they overlap, but perhaps
> there are changes there that could help as well (I haven't reviewed any of
>
On Tue, Nov 5, 2013 at 10:56 AM, Sorvig Morten wrote:
> On 02 Nov 2013, at 17:58, Thiago Macieira
> wrote:
>
> > On quarta-feira, 30 de outubro de 2013 07:29:56, Turunen Tuukka wrote:
> >> We should have the applications made with Qt 4.8.5 on Mac OS 10.7 (for
> >> example) working in 10.9 without
On 02 Nov 2013, at 17:58, Thiago Macieira wrote:
> On quarta-feira, 30 de outubro de 2013 07:29:56, Turunen Tuukka wrote:
>> We should have the applications made with Qt 4.8.5 on Mac OS 10.7 (for
>> example) working in 10.9 without serious issues. And we should be able to
>> agree together what i
On segunda-feira, 4 de novembro de 2013 17:23:55, Oswald Buddenhagen wrote:
> > So one person alone cannot do it. Two can:
> >
>
> but "we" are big enough to be able to do a clean-room implementation,
> don't you think? so the statement that "we" are not allowed to look at
> the patches is simply
On Mon, Nov 04, 2013 at 08:02:47AM -0800, Thiago Macieira wrote:
> On segunda-feira, 4 de novembro de 2013 11:46:35, Oswald Buddenhagen wrote:
> > that's nonsense. any simple patch is not subject to copyright (though
> > it's still good tone to credit the investigator). and anything complex
> > eno
On segunda-feira, 4 de novembro de 2013 11:46:35, Oswald Buddenhagen wrote:
> that's nonsense. any simple patch is not subject to copyright (though
> it's still good tone to credit the investigator). and anything complex
> enough is likely to produce a slightly different patch anyway, even
> after
On Mon, Nov 04, 2013 at 02:20:35PM +0100, Konrad Rosenbaum wrote:
> On Monday 04 November 2013 11:46:35 Oswald Buddenhagen wrote:
> > On Sun, Nov 03, 2013 at 06:49:17AM -0800, Thiago Macieira wrote:
> > > We can't even click the link. If we read their patches, we can't write
> > > the same later.
>
On Mon, Nov 4, 2013 at 8:20 AM, Konrad Rosenbaum wrote:
> On Monday 04 November 2013 11:46:35 Oswald Buddenhagen wrote:
>
> > On Sun, Nov 03, 2013 at 06:49:17AM -0800, Thiago Macieira wrote:
>
> > > We can't even click the link. If we read their patches, we can't write
>
> > > the same later.
>
On Monday 04 November 2013 11:46:35 Oswald Buddenhagen wrote:
> On Sun, Nov 03, 2013 at 06:49:17AM -0800, Thiago Macieira wrote:
> > We can't even click the link. If we read their patches, we can't write
> > the same later.
>
> that's nonsense. any simple patch is not subject to copyright (though
On Sun, Nov 03, 2013 at 06:49:17AM -0800, Thiago Macieira wrote:
> On domingo, 3 de novembro de 2013 09:39:18, Matt Broadstone wrote:
> > I've been loosely following the macports effort to port 4.8.x to Mavericks
> > over here: http://trac.macports.org/ticket/40852. It seems like their
> > changes
On domingo, 3 de novembro de 2013 09:39:18, Matt Broadstone wrote:
> I've been loosely following the macports effort to port 4.8.x to Mavericks
> over here: http://trac.macports.org/ticket/40852. It seems like their
> changes are "working," I can maybe see if I can convince them to push
> upstream
On Sat, Nov 2, 2013 at 12:58 PM, Thiago Macieira
wrote:
> On quarta-feira, 30 de outubro de 2013 07:29:56, Turunen Tuukka wrote:
> > We should have the applications made with Qt 4.8.5 on Mac OS 10.7 (for
> > example) working in 10.9 without serious issues. And we should be able to
> > agree togeth
On domingo, 3 de novembro de 2013 16:24:44, Petko Ditchev wrote:
> On the current note - where can I find 4.8.3 compiled ? In Qt5 I can't
> change layouts in GNOME and in 4.8.5 I can't use shortcuts with
> non-latin letters . The latter is fixed , but not merged , and to build
> my app bug free for
On the current note - where can I find 4.8.3 compiled ? In Qt5 I can't
change layouts in GNOME and in 4.8.5 I can't use shortcuts with
non-latin letters . The latter is fixed , but not merged , and to build
my app bug free for linux I have to get a 4.8.3 or to build 4.8.6 myself .
Petko
___
On quarta-feira, 30 de outubro de 2013 07:29:56, Turunen Tuukka wrote:
> We should have the applications made with Qt 4.8.5 on Mac OS 10.7 (for
> example) working in 10.9 without serious issues. And we should be able to
> agree together what is a serious enough issue to take the risk with 5.2
> get
30.10.2013, 03:58, "Calogero Mauceri" :
> Shouldn't the workind directory be initialized with the path the
> application was launched from?
In Unix-like systems children inherit working directory of parent.
If Finder has "/" as working directory and does not change it
while browsing, working d
On 10/30/2013 8:59 AM, Konrad Rosenbaum wrote:
Hi,
On Wednesday 30 October 2013 00:58:05 Calogero Mauceri wrote:
> The Qt documentation states that QDir::currentPath() returns "The
> application working directory". Shouldn't the workind directory be
> initialized with the path the applicatio
Hi,
On Wednesday 30 October 2013 00:58:05 Calogero Mauceri wrote:
> The Qt documentation states that QDir::currentPath() returns "The
> application working directory". Shouldn't the workind directory be
> initialized with the path the application was launched from? If that's
> not the case, which
On 10/30/2013 1:45 AM, Sandy Martel wrote:
> Le 2013/10/30 à 11:06, Nicolás Alvarez a écrit :
>
>> 2013/10/29 Calogero Mauceri :
...
>>>
>>> The Qt documentation states that QDir::currentPath() returns "The
>>> application working directory". Shouldn't the workind directory be
>>> initialize
On 29.10.2013 17.18, "Thiago Macieira" wrote:
>On quarta-feira, 14 de agosto de 2013 13:15:42, Jonathan Liu wrote:
>> Hi,
>>
>> Are there any plans for a Qt 4.8.6 release in the near future?
>>
>> Qt 4.8.5 was unfortunately released with a critical graphics drawing
>> regression (see QTBUG-315
Le 2013/10/30 à 11:06, Nicolás Alvarez a écrit :
> 2013/10/29 Calogero Mauceri :
>>> ...
>>
>>
>> The Qt documentation states that QDir::currentPath() returns "The
>> application working directory". Shouldn't the workind directory be
>> initialized with the path the application was launched f
2013/10/29 Calogero Mauceri :
> On 10/29/2013 9:01 PM, Sandy Martel wrote:
>> Le 2013/10/30 à 5:24, Thiago Macieira a écrit :
>>
>>> On terça-feira, 29 de outubro de 2013 16:53:55, Calogero Mauceri wrote:
For some reasons QApplication::applicationDirPath() works properly on OS
X 10.9, bu
On 10/29/2013 9:01 PM, Sandy Martel wrote:
> Le 2013/10/30 à 5:24, Thiago Macieira a écrit :
>
>> On terça-feira, 29 de outubro de 2013 16:53:55, Calogero Mauceri wrote:
>>> For some reasons QApplication::applicationDirPath() works properly on OS
>>> X 10.9, but it returns the path to the app exec
Le 2013/10/30 à 5:24, Thiago Macieira a écrit :
> On terça-feira, 29 de outubro de 2013 16:53:55, Calogero Mauceri wrote:
>> For some reasons QApplication::applicationDirPath() works properly on OS
>> X 10.9, but it returns the path to the app executable (the one inside
>> the app bundle). I'm w
On terça-feira, 29 de outubro de 2013 16:53:55, Calogero Mauceri wrote:
> For some reasons QApplication::applicationDirPath() works properly on OS
> X 10.9, but it returns the path to the app executable (the one inside
> the app bundle). I'm wondering whether a similar implementation could
> fix th
On 10/29/2013 4:47 PM, Thiago Macieira wrote:
> On terça-feira, 29 de outubro de 2013 16:35:31, Calogero Mauceri wrote:
>> Related to problems with OS X 10.9, please consider fixing the following
>> bug with QDir::currentPath() returning root dir:
>>
>> https://bugreports.qt-project.org/browse/QTB
On terça-feira, 29 de outubro de 2013 16:35:31, Calogero Mauceri wrote:
> Related to problems with OS X 10.9, please consider fixing the following
> bug with QDir::currentPath() returning root dir:
>
> https://bugreports.qt-project.org/browse/QTBUG-34300
>
> our application is no more running fo
On 10/29/2013 4:18 PM, Thiago Macieira wrote:
> On quarta-feira, 14 de agosto de 2013 13:15:42, Jonathan Liu wrote:
>> Hi,
>>
>> Are there any plans for a Qt 4.8.6 release in the near future?
>>
>> Qt 4.8.5 was unfortunately released with a critical graphics drawing
>> regression (see QTBUG-31579)
On quarta-feira, 14 de agosto de 2013 13:15:42, Jonathan Liu wrote:
> Hi,
>
> Are there any plans for a Qt 4.8.6 release in the near future?
>
> Qt 4.8.5 was unfortunately released with a critical graphics drawing
> regression (see QTBUG-31579) from Qt 4.8.4 which meant that I am
> unable to upda
On quarta-feira, 14 de agosto de 2013 13:15:42, Jonathan Liu wrote:
> Are there any plans for a Qt 4.8.6 release in the near future?
There are no plans to stop releasing 4.8 so far. There are 94 changes post
4.8.5 already, so I'd guess we are releasing. I don't know for how long: we're
going to
32 matches
Mail list logo
