o the point of obscurity. ;-)
(Walter that is only a joke, I'm just teasing you a little bit.)
--
Mark Miesfeld
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't hav
inish' page will have a Create Desktop Icon check box which by
default is unckecked. If the user checks it, a shortcut icon is created on
the Desktop which, if double-clicked, opens up the ooRexx menu folder.
If Rick and David are okay with that, I'll add it to the
and programs. Or all of
> the above.
>
>
I did think about a tutorial, but I was still thinking about starting a
tutorial we wrote and included as an application.
A link to a website is a good idea. Linking to a page that was or include
a list of how to get started thi
>> easily again.
>>
>
That's good, as I first said, I'm not saying we shouldn't add a desktop
icon. But, I'm still not sure what the icon should point to?
--
Mark Miesfeld
--
Rapidly troubl
where installing a desktop icon serves much purpose.
--
Mark Miesfeld
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performa
r.
>
Hmm, if it didn't work that would be a bug and you should open a bug and
we'll fix it. However it works fine for me in 4.2.0. You have to type
"dir" in the code window and then you have to click the Run button. The
p
Yes, whatever is easiest for you David.
--
Mark Miesfeld
On Wed, Dec 11, 2013 at 9:44 AM, Rick McGuire wrote:
> I'd say whatever you find easier, since you're doing the work. SVN allows
> us to recover anything you might delete accidentally and we also have back
> up
Okay, I'm good with that.
--
Mark Miesfeld
On Wed, Dec 11, 2013 at 6:57 AM, Rick McGuire wrote:
> yeah, we can do the back copy on a doc-by-doc basis when the time comes.
> I'm ok with that. I might even try doing a merge first rather than a
> replacement to maintain t
k to trunk and it
wouldn't be any extra pain.
Otherwise, I can branch docs/oodialog and docs/oodguide off somewhere now
and fix up trunk after you've merged the 4.2.0 branch back to trunk.
--
Mark Miesfeld
-
David,
Sounds good to me. I was hoping to, maybe, do the release around Christmas
if things went well. Wrapping things up around Christmas and doing the
release in January is good.
--
Mark Miesfeld
On Tue, Dec 10, 2013 at 8:14 AM, David Ashley wrote:
> All -
>
> I propose modi
David,
I'd also like to see it done. If you will do it great. Putting it off
until after the 4.2.0 release is fine with me though.
--
Mark Miesfeld
On Tue, Dec 10, 2013 at 7:52 AM, Rick McGuire wrote:
> I'm certainly in favor of removing the image versions of these. They ar
release, this is likely, set milestone to none and status
to - I think accepted since you have already have done the coding.
Then remove the code for the 4.2.0 branch, the code will stay in trunk.
--
Mark Miesfeld
On Tue, Dec 10, 2013 at 7:14 AM, Moritz Hoffmann wrote:
> -BEGIN
David,
That strategy makes sense to me. Thanks for clarifying exactly what is
being produced.
By the way, I've put the PDF docs on SourceForge.
--
Mark Miesfeld
On Mon, Dec 9, 2013 at 5:32 PM, David Ashley wrote:
> All -
>
> Since we are into the 4.2.0 beta deeply now I
Rick,
I think when the build is done, it produces a .sgml file. I had thought
that, that file was then transferred to the doc book source files for
producing the error messages.
I think it used to be done that way, and the process was dropped over the
years.
--
Mark Miesfeld
On Mon, Dec 9
s what I did for all the ooDialog doc. Unfortunately, David had
already changed much of the ooDialog doc, so I had to change it back.
One thing is that the newer versions of publican don't emit the warnings
any more unless you ask for them.
--
Mark Miesfeld
--
Of course if you think there is a lot, we could just apply to trunk and
redo the branch when you think you've got them all.
--
Mark Miesfeld
--
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps
. I should have written down
the name, instead I trusted to my memory.
I think it is a file that Rick might have forgotten to check in. Something
similar to stackFrame.ood ??
--
Mark Miesfeld
>
> David Ashley
>
>
>
>
We can fix the first one. Can you open a bug for them. Just put in the
warning text.
hostemu is mostly David's area. He can decide how he wants to handle it.
--
Mark Miesfeld
On Mon, Dec 9, 2013 at 12:46 PM, Perry Werneck wrote:
> Hi,
>
> It´s the only errors for now. Probabl
x27;m not sure that needs
to be changed.
Are those the only 2 warnings produced?
--
Mark Miesfeld
On Mon, Dec 9, 2013 at 11:47 AM, Perry Werneck wrote:
> Hi,
>
> I got a few errors during the validation of the OpenSUSE install package
> for the ooRexx 4.2.0 beta:
>
> [ 189s]
That sounds good David.
--
Mark Miesfeld
On Mon, Dec 9, 2013 at 10:57 AM, David Ashley wrote:
> That sounds like a plan.
>
> I was going to put a zip file on SF that just contained the PDFs. What I
> will do is put up one that does NOT contain the ooDailog doc and let you
> repl
ialog doc, and put the package back up on SourceForge. That
seems easiest.
--
Mark Miesfeld
--
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download
All -
The Open Object Rexx Project is extremely happy to announce the first
ooRexx 4.2.0 beta. The first beta installation packages are available on
SourceForge at:
https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0%20%28beta%29/?
Installer packages are available for a few operating syst
.2.0 directory is created on SourceForge. I'll send out the beta
announcement tomorrow.
--
Mark Miesfeld
> Rick
>
>
> On Sun, Dec 8, 2013 at 6:28 PM, Mark Miesfeld wrote:
>
>> On Sat, Dec 7, 2013 at 2:46 AM, Rick McGuire wrote:
>>
>>>
>>> A be
ot to get this going Rick. I can do the branching tomorrow
evening after we hear from David. Or of course you can do it if you want,
and get to it before tomorrow evening.
As soon as the branch is done I'll set up the directory on SourceForge and
upload the Windows builds.
--
Mark Miesfeld
is one I always try to do. Yesterday I updated a tracker item where I
forgot, thought about it later.
The others I was trying to do, but they didn't seem to work for me, so I
quit. I probably had the syntax slightly off. I'll
00:00:06.102000
Suite construction: 00:00:02.103000
Test execution: 00:04:44.085000
Total time: 00:04:58.793000
--
Mark Miesfeld
--
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps
ails and do some real work.
--
Mark Miesfeld
> Craig Harris
>
>
>
> *From:* Mark Miesfeld [mailto:miesf...@gmail.com]
> *Sent:* Saturday, December 07, 2013 5:18 PM
> *To:* Open Object Rexx Developer Mailing List
> *Subject:* Re: [Oorexx-devel] rexxref updates
>
>
>
omething fixed until the *next* release.
--
Mark Miesfeld
--
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doublecli
ll of NSIS, so it is easier to use the zip file than to do a regular
install of NSIS and add in the extra stuff.
The ooRexx installer itself now detects if it was built using the too short
string max version of NSIS and warns the user if it detects that.
--
Mark Mie
k on Windows. There was a
pre-built Windows build for the release at the version of publican we are
currently using. It will not work for me. And, there have been a lot of
publican versions released since then, but I haven't seen any pre-built
Windows builds with them.
get where you are now.
Since we haven't done a feature release for a long time and there are some
nice new features in trunk now, I'm in favor of not adding any more and
doing a beta / release cycle now. Maybe we can get some users to actually
test the beta over Christmas break.
--
a copy, if
the doc builds. Which it doesn't always.
Link to the main page:
http://build.oorexx.org/
You have to use your Internet skills to drill down and find the most
current build. Hint, follow the downloads links and the most current
of months ago, it looked like the main
thing that needed some work was the title page. But, I couldn't get it to
come out right, so I kept trying and trying, which was what was a lot of
work. It might not be too much work if you can get it to come oka
dly, the newer versions do a better job of the
index, they don't just throw everything in one section.
--
Mark Miesfeld
--
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a s
urrent and
> three previous versions of an OS. There will be some exceptions to this
> rule but those will be exceptions and not the general case. If you have
> a problem with this policy please let me know and we can see about an
> exception.
>
That seems pretty reasonable to me Dav
installer will replace the current ooDialog with
ooDialog 4.2.3.
--
Mark Miesfeld for the ooRexx Development Team
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a c
ALL),
> like I can with Regina, PC/REXX and others?
> >> I Guess NO
>
If he means an actual DOS system, then no. However, many people use that
type of terminology to mean a console window. If that is what he means,
then he can run ooRexx in a console.
--
Mark Miesfeld
--
I'm good with number 2.
Although, I don't have a compelling need to use a digit as the first
character of a class, so any of the options would be fine with me.
3DGlasses is a pretty good name. ;-)
--
Mark Miesfeld
On Sun, Nov 24, 2013 at 8:06 AM, Rick McGuire wrote:
> Ran int
tributes of a root directory, do the following:
- To see files in a root directory, you can use "C:\*" and step through
the directory by using *FindNextFile*.
- To get the attributes of a root director
On Wed, Nov 20, 2013 at 1:49 PM, Rick McGuire wrote:
> I'm not willing to fix 1179 because it will end up making all programs
> compiled with rexxc to need recompiling to run with the new version.
>
That's good, I'd just say don't use so many
57 Arguments
Gives Wrong Result <https://sourceforge.net/p/oorexx/bugs/1179/feed.rss>
#1182 BIFs Do Not Accept Arguments>9
--
Mark Miesfeld
--
Shape the Mobile Experience: Free Subscription
Software experts and dev
Looks good so far Rick.
--
Mark Miesfeld
On Wed, Nov 20, 2013 at 11:37 AM, Rick McGuire wrote:
> Ok, I've gone and marked the RFEs that I believe are already in trunk or I
> would like to implement for the next release as the 4.2.0 Milestone. You
> might want to review the
Rick,
That sounds like a good plan. I was toying around with looking at what it
might take to back port some of the feature requests you had implemented
from trunk to 4.1 fixes from the commit messages. And, it looked difficult
to me.
Your number 3 may indeed be easier.
--
Mark Miesfeld
On
r from:
oorexx.ver
configure.ac
--
Mark Miesfeld
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strateg
On Wed, Nov 20, 2013 at 5:52 AM, Rick McGuire wrote:
> I'm thinking once I get the branch made, we should switch to building the
> 4.2.0 branch at least temporarily.
>
I agree with that. Some people might get in a little early testing that
way.
--
be nice to have those extensions updated with what is in trunk, rather that
what is in 4.1.3.
--
Mark Miesfeld
On Wed, Nov 20, 2013 at 6:07 AM, Mark Miesfeld wrote:
> I thought I did, let me see what I can find.
>
> --
> Mark Miesfeld
>
>
> On Wed, Nov 20, 2013 at 5:42 AM
I thought I did, let me see what I can find.
--
Mark Miesfeld
On Wed, Nov 20, 2013 at 5:42 AM, Rick McGuire wrote:
> Mark,
>
> Have you written down any notes on what files need to be updated when we
> create a new release branch? It's been a while since I've done one.
most in my mind were exactly what you
are suggesting, or to branch off trunk to a "holding" directory like we did
with some of your 4.0 work that you didn't want to lose and branch 4.1.3 to
4.2.0.
I think your proposal is ideal, I'm all for it.
--
Mark Miesfeld
On Wed, Nov 20, 2013
a single type of exception?
>
>
I don't think we need anything new, the native API already has enough to
handle the types of errors you brought up, I think.
--
Mark Miesfeld
--
Shape the Mobile Experience:
Okay, that works great:
/* somePrg.rex */
say 'location='routineTest()
::requires "ooDialog.cls"
C:\work.ooRexx\wc\ooDialog\trunk>somePrg.rex
location=C:\work.ooRexx\wc\ooDialog\trunk\somePrg.rex
Thanks again.
--
Mark Miesfeld
On Sat, Nov 16, 2013 at 2:15 PM, Ric
Thanks Rick
I was looking at something similar to that, but won't the package name be:
Package name=C:\Rexx\ooRexx\ooDialog.cls
where what I really need is:
name=C:\work.ooRexx\wc\ooDialog\trunk\somePrg.rex
I'll code it up and try it though. From a routine would be fine.
--
Mar
* somePrg.rex */
rcFile = .application~srcDir"resources\imageButton.rc"
symbolFile = .application~srcDir"resources\imageButton.h"
...
::method SomeMethod
say .application~srcDir
Any ideas?
--
Mark Miesfeld
-
David,
I saw your commits yesterday and wondered why you were changing the link
flags. So, thanks for the explanation.
--
Mark Miesfeld
On Mon, Nov 11, 2013 at 6:24 AM, David Ashley wrote:
> All -
>
> I created VMs for Ubuntu 13.10 32 and 64 bit ooRexx builds yesterday.
> Dail
On Wed, Nov 6, 2013 at 8:07 AM, Michael Lueck
wrote:
> Greetings Mark,
>
> Mark Miesfeld wrote:
> > Future versions of ooRexx may, or may not, work on that system. All I'm
> saying is that I want to stop claiming that future versions of ooRexx are
> supported on Win
's nothing wrong with that.
ooRexx 4.1.3 should run fine on that system. Future versions of ooRexx
may, or may not, work on that system. All I'm saying is that I want to
stop claiming that future versions of ooRexx are supported on Windows 2000.
--
Mark Miesfeld
>
> Robert
&
moving forward than living in the past.
I think the Unix / Linux version claims are probably out of date also, but
I don't have a good handle on that, so I'll leave updating that area to
some one else if they are
I would not be surprised if 4.1.3 has a dependency on a system API not
available on Windows 2000. But, I would expect a different type of message.
What exactly happens, and what is the exact message you are getting?
--
Mark Miesfeld
On Mon, Nov 4, 2013 at 7:12 PM, Michael Lueck
wrote
t me know and authorise me.
>
You should contact, probably the president of RexxLA and the webmaster, and
arrange to do that.
--
Mark Miesfeld
--
October Webinars: Code for Performance
Free Intel webinars can help you
which, in my opinion,
is no harder to use then the RexxLA links.
--
Mark Miesfeld
-- Forwarded message --
From: Mark Miesfeld
Date: Sun, Jul 7, 2013 at 3:11 PM
Subject: Announce ooRexx 4.1.3 Is Now Available
To: Open Object Rexx Announcements ,
Open Object Rexx Users , ooRexx Dev
but some one who is not real interested in ooRexx. Or, who was
interested but has lost interest or no longer has the time.
--
Mark Miesfeld
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate
Latest there is 4.1.1 ?
>
>
Hi Mike,
I have no way of doing anything with RexxLa sites.
SourceForge is what is hosting the ooRexx. project. It is the only place
that I personally can make sure things are up to date. The latest official
releases are only ava
rse version.
What if you do:
rexx -v
from the command line?
I did send out announcement e-mails for both versions.
--
Mark Miesfeld
--
October Webinars: Code for Performance
Free Intel webinars can help you acce
a
lot of bugs that have since been fixed.
--
Mark Miesfeld
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling,
Oliver,
I put a new ooDialog 4.2.3 (preview) build on SourceForge.
https://sourceforge.net/projects/oorexx/files/ooDialog/4.2.3%20%28preview%29/?
you might want to install that.
--
Mark Miesfeld
--
October Webinars
hy don't you open a bug and include a test program that
causes the crash.
--
Mark Miesfeld
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore ti
>
> I've searched through the ooDialog source code, but cannot find this
> message on a "say" or "printf".
>
> Help!
>
The problem has been fixed, you need a newer build. Which one are you
using?
--
Mark Miesfeld
-
Excellent David. It looks good. Thanks for all the time you put into it.
--
Mark Miesfedl
On Thu, Sep 19, 2013 at 7:02 AM, David Ashley wrote:
> The automated build for the Windows 64bit ooRexx install worked last
> night. It should be available on the Build Machine
> (http://build.oorexx.org
nals - www.sysinternals.com
Process rxapi killed.
C:\bin>
Go to the website listed to get it. The utilities are free.
We could change the build to use pskill instead of killer and just say it
is a condition of building on Windows
hex,
It is possible I'm sure. Not sure how much work it is.
--
Mark Miesfeld
On Tue, Sep 17, 2013 at 9:49 AM, hakan wrote:
> **
> Mark
> Is it with, without any big changes, possible the let the build directory
> (Win32Rel) reflect the bitness of the latest oorexx build
hat it could be is if you are trying to cross-compile.
If you are on a 32-bit Windows and try to cross-compile a 64 bit ooRexx,
it won't work. But since rexximage.exe shows up in the task manager, I
don't think that is the problem.
I would just install the relea
.
This program and the accompanying materials are made available under
the terms of the Common Public License v1.0 which accompanies this
distribution or at
http://www.oorexx.org/license.html
C:\work.ooRexx>
--
Mark
killer.exe bitness with the rxapi bitness.
--
Mark Miesfeld
>
> Thanks everyone,
> David Ashley
>
>
>
> --
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
> 1,500+ ho
#x27;t matter, you could just
tell it to end itself.
--
Mark Miesfeld
--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, S
hex mentioned, you will need to be sure to completely delete the build
directory in between a 32-bit and a 64-bit build.
Or, maybe have 2 VMs one for 32-bit Windows and ooRexx and one for 64-bit
Windows and ooRexx.
--
mix of 32-bit and 64-bit executables.
I'll look at killer and see if I can fix it. But, it's tough getting
around some of the Windows security stuff.
--
Mark Miesfeld
>
> David Ashley
>
> On Tue, 2013-09-17 at 08:08 -0700, Mark Miesfeld wrote:
> > On Tue, Sep 17, 201
look at the killer code again, but it hasn't seemed pressing to
me. I think you can just ignore it for now.
--
Mark Miesfeld
--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of
On Mon, Sep 16, 2013 at 6:02 PM, Mark Miesfeld wrote:
>
>
>> !insertmacro: end of _Else
>> Invalid command: ooRexxProcess::findProcess
>> Error in script "oorexx.nsi" on line 3077 -- aborting creation process
>>
>
>
> I'm pretty sure that me
et/projects/oorexx/files/oorexx-buildutils/1.1.0/?
and download it. It goes in the Plugins directory of your NSIS install.
--
Mark Miesfeld
--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ ho
roblem.
>
I'm not sure what that means "an export" For the permanent fix I just
checked in, you would need to pick up those changes.
--
Mark Miesfeld
--
How ServiceNow helps IT people transform IT d
output
when the error happens. Any lines before the error and if there are any
after. Also what is in the output log, the lines before the log ends.
--
Mark Miesfeld
On Sun, Sep 8, 2013 at 2:04 PM, Mark Miesfeld wrote:
> Hi David,
>
> Sorry, I didn't get a chance to look in
7;ll try
to give you some more input later this week. I won't have Internet access
to the middle of the week though.
--
Mark Miesfeld
On Fri, Sep 6, 2013 at 11:26 AM, David Ashley wrote:
> I got past the killer.exe problem but have run into a new error. When
> the process starts to cre
David, I have very limited Internet aceess, will reply in a day or two.
--
Mark Miesfeld
On Sep 6, 2013 11:27 AM, "David Ashley" wrote:
I got past the killer.exe problem but have run into a new error. When
the process starts to create the oodialog files I get an error before
7.1 is the best one to use at this point. Without a SDK,
there are probably some other things you will find missing. Visual C++ or
Visual Studio will have a version of the SDK with it. But, it is usually
incomplete or out of date.
--
Mark Miesfeld
On Thu, Aug 29, 2013 at 8:02 AM, David As
DATA=C:\Users\Administrator\AppData\Roaming
APPVER=6.1
...
Look at the path to be sure it looks okay. There can be a problem with
VsDevCmd.bat. If there is, the path variable will be screwed up after you
run it.
--
Mark Miesfeld
---
Hi David,
As I remember, this is the same problem you had several years ago when you
first tried to set up the Windows build.
Have you tried running makeorx.bat manually from the command line? Or is
this from a script?
Can you post the exact message you are getting?
--
Mark Miesfeld
On Wed
>
I think that's exactly what you should do. What I usually do is something
like:
touch rexxpgm.pdf
toudh rexxref.pdf
...
which just creates 0 length files of course.
The docs are built daily, it is easy enough to download them separately.
--
Mark Miesfeld
-
Thanks for the heads up David.
--
Mark Miesfeld
On Wed, Jul 10, 2013 at 5:57 AM, David Ashley wrote:
> All -
>
> Due to a UPS failure the ooRexx build machine is currently offline. It
> should be back up tonight after I purchase and install a new UPS.
>
Thanks Ruurd. I'm not sure what the problem was, when I viewed my e-mail
it looked like the links were correct.
--
Mark Miesfeld
On Mon, Jul 8, 2013 at 12:38 AM, Ruurd Idenburg wrote:
> Mark,
>
> think Walter is right in that the other links on the page still points to
> t
/
--
Mark Miesfeld
On Sun, Jul 7, 2013 at 3:11 PM, Mark Miesfeld wrote:
> The Open Object Rexx Development Team is proud to announce the availability
> of ooRexx 4.1.3. This is a bug fix only release, with about 20 bug fixes.
>
> Installation packages for ooRexx are available im
64.exe (18.1
MB)<http://sourceforge.net/projects/oorexx/files/latest/download?source=files>
*
*
*
is a link to a single file. Do not pick that link. Pick the link of the
file you want to download.
--
Mark Miesfeld
On Sun, Jul 7, 2013 at 9:03 PM, Walter Pachl
wrote:
> This gives me***
The Open Object Rexx Development Team is proud to announce the availability
of ooRexx 4.1.3. This is a bug fix only release, with about 20 bug fixes.
Installation packages for ooRexx are available immediately on SourceForge.
You can download ooRexx 4.1.3 from:
http://sourceforge.net/projects/oore
Okay, thanks David.
Have a good time on your vacation.
--
Mark Miesfeld
On Sun, Jul 7, 2013 at 2:43 PM, David Ashley wrote:
> I created all the Linux install files and uploaded them to SourceForge.
> I also uploaded the Linux source file. So I think we are ready to go.
>
> David A
o, I don't think the gtk runtime should be in the installer.
But, what would be nice Perry, would be to include a readme file that
detailed exactly how the user of gtkrexx can install the runtime
themselves.
--
Mark Miesfeld
--
talling everything needed for
gtkrexx or just installing the gtkrexx files would be ideal.
--
Mark Miesfeld
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.
ploaded them to SourceForge.
After you have uploaded the Linux builds, I'll send out the announcement
and delete the 4.1.3 beta directory on SourceForge.
--
Mark Miesfeld
On Wed, Jul 3, 2013 at 8:47 AM, David Ashley wrote:
> I will build the release files this weekend, probably on Sunday. I
knowledgeable about NSIS installers on Windows, so if you submit
an installer for rexxgtk I'm likely to take a close look at it.
Ask questions on this list. "Did anyone see my patch?" seems like a
perfectly valid question to get a conversation going.
--
Mark Miesfeld
-
David,
That sounds good to me. Tomorrow I'll create the ooRexx 4.1.3 folder on
SourceForge but mark it for staging so it is not visible to users. Then
you can put up your files as is convenient for you.
--
Mark Miesfeld
On Wed, Jul 3, 2013 at 8:35 AM, David Ashley wrote:
> If the
Oliver,
Anything in ooDialog trunk is not in the ooRexx 4.1.3 release, which is
just a bug-fix release of the interpreter.
So the work you are currently doing on the User Guide will not be in this
bug-fix release.
--
Mark Miesfeld
On Wed, Jul 3, 2013 at 8:32 AM, Oliver Sims <
olive
The alternative would be to do an official release now before you leave.
I'm comfortable with that because I don't think a second beta will give us
new bugs.
I can go either route.
--
Mark Miesfeld
On Wed, Jul 3, 2013 at 8:10 AM, David Ashley wrote:
> All -
>
> I am going on va
("Each mouse object is associated with a single *underlying *
> window") as meaning "dialog".
> I have to confess that in a burst of misplaced confidence I didn't read
> further than that.
>
101 - 200 of 1904 matches
Mail list logo
