Development

Ticket #12337 (WebPositive will not load, missing symbol) created

Latest Bugs & Tasks - Thu, 2015-08-27 13:38
  1. Update to hrev49247 daily build
  2. Select Webpositive from Applications menu
  3. Notice error message that says:

Could not open "WebPositive" (Missing
symbol:
_ZNBBSpinnerC1EPKcS1_P8BMessagem).

Categories: Development

Midi: Remove some duplicated code

Source Activity - Thu, 2015-08-27 09:48
Introduced new private read/write_midi_settings() and used them in MidiSettingsView and SoftSynth. Introduced new private read/write_midi_settings() and used them in MidiSettingsView and SoftSynth.
Categories: Development

[haiku] Re: Sequitur (Dan MacDonald)

Haiku Mailing List - Thu, 2015-08-27 05:45
ramps, as a tempo change in a midifile is always a discrete event, but you can get as close as you wish to a desired ramp with a suitable number of tweaks to the graph in the window. -- Pete -- ...
Categories: Development

Ticket #12336 (Volume replicant fails to connect to the system mixer) created

Latest Bugs & Tasks - Thu, 2015-08-27 00:16

Introduced in hrev49584, my Deskbar is unresponsive to clicks and doesn't redraw much of the time. This appears to be related to the Volume replicant asking to connect to the mixer, which gets stuck in a loop timing out in the request. Output when run from Terminal (in endless repetition):

QueryPort: read_port failed, msgcode 0x601, port 396: Operation timed out
BMediaRoster::GetParameterWebFor CONTROLLABLE_GET_PARAMETER_WEB failed
MixerControl: No parameter web
Categories: Development

[haiku] Re: Sequitur (pete . goodeve)

Haiku Mailing List - Wed, 2015-08-26 21:45
On Fri, Aug 14, 2015 at 08:53:32PM +0100, Dan MacDonald wrote: Are there any decent softsynths or samplers for Haiku that could be used with this or does it require MIDI hardware to be used? One of the more uderappreciated features of Haiku [IMO] is that it has by *far* the best MIDI handling scheme of any OS! So, yes, in short, there are quite a few ways to use a SoftSynth. ...
Categories: Development

[haiku-development] Re: [RFC] Getting rid of the tabs in Terminal, using Stack Tile instead (gus knight)

Development mailing list - Wed, 2015-08-26 19:45
On Sun, Jul 26, 2015 at 11:55 AM, Humdinger dmarc-noreply@xxxxxxxxxxxxx wrote: waddlesplash to work on. :) Oh, this isn't on contract time, it's more of scratching a personal itch of mine. -gus ...
Categories: Development

[haiku] Re: Sequitur (Dan MacDonald)

Haiku Mailing List - Wed, 2015-08-26 19:45
Thanks for the links Adrien! I'll try them soon. It'd be great to see Helm and TAL Noizemaker ported to Haiku - both use the JUCE toolkit which would obviously need to be ported first. On Fri, Aug 14, 2015 at 9:23 PM, Gordonjcp gordonjcp@xxxxxxxx wrote: ...
Categories: Development

launch_daemon: Delegate launch data replies to Job.

Source Activity - Wed, 2015-08-26 19:39
Previously the LaunchDaemon would send out its own team id when a given job was not yet launched, leading to invalid BMessengers once the port owner changed to the actually launched team. The launch of the target team and the launch data replies were also not synchronized, which could lead to the launched team getting a reply pointing to the launch_daemon when requesting data for itself. This is the case for the BRoster init of the registrar. The fix in hrev49561 therefore didn't always work, because the registrar would sometimes get the launch_daemon team id instead of the id of itself. It would later try talking to the launch_daemon, which obviously never replied, leading to #12237. The LaunchDaemon now delegates the launch data reply to the Job instead. The Job either replies directly, in case it has already been launched, or queues the reply for when the launch completes. This causes launch data requesters to block until the launch attempt is completed, but won't block the LaunchDaemon message loop. This commit introduces the seperate fLaunchStatus to properly handle the ambiguity of fTeam being < 0, which is the case for both, when no launch was attempted and when the launch failed. This new field now determines what IsLaunched() returns and how launch data replies are handled. The new launch status is additionally protected by the launch status lock, which will later probably be made broader in scope to protect against race conditions once service monitoring is implemented. Previously the LaunchDaemon would send out its own team id when a given job was not yet launched, leading to invalid BMessengers once the port owner changed to the actually launched team. The launch of the target team and the launch data replies were also not synchronized, which could lead to the launched team getting a reply pointing to the launch_daemon when requesting data for itself. This is the case for the BRoster init of the registrar. The fix in hrev49561 therefore didn't always work, because the registrar would sometimes get the launch_daemon team id instead of the id of itself. It would later try talking to the launch_daemon, which obviously never replied, leading to #12237. The LaunchDaemon now delegates the launch data reply to the Job instead. The Job either replies directly, in case it has already been launched, or queues the reply for when the launch completes. This causes launch data requesters to block until the launch attempt is completed, but won't block the LaunchDaemon message loop. This commit introduces the seperate fLaunchStatus to properly handle the ambiguity of fTeam being < 0, which is the case for both, when no launch was attempted and when the launch failed. This new field now determines what IsLaunched() returns and how launch data replies are handled. The new launch status is additionally protected by the launch status lock, which will later probably be made broader in scope to protect against race conditions once service monitoring is implemented.
Categories: Development

BRoster: Apply no-registrar mode in a few more cases.

Source Activity - Wed, 2015-08-26 19:33
Avoids some more attempts at communicating with the registrar if the no-registrar flag has been set. Avoids some more attempts at communicating with the registrar if the no-registrar flag has been set.
Categories: Development

Revert "MediaNode: Wait for 0 time if the absolute timeout is in the past"

Source Activity - Wed, 2015-08-26 18:53
This reverts commit ae9cbf9c4e167470b47964059e90c2b0881367eb. * Thanks to Pawel Dziepak for reporting! This reverts commit ae9cbf9c4e167470b47964059e90c2b0881367eb. * Thanks to Pawel Dziepak for reporting!
Categories: Development

Screen: Rework AlertView to just use BAlert.

Source Activity - Wed, 2015-08-26 18:36
Fixes #12330. Fixes #12330.
Categories: Development
Syndicate content