I agree with Chris's comments below. It is fine to be able to change values
using control+left/right arrow when in the dialog list, but I've found this
method to be sluggish, plus there are some things that can't be done from
this dialog list. The paradigm of using control+left/right arrow keys can
be kept in place as an option, but if one hits enter one should be brought
to the appropriate track field where one can then interact with it by using
the built-in Sonar keystrokes. When in the track field, changing volume,
for example, can be done either with the left/right brackets (and this is
very responsive) or, if one hits enter, one can edit the value exactly by
entering digits from the keyboard.
So I would like to see the user brought to the appropriate field when
hitting enter.
The problem here is that, when the dialog list is built, it may be picking
up some track fields that aren't visible, thus the scripts have to decide
what to do in this case. Also, I think John has the scripts automatically
go some place and perform a mouse click when hitting enter on some items in
the list. If custom actions have to be assigned for every item in the
dialog list, then the method of automatically grabbing elements to populate
the list won't work and special code would have to be made for each element.
So it all depends on the structural approach to the scripts that the
developer wants to take. There are many ways of coding to perform the same
job. Getting the control surface code to work certainly offers other
opportunities and choices. But in the end analysis, it's a design choice.
I've spent almost more time thinking about the structure of a program than
actually coding for some large projects I've done in the past. That is
often time well spent because one will build in the hooks to that make it
perhaps easier to maintain code, add functionality at a later date, improve
efficiency, etc. In my early days of coding I used to think that flow
charts were a waste of time. But they can often help avoid many problems
down the road.
--pete
-----Original Message-----
From: sonarblindbeta-bounce@xxxxxxxxxxxxx
[mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Belle
Sent: Wednesday, May 06, 2015 1:15 PM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Re: sonar blind keep waiting for the next release
Ok folks, just was taking a good jog around the tracks list nad the
children of such.
Now here's something to think about for the master programmer.
This is just my thought, tell me if you agree or disagree.
I think if you try and script a custom overlay to handle all the types
of controls you're going to get in to since you're dealing with edit
fields, and sliders and drop down menus, for instance I think the bank
and patch are like that.
when I tried to change values for the patch column, it didn't work at
all with the control and arrow keys.
I think the first letter navigation to get there quickly is the main
important thing that needs to happen here, but let the user drop out to
the native sonar ui and do stuff to the control he wants to jump to.
that makes sense to me.
and if I were scripting this, which thank god I'm not, ha ha,
that's what I'd do make the navigation keys to get there fast, but don't
re-do what's already there and handy already,
we have nice value adjustment keys with brackets and plus and minus on
top row, and haven't checked yet, but probably number pad works too I bet.
and remember, we talked about all the stuff in the applications key
menus, the automation control,s nad for binding a real midi controler or
control surface, and snap shot automation and all the rest of it.
so to me, getting there and dropping me out accurately is the biggy.
Because I want native control to the ui on these control which are valid
anyplace, the inspector,
the track view, any place sonar has the ability to do keyboard access to
the ui, so why not just let that happen and just get me there quickly.
Now if you can implement changing values, that's fine, but ct does this
to the actual control, not while you are in a special over-lay.
so that doesn't get in the way but if you wanted to say do an automation
snap shot after making a volume change, that means dropping out of the
control shift f11 menu,
making your change going in to the applications menu and hitting the
snapshot item, then going back in to the overlay menu.
that's not efficient.
Would rather have keys available to do the value changes right when I'm
on the control, and can see it's value, and sonar already has some good
keys assigned.
So what do you guys think,
do we need to try and deal with the controls in the overlay itself, or
would you rather see just getting to the control you want fast and
dropping us off there like a super duper escalator that goes in every
direction 'grin'?
On 5/6/2015 11:50 AM, Chris Belle wrote:
Could we get a quick list of the hot keys for the scripts in one place?
Let's see,
control shift f12 for tracks list.
hit once just says tracks list.
Hit twice brings it up.
Control-shift-f11 for the children of the tracks list, fields and such.
Allows first letter nav to volume and pan and all the usual stuff for
track fielcds, is supposed to dump you out to said field when you hit
enter, but doesn't on mine, for what ever reason.
Control shift o for a bunch of menus and such, a hodge podge of things.
In native sonar mode insert h brings up the track manager, but for the
jaws scripts insert h is a bunch of short cuts.
There was something mentioned about a s menu and a t menu but they
don't work for me.
Anything else I should know about?
On 5/6/2015 5:21 AM, Rishi D Mack wrote:
chris, if you're on a track, press ctrl+shift+f11 to bring up the
children for that track.
-----Original Message----- From: Chris Belle
Sent: Sunday, May 03, 2015 10:30 PM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Re: sonar blind keep waiting for the next
release
Well, I got the track list with so many children, but when I arrow right
or left it kicks me back to the regular tracks grid.
On another note, was following along with John's demo and the sends menu
does work, that's nice.
But to access the clips pane, that does not work for me.
When I do control shift l, I get a search thing for ocr or graphics.
I don't get what he gets on the recording.
But at least some of the stuff is working, and being able to use first
letter nav in the tracks list is cool.
to get to different tracks.
On 5/3/2015 8:40 PM, Pradip Chandra Sikdar wrote:
I think, you are in the tracks grid. In that case, press [ ] keys.
If you press control+f12 twice to get the tracks list then, press
control+arrow keys to change values.
On 4 May 2015 6:47:52 am Chris Belle <chrisbelle@xxxxxxxxxxxx> wrote:
Ok more strangeness.but it
I got the tracks list to light up finally for a while in jaws.
Now when I use the control and arrow keys to change volume or pan and
such it moves by one increment value, like going from 127 to 126
says no children, no objects so it's trying to do something else, butever
it's looping back around to do the pan function or volume, or what
it's own.track
On 5/3/2015 8:11 PM, Chris Belle wrote:
Now this is strange.
When ever I fire up jaws, I get some sort of window that says
something like hud fb and nothing will read.
I can fire up window-eyes and dismiss the window and get basic
jaws, butnavigation, I've gotten things to light up a few times with
blindnone of the keys work as expected,
not alt 1 not control shift f12 for tracks list, it is weird.
I have got the resolution set right, I actually had it bigger but I
put it at 1280 by 1024
I know the scripts are loaded because I do insert q and get the
offsonar deal, so go figure.
but with window-eyes everything lights up.
Well, as much as it can, you know what i mean.
On 5/3/2015 7:44 PM, Chris Belle wrote:
Your our hero John.
On 5/3/2015 3:53 PM, John Martyn DoItBlind wrote:
I have a lot fixed in this next revision, just not ready to send
the new stuff.
John
