Not sure what the PowerShell thing is, but my install included an Msys bash
shell, which is as straightforward as using git for any Linux shell.
Phil
-----Original Message-----
From: "Arjen Markus" <arjen.mar...@deltares.nl>
Sent: 08/10/2014 08:57
To: "Phil Rosenberg" <philip_rosenb...@yahoo.com>; "Greg Jung"
<gvj...@gmail.com>; "Alan W. Irwin" <ir...@beluga.phys.uvic.ca>
Cc: "plplot-devel@lists.sourceforge.net" <plplot-devel@lists.sourceforge.net>
Subject: RE: [Plplot-devel] Patch: wingcc.c (cursor, window management)
Hi Phil, Greg, Alan,
I have not inspected the implications of the changes Greg proposes yet, but I
will do so, using Alan’s guidelines.
As for Git on Windows, indeed, the installation comes with a powershell thingy
and a GUI that seems to give access to github and nothing else. The GUI is not
a general tool for any repository out there, as far as I can tell.
I use the receipes described in the file README.developers for all my git
stuff, being a non-expert ;).
Regards,
Arjen
From: Phil Rosenberg [mailto:philip_rosenb...@yahoo.com]
Sent: Wednesday, October 08, 2014 9:50 AM
To: Greg Jung; Alan W. Irwin
Cc: plplot-devel@lists.sourceforge.net
Subject: Re: [Plplot-devel] Patch: wingcc.c (cursor, window management)
Hi Greg
In case it helps, I'm a Windows git user. I found the best way to use git was
to use the git bash shell. I think it is included in the Windows install. Or
use Cygwin, to again get access to bash. This way you are doing things just
like most Linux users and as most open source tools have a strong Linux bias it
makes life much simpler.
However, make sure you only use bash for git. Change to the visual studio
command prompt for calling cmake.
Just out of curiosity, I'm surprised you aren't using a cross platform
Windowing library like Qt or wxWidgets. Any reason why not?
Phil
From: Greg Jung
Sent: 08/10/2014 00:14
To: Alan W. Irwin
Cc: plplot-devel@lists.sourceforge.net
Subject: Re: [Plplot-devel] Patch: wingcc.c (cursor, window management)
OK I'll do it one of those ways, I'm back on my computer. I was following the
literal instructions given on the wiki page. The "Git for windows" I downloaded
wasn't easy on windows 8.1; they offer the powershell console and a whitespace
app for the "gui" interface. I've already learned and forgotten enough
powershell buzz to know I didn't want to get any deeper there.
As I look at it again ,
Xwin uses keeps the PLGraphicsIn as a member of {dev}.
in the {dev} structure and copied out to the location provided by the user. So
the cat's out of the bag as far as that goes.
In my way the caller initializes the structure and
passes his option via this structure to the event-handling routine. The device
coordinates
are adjusted to look like X-style orientation (y = Ymax-Y) and a clipping
rectangle is
used to confine the cursor to the window. The returned normal coordinates are
adjusted,
determined by experimentation, so that an "X" plotted at the reported point, in
normal coordinates, lies under the cursor. Generally a re-plot of the reported
position in device coordinates fails.
ls .git
On Tue, Oct 7, 2014 at 11:55 AM, Alan W. Irwin <ir...@beluga.phys.uvic.ca>
wrote:
On 2014-10-07 07:56-0700 Greg Jung wrote:
Hi guys,
I have been working on the _WIN32 incarnation of gnudatalanguage (GDL),
the overall project is in pretty good shape internally - it has most
aspects of IDL pre-2000 implemented. For plotting it uses plplot;
For the others here, GDL
<http://en.wikipedia.org/wiki/GNU_Data_Language> is a free (GPLed) alternative
to IDL. IDL itself is a heavily used (in Astronomy for example) data
analysis language
<http://en.wikipedia.org/wiki/IDL_(programming_language)> so I assume
GDL has lots of users, and I am glad they are getting exposed to
PLplot via that software.
hence
I've got a few lines to wingcc.c that should be useful, and one aspect of
the newer (post-5.10.0) version that I want to argue against. I began to
go through git but today I'm on a different computer and git usage was
hitting
roadblocks so I'm submitting this old-school.
@Greg: your patch does not show your desired change in this regard
(and perhaps other regards as well) because you prepared the patch
against 5.10.0 rather than our latest git master version.
@ Greg: One question I have is what PLplot device does GDL use on the Unix
side? I assume you would want us to minimize struct change
issues in that case as well.
GDL has separated device classes which service the routines as fit for the
specific device. The X cursor routines do not call xwin, I believe.
The changes I made to Wingcc for better functionality:
Added a DestroyWindow() system called to clean up the plstream object
destroyed.
I tried every which way to call this from the GDL code, nothing worked.
Change SetForegroundWindow call to a BringWindowToTop call upon window
creation. That way the user is still typing productively.
Similar maneuvers in GetCursorCmd are made to bring the graphics window to
top but return the input focus. Sleep(2) calls were necessary to get this to
work more reliably.
So here is the patch result of the 'git format-patch origin' command. I know
the
"mode passing" aspect is a bit peculiar to my own usage so I'm not gung-ho to
have it this way if an important usage is needed for the local copy of the gin
structure.
DISCLAIMER: This message is intended exclusively for the addressee(s) and may
contain confidential and privileged information. If you are not the intended
recipient please notify the sender immediately and destroy this message.
Unauthorized use, disclosure or copying of this message is strictly prohibited.
The foundation 'Stichting Deltares', which has its seat at Delft, The
Netherlands, Commercial Registration Number 41146461, is not liable in any way
whatsoever for consequences and/or damages resulting from the improper,
incomplete and untimely dispatch, receipt and/or content of this e-mail. ------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
