Development mailing list

Hi, in these days i've recompiled Lock Workstation: an app which provides a login mask to lock Haiku boxes with a password (and i've also made a modern login mask, only using the magnificient WonderBrush) :-) Screenshot: For security reason, when LockWorkstation is activated, mouse click is disabled and also Team Monitor *should* be disabled, but CTRL ALT CANC when LockWorkstation is activate, will bring Team Monitor window, with ...

2013/5/4 Ingo Weinhold ingo_weinhold@xxxxxx It's ugly anyway, so why not just: indices.AddItem((void*)(long)**index); (addr_t) would be the correct type. Thanks, I used long, will change to addr_t. ...

On 05/04/2013 12:23 PM, Axel Dörfler wrote: On 05/04/2013 11:22 AM, Jérôme Duval wrote: I went ahead with some 64 bit fixes in MediaPlayer and got stuck with this: src/apps/mediaplayer/playlist/ListViews.cpp: In member function 'virtual void DragSortableListView::MessageReceived(BMessage*)': ...

On 05/04/2013 10:08 AM, Jérôme Duval wrote: is it OK to add these macros in SupportDefs.h? /* bigtime_t */ #define B_PRIdBIGTIME B_PRId64 #define B_PRIiBIGTIME B_PRIi64 ...

Hi Jérôme, On 05/04/2013 11:22 AM, Jérôme Duval wrote: I went ahead with some 64 bit fixes in MediaPlayer and got stuck with this: src/apps/mediaplayer/playlist/ListViews.cpp: In member function 'virtual void DragSortableListView::MessageReceived(BMessage*)': src/apps/mediaplayer/playlist/ListViews.cpp:331:28: error: cast to ...

Hi, I went ahead with some 64 bit fixes in MediaPlayer and got stuck with this: src/apps/mediaplayer/playlist/ListViews.cpp: In member function 'virtual void DragSortableListView::MessageReceived(BMessage*)': src/apps/mediaplayer/playlist/ListViews.cpp:331:28: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast] The code tries to add an int32 in a BList: ...

Hi, is it OK to add these macros in SupportDefs.h? /* bigtime_t */ #define B_PRIdBIGTIME B_PRId64 #define B_PRIiBIGTIME B_PRIi64 Bye, Jerome ...

Hi, what happend to the discussion about providing an optional freetype2 package with subpixel rendering enabled? Is anybody actually working on this? What is the status? Cheers, Rossi -- ...

How is it okay? The app is not waiting on user input so a modal dialog is wrong. Maybe excusable because it's supposedly short-lived but this is just not the kind of tradeoff we should be making. Ok, I went with minimal changes and only removed the QuitRequested hack. Instead I added a static method GetWindow in the BAboutWindow class. This will return the existing window, if there is one, or a new window if there is not. This gets us behaviour close to what was there before, allows the window to close, and remove the fAboutWindow field from callers, making their code a ...

On April 29, 2013 at 10:25 PM John Scipione jscipione@xxxxxxxxx wrote: I don't like modal windows much, but I think BAboutWindow falls in the case where it's ok to do that. How is it okay? The app is not waiting on user input so a modal dialog is wrong. Maybe excusable because it's supposedly short-lived but this is just not the kind of tradeoff we should be making. How is it a tradeoff when there is no point at all to keep this window open? Making non-modal about windows is not just wasted effort, it's also completely superfluous. ...

Alexander von Gluck IV wrote: I've finally pinned down some code that can transition into the Mesa3D / Gallium3D projects for Haiku. My plan at the moment is to try and move the winsys code and some of the GL screen initialization code into Mesa. If you have entirely too much time on your hands you can see my progress on the Mesa code here: ...

On Mon, Apr 29, 2013 at 3:03 PM, John Scipione jscipione@xxxxxxxxx wrote: If we can get the benefits of a shallow interface like BAlert without the downsides of modality I say great, but I don't see how that's possible. How does making the window a Singleton work? I understand that a lot of people hate modal windows - but what I find difficult to understand is a desire to bring up an About window and then leave it open while you continue working in the application that launched it. ...

On Mon, Apr 29, 2013 at 4:59 PM, pulkomandy@xxxxxxxxxxxxx wrote: The about window is very close to a BAlert, even if it isn't one anymore. You don't want to keep it open, you don't want it to hide under other windows. Why shouldn't a BAboutWindow be a regular BWindow that you can keep open or hide under other windows? BAlert's suck as about boxes, they're just used because they're easy. The question is, where do we want to put the complexity, in the hands of the BAboutBox class programmer or in the hands of the user? Modal ...

Well, you don't need to keep the about box open while you do other things with the app, so having it modal sounds ok to me. You don't need to use BAlert for modal windows, there's a window flag for that. I don't like modal windows much, but I think BAboutWindow falls in the case where it's ok to do that. How is it okay? The app is not waiting on user input so a modal dialog ...

On Mon, Apr 29, 2013 at 3:16 PM, pulkomandy@xxxxxxxxxxxxx wrote: I really don't want the about box to be modal since that blocks the app, but if you wanted to go that way it would be pretty easy to do using BAlert as a base class instead of BWindow. Making the about box modal blocks the calling app which is less than ideal. Well, you don't need to keep the about box open while you do other things with the app, so having it modal sounds ok to me. You don't need to use BAlert for modal windows, there's a window flag for that. ...

Am 29/04/2013 21:16, schrieb pul