Development

Hi Humdinger, On Mon, May 18, 2015 at 9:47 AM, Humdinger humdingerb@xxxxxxxxxxxxxx wrote: As you said, this idea to hide the scrollbar seems to come from touch-devices, or at least became popular with those. On a mouse operated desktop system however, you generally want/need to see what you want to click. ...

MemoryView: - During edit mode, if navigating with the left or right arrow only resulted adjusting the focus nybble and not transitioning to another block, redraw wouldn't be triggered, leading to it appearing as if the keypress had no effect. MemoryView: - During edit mode, if navigating with the left or right arrow only resulted adjusting the focus nybble and not transitioning to another block, redraw wouldn't be triggered, leading to it appearing as if the keypress had no effect.

On 26/04/2015 00:31, Chris Hanson wrote: CPUs, or just Intel CPUs? Some cursory searches haven’t provided a direct answer. I’m mostly interested because it would also mean it should be possible to cross-compile… (Compiling anything on a 66 MHz BeBox feels pretty slow these days.) No, BeOS on PPC didn't even use the ELF format. ...

264 MB

265 MB

266 MB

I does not know if this bug is new, but every time then i start up may Haiku, my folder options are default, not user settings enymore.

hrev 49162

- Remove out-of-place accessor to type lookup info on ValueLoader. Instead, adjust CreateChildren() and CreateChildrenInRange() to take a TeamTypeInformation parameter. This can then be used by value nodes that need to be able to look up type information in order to properly publish their children, such as BList and BMessage. Refactor subclasses and callers accordingly - Remove out-of-place accessor to type lookup info on ValueLoader. Instead, adjust CreateChildren() and CreateChildrenInRange() to take a TeamTypeInformation parameter. This can then be used by value nodes that need to be able to look up type information in order to properly publish their children, such as BList and BMessage. Refactor subclasses and callers accordingly

fixed:

Fixed in hrev49251.

* Fixes #8675. * Fixes #8675.

On 18 May 2015 at 09:15, fox noodles foxnoodles@xxxxxxxxx wrote: Apparently this is a matter of taste and what you're used (and how the OSs behave you use besides Haiku). So it should definitely be an optional thing. As you said, this idea to hide the scrollbar seems to come from touch-devices, or at least became popular with those. On a mouse operated desktop system however, you generally want/need to see what you want to click. ...

Why Haiku using old-old autoconf and libtool in the buildtools ( ​https://git.haiku-os.org/buildtools )? I does not mean the "legacy" folder!

• Our autoconf is 2.61, but the latest version is 2.69 (it is a 6 years long span between the two version)
• Our libtool is 1.5.2, while the latest is 2.4.6 (almost 10 years long span)
• Our isl is 1 year old.

I swapped these softwares to the latest version, and tried to make a test build on OSX, but i got some errors at configuring binutils (i have no problem with the original in-tree version). So it seems, there is some not-upstreamed Haiku specific patches and mods in these softwares. IT would be great to upstream these changes (if any), and update the in-tree softwares to the latest version.

fixed:

Applied in hrev49249.

TableCell{Bool,Enumeration}Editor: - OptionPopUp-derived editors for their respective value types. TableCellIntegerEditor: - TextControl-derived editor for integer values that validates inputs based on the target integer size and type. Not actually used yet, but together with the previous changes, these lay the groundwork for the remaining part of #9708. TableCell{Bool,Enumeration}Editor: - OptionPopUp-derived editors for their respective value types. TableCellIntegerEditor: - TextControl-derived editor for integer values that validates inputs based on the target integer size and type. Not actually used yet, but together with the previous changes, these lay the groundwork for the remaining part of #9708.

264 MB

265 MB

266 MB

- Introduce interface class ValueFormatter. This one takes on the responsibilities of formatting a value into a string, which were previously embedded within the various TableCellValueRenderer subclasses. - Add implementing subclasses for the various value types. - Introduce TableCellValueRenderer subclass TableCellFormattedValueRenderer. This is a simple TableCellValueRenderer implementation for the simple case of a renderer that does nothing more than use a formatter to present a string version of its corresponding Value. Since this describes all existing renderers, this renders them obsolete. - Refactor the respective ValueHandler subclasses to make use of the formatters and new rendererer subclass. - Introduce interface class ValueFormatter. This one takes on the responsibilities of formatting a value into a string, which were previously embedded within the various TableCellValueRenderer subclasses. - Add implementing subclasses for the various value types. - Introduce TableCellValueRenderer subclass TableCellFormattedValueRenderer. This is a simple TableCellValueRenderer implementation for the simple case of a renderer that does nothing more than use a formatter to present a string version of its corresponding Value. Since this describes all existing renderers, this renders them obsolete. - Refactor the respective ValueHandler subclasses to make use of the formatters and new rendererer subclass.

Does Haiku maintain binary compatibility with BeOS R5 for PowerPC CPUs, or just Intel CPUs? Some cursory searches haven’t provided a direct answer. I’m mostly interested because it would also mean it should be possible to cross-compile… (Compiling anything on a 66 MHz BeBox feels pretty slow these days.) -- Chris ...