BookmarkSubscribeRSS Feed

Hi,

I cannot understand why SAS Enterprise Guide 8.3 has lost the RUN command on the context menu in the SAS Code node. 

 

In SAS Enterprise Guide 7.15 and SAS Studio 3.8, the right-mouse click menu in the SAS Code node both contain a Run command, like this:

SAS Enterprise Guide 83 2021-07-03B.pngSAS Enterprise Guide 83 2021-07-03C.png

 

So now we've got all modern and adopted SAS Enterprise Guide 8.3, can we please have our old RUN command back ? I know a group of currently aggrieved users, and one particularly grumpy one, who will be much happier for its return.

 

Cheers,

 

Down Under Dave

New Zealand

8 Comments
Patrick
Opal | Level 21

I definitely miss F3 to just run the code - or selected code portion - in my active program window. I'm still making 'the mistake" to often trying to use it.

I do like very much that I can run a flow from or to a selected node.

DaveShea
Lapis Lazuli | Level 10

Hi Patrick,

I am not sure if I have mistaken what you wrote, but under EG8.3, in a normal SAS Code Node, I can use F3 to run all the code in the current node or, if there is code selected, just that portion.

 

For example, if I hit F3 when I am in the SAS Code node shown below, only the DATA step that is highlighted will get run, resulting in WORK.CLASS getting created. Similarly, if I have hit the "running man" on the top tool-bar, again, only that highlighted DATA step will get run.

DaveShea_0-1625394926600.png

On the Process Flow itself, you can still use F3 to run only the nodes that are selected. In this example screenshot, hitting F3 or the RUN button on the toolbar, causes all three nodes to run in left-to-right reading order, like a book:

DaveShea_2-1625395719538.png

 

However, if I select only two of the nodes on the Process Flow, using Ctrl+Mouse-Click, as in the following screenshot, only those two items will be submitted, but again, in the left-to-right reading order (i.e. [Make SHOES] followed by [Make CLASS]). In this screenshot, we have caught the selected items in mid-flight, [Make SHOES] is currently running (green) and [Make CLASS] (yellow) is queued up and ready to start as soon as [Make SHOES] has finished.

 

DaveShea_3-1625396035546.png

 

 

Please let me know I have missed something here.

 

Cheers,

 

Downunder Dave
New Zealand

Patrick
Opal | Level 21

@DaveShea May be it's just me but when I hit F3 with SAS EG8.3 (well any SAS EG version eight) then instead of executing the SAS code I get below.

Patrick_0-1625397740273.png

 

It you know how to change this behavior so I get F3 back as function key to execute my SAS program then you'd make me rather happy.

 

DaveShea
Lapis Lazuli | Level 10

Ah-ha ! I know what the problem is !

 

I think you are probably working on a laptop device. If so, read on.

 

The physical keys on the laptop keyboard often default to specific laptop operations like sound up/down, microphone on/off, screen brightness etc. They also have their traditional F1, F2, F3 etc. printed on them.

 

To be able to use the F1, F2, F3 operation, you usually have to hold down another key on the keyboard labelled something like "FN" and then press the function key. Thus to get the wonderful F3 operation, hold down FN, and then press F3.

 

Your laptop might have a FN key labelled slightly differently, maybe "func", you should check the manual (remember those ?) if in doubt.

 

On my laptop, because I ALWAYS want to use the F1, F2, F3 operation and almost NEVER use the specific laptop operations, I set the function keys ON by default.

I have a ThinkPad laptop and on that, to make the F1, F2, F3 keys always ON, I held down the FN key and then pressed the ESC key. On my laptop, that made a tiny white LED light up on the ESC key, indicating that the FN was now locked. On my machine, this behaviour hangs around even when you restart the laptop.

 

You should check your laptop's manual, but I am confident you will be able to do the same thing and your lovely F3 and all its friends will be returned to you.

 

Good luck and keep us posted.

 

Downunder Dave.

New Zealand

Patrick
Opal | Level 21

@DaveShea 😀

Worked exactly the same on my new Dell. You definitely made me happy.   ...and sorry "SAS" for blaming you.

BillSawyer
SAS Employee

Hi @DaveShea ,

 

While in a program window, exactly what is it that you don't like about hitting Run or F3?

In EG 8.3 is there a case in which Run/F3 does not accomplish the same goal as right-click Run/Run Selection?

In EG 8.x, if code is selected then Run/F3 will Run Selection....if no code is selected then Run/F3 will run the full program.

Let me know.

 

Regards,

Bill

 

 

PeterHobart
SAS Employee

I work for SAS, and I had exactly the same problem on my new Dell laptop. It looks like the manufacturers have decided we need control of system volume at our fingertips, at the cost of easy access to the function keys. I had to make a change in the system BIOS screen to go back to normal, as I run code more often than I change my system's sound. 

Trying to work out how to use the combinations like [Ctrl] or [Alt] + a function key (like Alt + F4 to close a program) was a real challenge until I flipped the PC to "function-key priority".

 

I'm lucky enough to have local admin rights on my PC. In most companies access to these settings will only be available to the IT department. The only "fix" then might be to attach an external USB keyboard with dedicated function keys.

DaveShea
Lapis Lazuli | Level 10

Hi Bill,

This post got a bit side-tracked with Patrick's question about the F3 key on his laptop.

From an accessibility point of view, being able to use the mouse only to select and then submit some or all of the code in a code node is very important. It smooths the flow of things, and so far as I am concerned, seems very natural; select, submit, click to select the SASLOG, scroll through the SASLOG, all with the mouse.

 

It is curious to me that SAS Studio retains the context menu Run command whilst SAS Enterprise Guide 8.3 has lost it.

 

I cannot see the advantage in removing the Run command from the context menu, it is like removing the Copy/Paste commands and then saying that keyboard Ctrl-C/Ctrl-V are just as good. There would be an uproar if SAS Enterprise Guide did that. I look forward to seeing the return of the Run command on the context menu.

 

Cheers,

 

Downunder Dave
New Zealand