Displaying 20 results from an estimated 700 matches similar to: "some (may be related) problems with windows(rescale=) (PR#794)"
2000 Dec 28
0
some (may be related) problems with windows(rescale=) (PR#795)
If these things bother you, could you please supply fixes? For some reason
you omitted the part of the help page dealing with one of these (which is
as documented), and I also think you are confusing `plot' and `device'
sizes. The latter will be the displayed device surface, I believe.
Nothing on the help page suggested that the fine details of the R read-only
parameters will be as you
2001 Jan 10
0
Re: some problems with windows(rescale=) (PR#794)
Part 1) is basically that the initial rescaling is done if the window is
too large to fit on the screen. That's true and obvious (no scrollbars)
and intentional and on the help page. As ever, you need to report bugs on
what is documented, not what you would like.
This will be changed for 1.2.1, but was several hours' work. I have also
cleaned up the scrollbar behaviour.
Part 2) I just
2000 Dec 29
0
Is this a bug? Having cex!=1 before setting par(mai=) gives strange line spacings.
width <- 7
height <- 5
# create whatever device type
# and have cex=1 before setting par(mai=)
windows(width=width, height=height, rescale="R")
oldmai <- par("mai")
par(cex=1)
par(mai=oldmai)
plot.new()
par(usr=c(0,2,0,2))
par(cex=2)
par1 <- par()
text(1,1,"there is hardly anything i know for sure\nneither of the future nor of the past\nnor should i know what
2004 Jan 19
0
rsync 2.6.0 and Solaris 8
Trying to build rsync 2.6.0 on Solaris 8 (gcc 3.3.2) has revealed that
some of the EAI_ defines exist on Solaris, but not all of them. This
causes lib/getaddrinfo.c to fail compilation as EAI_MAX (and some others)
is undefined.
The patch below fixes this issue, but I haven't tested the specific error
conditions represented by the defines.
Bryan
--- lib/addrinfo.h.orig 2001-12-05
2023 Nov 17
1
Can someone please have a look at this query on stackoverflow?
Dear Ashim,
I don't think the aspectratio is appropriate in this context because
it would imply that the beamer (LaTeX) class is used but you're actually
using the article (LaTeX) class.
You may use specifications of the geometry package rather than
specifying options to the class:
e.g. replace your current header:
---
title: "Testing landscape and aspect ratio"
output:
2023 Nov 18
1
Can someone please have a look at this query on stackoverflow?
Dear Olivier,
Many thanks for your reply.
This works well for me.
How did you come up with the pagewidth / pageheight numbers? I do
understand that their ratio = 16:9,
but how did you choose these numbers?
Best Regards,
Ashim
On Fri, Nov 17, 2023 at 9:25?PM Olivier Crouzet
<olivier.crouzet at univ-nantes.fr> wrote:
>
> Dear Ashim,
>
> I don't think the aspectratio is
2023 Nov 18
1
Can someone please have a look at this query on stackoverflow?
Dear Ashim,
these are documented in the LaTeX 'geometry' package (see for example
on CTAN: https://ctan.org/pkg/geometry). As I added in my response on
Stackoverflow, several parts in the RMarkdown header actually concern
information that are processed by LaTeX to actually generate the PDF,
among which the 'geometry' line. For someone who is used to working with
LaTeX, it is
2023 Nov 18
1
Can someone please have a look at this query on stackoverflow?
And indeed again (I did not understand your previous question exactly
at first), the 'hard-coded' definition of a landscape a4 sheet would
therefore be:
paperwidth=29.7cm, paperheight=21cm
Olivier.
On Sat, 18 Nov 2023 13:20:49 +0530
Ashim Kapoor <ashimkapoor at gmail.com> wrote:
> Dear Olivier,
>
> Many thanks for your reply.
>
> Very cool.
>
> You know
2023 Nov 18
2
Can someone please have a look at this query on stackoverflow?
Dear Olivier,
Many thanks for your reply.
Very cool.
You know what I thought ? I thought you had modified the A4 sheet size
to compute the paperheight and paperwidth ?
I wonder if that's another way of proceeding.
Best,
Ashim
On Sat, Nov 18, 2023 at 12:51?PM Olivier Crouzet
<olivier.crouzet at univ-nantes.fr> wrote:
>
> Dear Ashim,
>
> these are documented in the LaTeX
2023 Nov 14
2
Can someone please have a look at this query on stackoverflow?
Dear all,
I have posted a query which has received a response but that is not
working on my computer.
Here is the query:
https://stackoverflow.com/questions/77387434/pdf-from-rmarkdown-landscape-and-aspectratio-169
Can someone please help me ?
Best Regards,
Ashim
2009 Oct 20
10
REXML
Hi,
How to embed ruby code in xml .
here is my XML template :
string = <<EOF
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ozxmlscene>
<ozml version="4.0">
<styleRun style="1091379" offset="0" length="7"/>
<text>The End</text>
<object value="84"/>
<object
2014 Dec 19
2
usbhid-ups on OmniOS (Solaris 10 derivate)
Hi Matej,
I've cc'ed the developers mailing list for now...
thanks for your report. Could you please send in some driver debug traces
(starting it manually, using "usbhid-ups -DDDDD ...")?
That would help in troubleshooting the issue.
thx and cheers,
Arno
2014-12-19 8:48 GMT+01:00 Matej Sekoranja <matej.sekoranja at gmail.com>:
>
> Update: driver is not stable. I
2014 Dec 19
0
usbhid-ups on OmniOS (Solaris 10 derivate)
Arno,
what version of Solaris or libusb required the interrupt pipe hack?
- Charles
On Dec 19, 2014, at 7:00 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote:
> Hi Matej,
>
> I've cc'ed the developers mailing list for now...
>
> thanks for your report. Could you please send in some driver debug traces (starting it manually, using "usbhid-ups -DDDDD
2015 Jul 04
2
Trouble installing xapian on windows
Hello, i am trying to install xapian on windows. As the xapian download page says, there are two options here:
1) mingw
2) a separate set of makefiles for MSVC.
If i understand correctly, MSVC is supported only by xapian 1.2.8 and older, so i decided to try mingw. The configure script worked perfectly, but "make" finished with a error (see the output below). So far i have two
2000 Nov 08
1
Graphics-Device-Size vs. Window-Size
I want to layout on screen a graphic bigger than the screen (width=16.53543,
height=11.69291) but strwidth() and strheight() give wrong results.
> x11(width=42/2.54, height=29.7/2.54, pointsize=12)
> plot(1,1, type="n", xlim=c(0, 1), ylim=c(-1, 0), xlab="", ylab="",
axes=FALSE)
> strwidth("Whatever")
[1] 0.08471151
> # Now resize the window and
2000 Nov 08
1
Graphics-Device-Size vs. Window-Size
I want to layout on screen a graphic bigger than the screen (width=16.53543,
height=11.69291) but strwidth() and strheight() give wrong results.
> x11(width=42/2.54, height=29.7/2.54, pointsize=12)
> plot(1,1, type="n", xlim=c(0, 1), ylim=c(-1, 0), xlab="", ylab="",
axes=FALSE)
> strwidth("Whatever")
[1] 0.08471151
> # Now resize the window and
2007 Jun 20
1
clients and carriage returns
I've recently ported PL/R (R embedded in Postgres as a procedural
language) to work on Win32 -- thank you to all involved for making the
embedded interface common between *nix and Win32!
This of course means users are now creating PL/R functions using Win32
based editors, which are using \r\n for EOL. I had not realized this
before, but R throws a parse error when it sees \r, even on a
2003 Aug 15
0
Re: [R} stars graphs
I thought about that star graph again, and realized that it would be quite
a handy thing for visualizing cyclic data like time or compass direction.
Here is a cleaned up (and renamed) version to do a polar plot that starts
at the right and goes counterclockwise or a 24 hour clock plot that starts
at the top and goes clockwise. There are probably other varieties that
would be interesting.
Jim
2008 Jul 18
1
par("din") vs dev.size()
Hello,
I was messing around with graphics, and noted an odd behavior of par("din"). If
the x11 device is empty, par("din") does not return the correct size
if the device
has been resized manually. dev.size() works correctly.
R version 2.7.1; Fedora 8
# case 1 - empty device
> x11()
> dev.size()
[1] 6.995263 6.994187
> par("din")
[1] 6.995263 6.994187
#
2006 Oct 06
1
glm and plot.effects
Dear R-helpers,
I don't see a difference between the following two plots of effect
objects, which I understand should be different. What am I missing?
require(doBy)
require(effects)
data(budworm)
m1 <- glm(ndead/20 ~ sex + log(dose), data=budworm, weight=ntotal,
family=binomial)
m1.eff <- all.effects(m1)
plot(m1.eff, rescale.axis = FALSE, selection = 2, main = 'rescale =