similar to: patch for FXHeaderItem#justification= in FXRuby 1.2

Hi, I was trying to make a horizontal bar plot. The barplot works when the text labels are of reasonable length, but not if some of them are slightly long. I think the long ones get 'squeezed' by default before the plot is flipped and keep the skew after the flip. Is there a way I can get around this? In the code below, plot px looks just fine, but the labels get staggered in plot py.

Hi all, Conrad, MikeS, Silvia, Erik, Illi, John and I have been working on another spec. It's definitely not final, but it should address several issues with the previous one. Please comment: http://wiki.xiph.org/index.php/OggPCM2 Two other issues that remained were: 1) Need for minor version (Silvia and I want it, MikeS is against) 2) Having the header 32-bit aligned vs. making the channel

Hi helpeRs. When I do two-ways tables dimnames in columns are almost left-adjusted: <- factor(rbinom(30,1,.3),labels=c("first","second")) > b <- a > table(a,b) b a first second first 21 0 second 0 9 If I do a oneway table however, dimnames are right-adjusted: table(a) a first second 21 9 Actually I must admit I

Hi all, Can someone tell me how to justify (right or left) the labels on the branches of a dendrogram tree? I have produced a dendrogram via agnes and plotted it with pltree. The dendrogram terminal branch labels seem to be centre-justified by default and I was hoping to change this to left justification. Thanks, Duncan ***************************************** Dr. Duncan Mackay School of

HI all, John Kkoleszar has asked for the option of storing data. He gave the rational that a) SIMD optimized filters b) Writing filter chains. Conrad Parker supported this say that both Core Audio and Jack operate on multiple single channel buffers. On IRC both Jean-Marc and MikeS argued that if OggPCM supports interleaved, the addition of chunked is hard to justify. My slant on the

Greetings all, I'm trying to build a justification case to get the firm I work for to start working with Asterisk more. How could I build this case? The argument I'm raising is that people need phones. PBX systems are too expensive for fewer options and less expansion capabilities. Leveraging Asterisk in the business plan would allow for more consulting revenue and resale

>The old "lock-in" model of the telecom world was nasty and monopolistic and >expensive, but by jove it just worked. >Because as you've seen from this list ANYTHING and EVERYTHING can, and >does, go wrong with this technology. Yes, true, but this is the nature of the beast. It (Asterisk) is an infinitely configurable platform that runs on anything. This essentially

Full_Name: Martin Karl-Friedrich Bader Version: 2.8.0 OS: 10.5.3 Submission from: (NULL) (131.152.1.1) Hi there, when using las=1 on the y-axis the labels keep their centered justification, e.g. if you plot a graph using the axis command: axis(side=2, at=c(0,50, 100, 125), lab=c("0","50","100", " "), las=1), then the 0 and the 50 are centered in relation

Hi Rene, we have discussed the issue of different formats per channel, e.g. different sampling rates. It was not clear whether with PCM sampling of devices this is actually a common (or even used) case. Do you know how multi-channel sound is sampled? Is it created with different widths/rates on different channels? If it is not a common case, we can leave the solution to different streams and

> > The fact that Asterisk is "soft" and you're trying to sell to > an IT Company.. > Just to clarify, we make up the IT company and we'd be selling it to our customers that may or may not be IT based. The company does run VoIP but does not use Asterisk (using VoIP to add additional local lines in different area codes). What I'm trying to accomplish is a

Hello, My IT department has implemented a samba PDC and now we are taking flack for it. Can anyone help me out with some good justifications for doing it this way vs the Microsoft way? Have a meeting about it in a short while... We wanted to do it because Linux is more secure and more stable. But there may be other good reasons and it would be good to know them. Or maybe it would be better

Switch the function documentation to kerneldoc comments, and add WARN_ON_ONCE asserts that the calling thread is a kernel thread and does not have ->mm set (or has ->mm set in the case of unuse_mm). Also give the functions a kthread_ prefix to better document the use case. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h | 4 +--

Switch the function documentation to kerneldoc comments, and add WARN_ON_ONCE asserts that the calling thread is a kernel thread and does not have ->mm set (or has ->mm set in the case of unuse_mm). Also give the functions a kthread_ prefix to better document the use case. Signed-off-by: Christoph Hellwig <hch at lst.de> Acked-by: Felix Kuehling <Felix.Kuehling at amd.com> ---

Hello, There is a new feature ''uninitialized block groups'' in ext4. Block and inode bitmaps in uninitialized block groups are uninitialized. This confuses the converter. The fix is call ext2fs_new_inode for each block group at open time. It set up uninitialized block and inode bitmaps appropriately. This patch also contains some other minor fixes. Thank you, Signed-off-by: Yan

s/drm_dp_get_validated_port_ref/drm_dp_mst_topology_get_port_validated/ s/drm_dp_put_port/drm_dp_mst_topology_put_port/ s/drm_dp_get_validated_mstb_ref/drm_dp_mst_topology_get_mstb_validated/ s/drm_dp_put_mst_branch_device/drm_dp_mst_topology_put_mstb/ This is a much more consistent naming scheme, and will make even more sense once we redesign how the current refcounting scheme here works.

vhost logging uses of vq_err has a few defects and style inconsistencies. o pr_debug already uses pr_fmt so its use in vq_err is defective however no #defines of pr_fmt exist in this code so no actual defects exist o vq_err uses need terminating newlines so add the missing ones o Coalesce formats and realign arguments Signed-off-by: Joe Perches <joe at perches.com> ---

vhost logging uses of vq_err has a few defects and style inconsistencies. o pr_debug already uses pr_fmt so its use in vq_err is defective however no #defines of pr_fmt exist in this code so no actual defects exist o vq_err uses need terminating newlines so add the missing ones o Coalesce formats and realign arguments Signed-off-by: Joe Perches <joe at perches.com> ---

Rather than having to open-code the list of accepted command flags in the unlocked version of each command, we can store that information in the generator to produce the check directly in the public API. --- generator/API.ml | 53 +++++++++++++++++++++++++++++---------------- generator/API.mli | 3 ++- generator/C.ml | 26 +++++++++++++++------- generator/GoLang.ml | 10 ++++-----

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > The current way of handling refcounting in the DP MST helpers is really > > confusing and probably just plain wrong because it's been hacked up many > > times over the years without anyone actually going over the code and > > seeing if things