Here's a few bugs I noticed:

For the desktop (Both Windows and Linux) :

* The behaviour for the Home key when selecting to the beginning of the
line (with shift-home) is not the same as when just using the home key
(smart-home type of thing). It would be nice and consistent if this were
changed.

* Repeating error messages when playing around with WD: sometimes, error
popups will just come back when closed or clicked "ok" with J not
responding to "break" either. I know I'm probably doing things wrong, but
it would be nice if beginners wouldn't have to restart J because of an
error they made writing a GUI. (I'm currently not at my home computer for
giving a concrete example).

For Android

* The "same-game" in Help>Studio>Showcases stopped working on android. It
seems the showcase window stays on top, but the game responds to touches in
the background (eg. when touching where there should be the 1P or 2P, the
menu button appears; the demo quits when I hit the on/off button, ...)

* In the Android jQT, is it possible to allow non-character keys too? I
know the lack an Android compatible text editing is an upstream issue, but
allowing cursor movement with arrow keys, selection with shift-arrows,
ctrl-shift-arrows, home, end, ctrl-c / ctrl-v for copy/paste etc would make
it FAR more usable when using a Bluetooth keyboard (or a software keyboard
allowing these keys, eg. messagEase ).

* Something strange is going on when scrolling with two fingers on Android
: dragging up or down in the terminal scrolls the text in the expected
direction, but once you hit the border of the editable text area, the
scrolling becomes erratic: sometimes changing direction, sometimes jumping
to other locations, sometimes continueing ... I don't really see a pattern.

Thanks for the continued effort to make our favorite language better.

Jan-Pieter

2014-11-04 15:16 GMT+01:00 Eric Iverson <[email protected]>:

> I did the work on the new 803 engine with some help from Bill Lam and
> with assistance from Roger on a few issues.
>
> The main thing was updating the source so that it could be built for
> all official platforms with the latest build tools for those
> platforms. Amazing how many problems evolving platforms and tools can
> introduce. One serious bug in cd for windows 8 64bit was fixed. In
> addition the raspberry pi and andoird builds will now be official
> Jsofware builds.
>
> This was necessary work to provide a new and solid base for moving forward.
>
> When the dust settles this updated source and build tools will be
> released under GPL 3.
>
> There will be a more formal announcement when the release is out of beta.
>
>
> On Mon, Nov 3, 2014 at 4:19 PM, Henry Rich <[email protected]> wrote:
> > Is there a list of the engine bug fixes?  Who is maintaining the engine
> > these days?
> >
> > Henry Rich
> >
> > On 11/3/2014 2:29 PM, chris burke wrote:
> >>
> >> A new 803 beta is available for most platforms. As before, install from
> >> http://www.jsoftware.com/download/j803/install.
> >>
> >> This has updated J binaries, and several fixes and enhancements to JQt.
> >> For
> >> a list of changes see www.jsoftware.com/jwiki/System/ReleaseNotes/J803.
> >>
> >> Please try reinstalling from scratch, thanks.
> >> ----------------------------------------------------------------------
> >> For information about J forums see http://www.jsoftware.com/forums.htm
> >>
> > ----------------------------------------------------------------------
> > For information about J forums see http://www.jsoftware.com/forums.htm
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
>
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to