I don't like your single signal design. It's cross platform only in that it
will compile/function on every platform. The application will behave
differently in the slot connected to said signal on mac than on
windows/linux. We should not expect every _user_ app to have separate
codepaths for differ
> This can be either quick-n-dirty
> passing a concatenated string (semicolon separated or whatever) as the path
> value, or getting fancy with passing pointers to structures that may have
> several pieces of info packed in
I'd just add an extra parameter to the signal which is empty for some even
> How will you handle renames? It looks like ReadDirectoryChanges uses
> two separate events, leaving it up to the user to match them up.
>
As for renames (and moves on Linux/X11) we'd need to come up with some mechanism
to sebd 2 pieces of information in one signal. This can be either quick-n-di
> Are you sure about that? The documentation specifies an
> kFSEventStreamEventFlagMustScanSubDirs flag for
> events which indicates that a problem happened either in the kernel or
> user space and events were coalesced.
>
Events being coalesced is another unrelated thing (a feature in fact - not
> Notice how on Mac we get notified on the exact leaf-most folder where the
> event
> happened, and that the event is always just "something changed here".
Are you sure about that? The documentation specifies an
kFSEventStreamEventFlagMustScanSubDirs flag for
events which indicates that a proble
On Saturday 21 July 2012 09:50:25 Sean Harmer wrote:
> On Monday 16 July 2012 20:22:24 Sean Harmer wrote:
> > On 16/07/2012 19:54, gunnar.sle...@nokia.com wrote:
> > > On Jul 16, 2012, at 4:54 PM, ext Sean Harmer wrote:
> > >> On Monday 16 July 2012 07:21:23 Thiago Macieira wrote:
> > >>> On segund
Darn, second attempt to fix my mess-up here in the mailing list only
made things worse.
Shoot me.
-regedit
On Fri, Jul 20, 2012 at 1:21 AM, logic.cpp wrote:
> BH
>
> Hello,
>
> Hope you don't mind my less-waste-your-time more-get-to-the-point English.
> Begin ramble:
>
> Wanted to fix QFileSystem
BH
Hey'all, Thanks for the feedback.
I think we can still make everything work inside one single class, either
QFileSystemWatcher or perhaps a new class if we don't want to break QFSW too
much. We'll do this à la "Graceful Degradation".
Before I explain, consider also the fact that - as Arvid me
Whoops I am so sorry, total noob here when it comes to mailing lists.
This was meant to be a reply to the existing thread
http://lists.qt-project.org/pipermail/development/2012-July/005279.html
The last post of which was by Arvid E. Picciani
Not sure if this means the discussion continues in this
BH
Hey'all, Thanks for the feedback.
I think we can still make everything work inside one single class, either
QFileSystemWatcher or perhaps a new class if we don't want to break QFSW too
much. We'll do this à la "Graceful Degradation".
Before I explain, consider also the fact that - as Arvid me
10 matches
Mail list logo
