default minimum instead of zero when the user turns on virtual memory. Thanks!
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40056 a95241bf-73f2-0310-859d-f6bbb57e9c96
* apply a patch by hamish (as part of GCI) that lets fseek() discard
characters pushed onto the stream via ungetc()
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40055 a95241bf-73f2-0310-859d-f6bbb57e9c96
When in nondirect mode, SwapBuffers() wasn't respecting the vsync parameter.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40051 a95241bf-73f2-0310-859d-f6bbb57e9c96
in the BSplitView class, related to getting and setting item weights
programatically.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40048 a95241bf-73f2-0310-859d-f6bbb57e9c96
Wrap call to SymbolLookup::Init() in a try/catch block since it could
potentially throw an exception. This was causing the debugger to terminate
in some instances.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40046 a95241bf-73f2-0310-859d-f6bbb57e9c96
Note that the reference to GCC4 Vorbis Tools is also broken but I did not fix
it as there is no GCC4 vorbis Tools package available where all the other
optional packages are.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40043 a95241bf-73f2-0310-859d-f6bbb57e9c96
There is nothing functional yet, I just wanted to try some ideas from the GCI results.
Code is mostly based on Web+ download window, which hapenned to match the mockups pretty well.
Icon is derived from Zumi's work (mix of two different icons)
Icon handling for apps themselves and categories is not done yet, because it depends on how they will be handled by the backend we chose
The install/remove/info buttons don't do anything yet.
Things I'm not sure about :
* What to put in the menu ? Should it replicate the icons at the bottom ?
* How to browse categories ? Is a "go up" button enough ? Should we have a BPopupMenu with all categories in a tree (I don't like menutrees in BPopupMenus...) ? A BOutlineListView would be wasting space... any other idea ?
* Should we keep textual buttons like this, or graphical ones like in the mockup ? Or maybe both ?
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40040 a95241bf-73f2-0310-859d-f6bbb57e9c96
back scrollbar icons and menu markers for example after they got broken when
the offset was introduced.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40019 a95241bf-73f2-0310-859d-f6bbb57e9c96
relevant parts (i.e. removes clipped or out of bounds parts) and does local
scaling in case the view rect is smaller than the bitmap rect. This avoids
sending the full blown bitmaps across when they are in the end scaled to a much
smaller representation. It's nowhere near perfect yet, but it's useable and
improves the network traffic heaviness quite a bit depending on the application.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40014 a95241bf-73f2-0310-859d-f6bbb57e9c96
is used. In my testing this did not seem to be a problem but it doesn't hurt to
fix it.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40012 a95241bf-73f2-0310-859d-f6bbb57e9c96
B_TRANSLATE("???") returns something larger than the size of name.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40011 a95241bf-73f2-0310-859d-f6bbb57e9c96
probably not needed.)
Another problem fixed here is that the border width value is in "border width"
not "border" so this code wasn't really working before.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@40007 a95241bf-73f2-0310-859d-f6bbb57e9c96
