Mark Waddingham wrote:
> One possibility is that the changes in the way the IDE works in v8
> is causing one of your plugins to do things in a slightly different
> order causing a selected state to be set *after* the tool has been
> changed.
Very helpful - thanks. I'll keep that in mind as I
On 2016-04-13 23:46, Richard Gaskin wrote:
Ali Lloyd wrote:
Not a feature, and I can't reproduce it here. Is it Linux-specific?
Perhaps, haven't tested it elsewhere. It seems to be related to how
one of my plugins works, but it's behaving differently in v8 than
before.
I'll pin down the
Ali Lloyd wrote:
> Not a feature, and I can't reproduce it here. Is it Linux-specific?
Perhaps, haven't tested it elsewhere. It seems to be related to how one
of my plugins works, but it's behaving differently in v8 than before.
I'll pin down the recipe and submit an report.
> On
Not a feature, and I can't reproduce it here. Is it Linux-specific?
On Wed, Apr 13, 2016 at 10:12 PM Paul Dupuis wrote:
> On 4/13/2016 4:13 PM, Richard Gaskin wrote:
> > RECIPE:
> > 1. Make a new stack
> > 2. With the Browse tool active, in the Message Box run:
> >
> >
I'd vote bug.
The name of the property (and its history) implies an object that can be
selected and unselected. It's too much work to have to compare the
property value with the stack name to determine if nothing is selected.
Regards,
Scott Rossi
Creative Director
Tactile Media, UX/UI Design
On 4/13/2016 4:13 PM, Richard Gaskin wrote:
> RECIPE:
> 1. Make a new stack
> 2. With the Browse tool active, in the Message Box run:
>
> put the selObj
>
>
> In versions prior to v8 the selObj is empty, but in v8 it returns the
> name of the stack.
>
> Bug or feature?
>
If it is a "feature",
RECIPE:
1. Make a new stack
2. With the Browse tool active, in the Message Box run:
put the selObj
In versions prior to v8 the selObj is empty, but in v8 it returns the
name of the stack.
Bug or feature?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the