>> I've opted not to make
>> the intrusive changes (for now) that have little or no benefit to an
>> end user, and probably are in fact detrimental to usability.
>
> How so? The users would not know about what is going on under the
> hood: they would simply open the "main" document, as before. So
>Ah, okay then, but still: if your application *wanted* to be malicious and,
>say, delete the file the user has such selected via file dialog, or maybe even
>at some later point by "security-scoping" that file and only delete it
>"silently" much much later, then the sandbox would not prevent su
2012/10/19 Chris Meyer :
> ...
> My application keeps a main document and a list of linked photos and
> movies that go into the document. The linked files would require me to
> keep around a "security scope" for the files.
I think that is exactly what I meant previously by "document security
scope
2012/10/19 Daniel Price :
>> ...
>> Nothing. Plain and simple. (I am not sure to what APIs you are actually
>> referring to, but let's just assume they existed).
>
> I was referring to the security-scoped URLs.
Ah, okay then, but still: if your application *wanted* to be malicious
and, say, delet
> However I wouldn't know why you wanted to "security-scope" a given
> file if the intention was *not* to place it into the Recent Files
> menu, too - I currently just don't see any other use case than the
> "Recent Files". So why not come up with a QRecentFileMenu (which would
> be a welcomed clas
> (I for my part have still Snow Leopard on my work iMac - Mountain Lion is
> just for toying around on the MacBook Pro. However to be fair Apple corrected
> many issues they completely did wrong in their "Vista"
release of Lion: it is almost as good as Snow Leopard again ;) But I am getting
OT
2012/10/19 Daniel Price :
> I looked into Security Scoped URLs when I was trying to a Qt app in the MAS a
> few months back (which is why I brought it up).
>
> These APIs (or rather the ones relevant to sandboxing - file URLs have been
> around on OSX for years) were only added in the very last v
I looked into Security Scoped URLs when I was trying to a Qt app in the MAS a
few months back (which is why I brought it up).
These APIs (or rather the ones relevant to sandboxing - file URLs have been
around on OSX for years) were only added in the very last version of OSX Lion
(10.7.3 if I re
On Oct 13, 2012, at 9:40 AM, Bo Thorsen wrote:
> Den 12-10-2012 17:11, Thiago Macieira skrev:
>> On sexta-feira, 12 de outubro de 2012 11.47.02, Bo Thorsen wrote:
>>> Hi Carel,
>>>
>>> Den 12-10-2012 10:27, Carel Combrink skrev:
What is the future of Qt Opensource SDK?
>>> One of the Digia
Done: https://bugreports.qt-project.org/browse/QTBUG-27650
Jarno
On Fri, Oct 19, 2012 at 1:14 PM, Samuel Rødal wrote:
> On 10/19/2012 09:44 AM, Jarno Seppänen wrote:
>>
>> I tested on two more machines with Nvidia graphics, can reproduce the
>> flicker on both: Ubuntu 12.10 with Asus GT520 runni
2012/10/18 Michael Jackson :
> ... This is all done with symlinks and does work very well. If someone wants
> to point me to the specific Apple document that says NOT to do this I will
> happily change my code otherwise I'll keep going this route.
Most probably this:
https://developer.apple.com/
On 18/10/2012 15:17, Niels Dekker (Qt interest) wrote:
>> Check the jom package at ftp://ftp.qt.nokia.com/jom/ It also includes ibjom,
>> which allows distribution with Incredibuild.
>
> Again, this looks very interesting. Thanks, Maurice. Would there be any
> significant difference between a Qt D
On 10/19/2012 09:44 AM, Jarno Seppänen wrote:
> I tested on two more machines with Nvidia graphics, can reproduce the
> flicker on both: Ubuntu 12.10 with Asus GT520 running Qt5 beta 1,
> other with Ubuntu 12.04 and Quadro FX 3800 running Qt5 master branch
> from Oct 14th. The previous machines I t
2012/10/19 Daniel Price :
> What's the solution to the file-link issue in Qt? Sandboxing prevents an app
> from reading or writing to any file other than those chosen specifically by a
> user via powerbox (the native dialogs). So if you app has a 'recent file'
> list or some other way to access
I can validate the problem.
For me it happens only(!) during the ColorAnimations.
If I either comment those, or set the RadialGradient visible: false
the "stuttering" is gone.
It's not stuttering with Rectangle
The Qt build is a checkout from this week on 64bit ArchLinux (updated this
week) and
What's the solution to the file-link issue in Qt? Sandboxing prevents an app
from reading or writing to any file other than those chosen specifically by a
user via powerbox (the native dialogs). So if you app has a 'recent file' list
or some other way to access files programmatically, it won't w
I'm not sure I follow you. Are you using soft-links in place of actual
libraries in all but one of the bundles? I'd assumed you were changing
environment variables or something (I've encountered a few apps that do that -
very bad).
But if you have a single directory, with three apps in it that
Hi,
I had a look at the status of Qt 5 on OS X regarding issues with Mac App
Store that were encountered in 4.8. It's looking quite good generally.
File dialog crashes inside a sandbox have been fixed with a patch similar
to the 4.8 one, so Qt 5 apps can run inside a sandbox without issues. Of
co
I tested on two more machines with Nvidia graphics, can reproduce the
flicker on both: Ubuntu 12.10 with Asus GT520 running Qt5 beta 1,
other with Ubuntu 12.04 and Quadro FX 3800 running Qt5 master branch
from Oct 14th. The previous machines I tested with had Intel graphics
(Poulsbo and GMA4500MHD)
On 10/18/2012 09:10 PM, Jarno Seppänen wrote:
> hi,
>
> On Mon, Oct 15, 2012 at 11:29 AM, Samuel Rødal wrote:
>> On 10/12/2012 11:10 PM, Jarno Seppänen wrote:
>>> Hi,
>>> I'm trying out Qt 5.0.0-beta1, but I'm seeing some unexpected
>>> animation flicker. I have a rotating rectangle which starts t
20 matches
Mail list logo
