Logic Control and LP8

Hi,
I'm surprised at the lack of outrage over the terrible state of the Logic Control unit implementation in Logic Pro . With earlier versions of Logic I found using the LC unit a delight, recording and mixing several projects with it. Now (8.0.1) it's simply not worth using. I've tried all I know . . . rebuild defaults, trash preferences, re-install the unit, build a new autoload template (even Logic's templates don't work any better in this respect). Global mode doesn't work and track selection is a problem in any mode. One exception: if you're content with using the up/down arrows on the LC for track selection it works better . . . even in Global mode . . . it will actually put a track into Record and not mention the dreaded "Automation Folder"! Apple has stated that the unit is "behaving as expected". Mackie advised me to check for double .cs preference files(there weren't). Nobody said "Oh yeah . . . it's a problem". Either the issue isn't as widespread as I imagine or the relevant companies are not aware of the problem. This unit wasn't cheap. I paid $1764.00 Canadian when I bought it. It was worth every penny at the time, but now it looks more like a non-usable piece of metal that cost over three times more than the software (LP8) that appears to be crippling it.
What gives?
RW

Yep, I'm amazed at how broken it is in LP8, both major and minor issues. It's like nobody tested the MCU when they'd reworking the GUI and other stuff for LP8.
I've certainly reported this as a bug, so it's not like they aren't aware of it. I really hope they are tackling all this stuff (as well as all the other stuff) for an update soon...

Similar Messages

Logic Control W/ LP8

Any one have issues with a Logic Control surface with the new LP8?

There have been a few issues since version 8, some of which have been rectified with the 8.0.2 update.
Some that remain are;
• Save LED doesn't go out after save
• Some on screen alerts cannot be responded to via the controller
There are a few others but overall it is working well for most people.
Make sure you don't have a corrupt preference file for the control surfaces. In my experience, this preference file is even more sensitive than the main logic preference file. Ditch it and rebuild.. It's a pain if you have many custom features set up, but is necessary to get things going again.
Once you have a set of logic preferences that are working well, copy the two files to the desktop and select them both, then right click and create archive... Then you'll have a pair of 'good' files that you can drop into the prefs folder when things go crazy again.
After a crash, you will want to drop the fresh ones in there.... as a crash always seems to corrupt the prefs files in my experience.
MacHD / Users / 'your account'/ Library / Preferences / (in here you look for, "com.apple.logic.pro.cs" for controllers
"com.apple.logic.pro.plist" for the app

L8 is seeing my Axiom as a Logic Control and it's wreaking havoc!

A new twist on all the control surface issues - I have a M-Audio Axiom 25 connected via USB and it's not setup in anyway as a control surface via the control surfaces preferences. I have never used it as such and never need to because I own a Logic Control.
All of the sudden, L8 is recognizing midi note input from the M-Audio as LC input - i.e. if I press an A3 it doesn't sound a midi note, but rather performs a specific Logic Control function as defined in the Key Command Preferences.
Of course, it's even worse because I have an Apogee Ensemble so Logic doesn't even recognize a potential Control Surface unless everything is powered up in just such a perfect way.
So I have a Logic Control that isn't recognized, and an Axiom 25 that is recognized as something it's not and if I go to Control Surfaces preferences, it's as if the world of cotrollers doesn't even exist because the master list of options is gone baby gone.
Anyone find a workaround for this?

totally different ports!
The LC is connected via my AMT8 - the Axiom is on it's own port via USB, so that shouldn't be issue.
I've tried cabling the Axiom port directly from the input object to a monitor and then terminating the connection just so I can see what it's transmitting - the "bad" notes don't show up as anything in the monitor and even though I've broken the Sum cable from the input object and the Axiom port is only cabled to a monitor and nothing else (the Sequencer input is not connected to anything at all!), L8 is receiving those key presses as LC commands.
So strange

Logic Control and Logic Pro 9.1.0

I'm running Logic Pro 9.1.1 and Logic Control V1.02 which makes it mackie control.
Today i set it up with Logic and noticed a few things:
1. The level reading on the Logic Control's display is choppy...meaning if i raise a fader really slowly the display levels also rise slowly synced with on the onscreen faders. However if i move the faders a bit faster, the Logic Control display reading is very choppy--it always settles at the right level, but the changes are jumpy. Is this usual ? This was not the case with Logic 7.
2. A few times the locator bar jumped forward missing beats, as if stop/play were pressed repeatedly. I rebuilt defaults and now it seems to be working fine, This used to happen to me in Logic Pro 7 as well, maybe its a fault with my controller. Anyone ever experience this ?
Thanks
Faisal

Cowbell, my experience has been different.
I tried the Logic Control mode but things were really wierd, some buttons not working, then the whole control lost contact with logic till i re-launched.
The Scroll bar jumping thing was happening a lot more often.
Then i deleted LC, trashed preferences and re-booted in Mackie Control mode.
Still strangeness and i went did the check TOUCHLESS FADER thing and all is working fine now which is WEIRD!!!!!! I think i may have a defect in the jog wheel/transport section but its all working fine for now.
I'll give it a few days.
Thanks !!

Keystation Pro 88 (or other controller) as the Logic Control

Has anybody got their setup like this? I've been trying to get this to work for the past 6 hours and no luck. Can someone please help me? Just bought Studio 2 days ago and haven't touched it yet cuz I can't get the keyboard to fully work.
Joined: 17 Jan 2006
Posts: 55
Location: Los Angeles
Posted: Sun Jul 15, 2007 12:03 am Post subject: Keystation Pro 88 (or other controller) as the Logic Control
I'm sure some of you already know how to do this. I just figured I'd write this up at some point to share with others. The basic idea is to use the Keystaion Pro 88 (or some other MIDI Controller) as an actual Control Surface, or in this case the Logic Control, to have more freedom with the MIDI Controller, i.e. using the group of 8 faders (on the Keystation) to control Volume for tracks 1-8 in the arrange window, and then hitting Bank Right to automatically control tracks 9-16, and as a result making a universal controller not bound by specific channel messages, or MIDI CC Volume messages etc... in short the essence of any Control Surface.
What I'm describing below is what this app will also do: http://www.opuslocus.com/lcxmu/index.php
I basically just wanted to avoid using a separate application all together. Keep in mind that the app does simplify the whole process, but Logic inherently can do pretty much everything the app does.
I recommend reading this in its entirety before attempting.
KeyStation Pro 88 as Logic Control
Part One: Add Logic Control as Control Surface
1. Open Logic.
2. Preferences / Control Surfaces / Setup...
3. New / Install / Select your preferred device (in my case Logic Control
4. Click the icon in the setup window for the Logic Control.
5. On the left hand side under "Logic Control" you should see an "Out Port:" and "Input:" ... select the desired MIDI in/out through which your device is connected.
6. Open Preferences / Control Surfaces / Controller Assignments. Make sure you select the "EXPERT VIEW" check box.
7. You should now see a bunch of different Zones in the Zone column, one of which is "Control Surface: Logic Control"
8. Create your own Zone, KeyStation Pro 88 (or whatever) using the Plus sign in the bottom left corner of the Controller Assignments window.
9. Now basically go through the existing parameters already available in the Logic Control Zones, Select what you want. You can select entire Modes or individual Controls / Parameters. You can select multiple values (only multiple Control / Parameters NOT modes) by selecting and dragging or simply with select and holding command.
10. Command-C the selected Modes and then click back onto you user zone that you created above.
11. Click inside the Mode column (or Control / Parameter column depending upon what you selected and copied from the Logic Control zones).
12. Command-V to paste the Modes into your user Zone.
13. Do this for as many Modes / Controls you want, that your specific MIDI controller interface will be able to handle.
Part Two: Assigning Input Values
1. Open Preferences / Control Surfaces / Controller Assignments
2. Now for each parameter that you copied, you will need to set the input MIDI value from your controller.
3. Click on your User Zone, then Mode, then the first parameter in the 3rd column.
4. You should see a "MIDI Input" option (this should already be set correctly as long as you set it earlier in Step 5 of Part One). If it's not set to the correct MIDI input (which I found to be the case sometimes even after Step 5), then change that here.
5. Next to "Value Change:" you will see a box with MIDI data in it. Delete the existing date by highlight and delete.
6. Activate "Learn Mode" (bottom right corner of Controller Assignments window) then click within the "Value Change" box, then move the corresponding fader, button etc. The "Value Change" should now show the MIDI data value for that fader. Be careful here, there should only be 3 groups of 2 for data here... if you see 2 groups, of 3 groups, of 2 then typically the FIRST group of 3 should be the value you want here. You can always delete the data, and move the fader again to be sure. The reason for the 2 groups of 3 is not in error: some buttons send TWO MIDI values, one on press and one on release. You can use this to your advantage and assign TWO different functions to these buttons, thus the first (press hold) value can do one thing and the second (release) value can do another. You can also change the MIDI controller to only send 1 message on press and nothing on release, or simply make sure that only the on value is present in the "Value Change" box.
7. You'll have to do this for all the different knobs / faders etc. on your MIDI controller. There are many shortcuts of course. You can manually type in the Values if you know them. For the Keystation Pro, M-Audio has an app called Enigma that I recommend for changing controller parameters and much more on the Keystation. You can use this app to assign all the actual control data that each button or fader sends to the sequencer, once you know the values you can convert that data to the MIDI data values and enter them into the Value Change box.
8. Once you're done assigning values to the controllers, you can delete all the Zones except for the user Zone you created earlier. Before you do this, it's a good idea to back up the Control Surface preference file just in case you ever want to grab something else from the Logic Control Zones. You could always add a second Logic Control and copy the Zone from that, but you'd have to reassign all the MIDI Input: values ... short version, just back up the preference file before you delete the Zones. The reason why you want to delete the Zones that you're not using is simply because if you have a controller that happens to send out MIDI data to the sequencer, and the actual Logic Control happens to have that MIDI data value already inherent it it's Zones, then you could be asking for trouble, simply put you'd be sending MIDI data to change Volume and the Logic Control maybe has that MIDI Data Value already assigned to Pan for the existing track.
The file to backup is located here: ~Users/username/Library/Preferences/Logic/com.apple.logic.pro.cs
As a precaution I have always backed up my Logic Preference file WITH this .cs file. Technically it's not necessary... for instance: Let's say you trash your preferences and open Logic to find that the Logic Control is missing from the Control Surfaces Setup. So you add it back and now you find out that Logic is missing the User Zone that you created. If you close Logic and copy the .cs file back to the directory above, then upon reopening Logic you should find your User Zone is in place again. But I've had mixed results with that, so just in case I copy over the preference file with the .cs file as a pair. It seems that the Logic pref file only contains information that the Logic Control is a Control Surface on your system and the .cs file is the preferences for that specific Surface.
Another note: after a recent Logic update, maybe 7.2? ... it was whichever update added support for more Control Surfaces, I can't remember. This update basically erased all the hours of hard work linking the Keystation to Logic as the Logic Control. This only happened with this specific Control Surface update, but not with 7.2.3, probably simply because they didn't make any changes to the .cs pref file.
Anyhow, when this happens again in the future, there seems to be a quick fix. I take NO responsibility for you somehow crashing Logic on a continual basis after applying the fix. Personally I have seen NO issues by doing this at all. I simply copied a version of the .cs file with the new update missing the Keystation Zone, as well as a version of the .cs file WITH the Keystation Zone, to a PC (I think it was a PC, don't believe I tried it with textedit, although should work as well). I opened both of the files in notepad and compared them. I noticed the word Keystation towards the bottom and realized that most all the data (gibberish) was exactly the same up until a point in which the file with the Keystation data had a group that was absent from the new .cs pref file from the new update. So I basically copied the data from the old .cs pref file, pasted it into the new .cs pref file, saved it and open Logic. Logic warned me that a pref file was corrupt or something of that nature, but loaded fine anyway, and the Keystation Zone was back in Controller Assignments.
One last thing... the problem that some of you may run into is that by making your MIDI controller a Control Surface, or turning your Keystation Pro into a Logic Control, limits some of the functionality of the MIDI Controller. For instance, a Logic Control's main purpose is to control different faders, knobs and what not of MANY different tracks. When you move a fader for volume on the Logic control, it will move the fader corresponding to the selected track... it's not programed to say change the actual midi CC 7 for Volume, only the actual Fader. Thus, what if you want the MOD wheel to still control modulation and you want the sustatin pedal to continue to act as a sustain pedal. Well, if Logic sees that Port 1 is the input for the Logic Control, but in reality the Keystation, then it's only going to allow specific events through. The way around this issue is by using both the input options that the Keystation has... hook the MIDI out into Logic and use the USB port as well. I run the Keystation as a Logic Control through the USB port, and use the MIDI out for actual MIDI data. But the catch is you have to make sure you only connect the MIDI Port into Logic's sequencer in the environment. Thus open the environment, open Clicks & Ports, Port 1 and Port 2 are the IN/OUT for the USB port. Midi Port is the Keystation's MIDI port. Select and delete the cable for the SUM, and run individual cables for the ports you want to use. Thus, all your other MIDI interface Ports, the Caps Lock keyboard etc. Just be sure that if your using Port 1 (USB Port Out from Keystation) for the fake Logic Control, that it DOES NOT cable into the "Input View" or "to Recording & Thru". This creates yet another issue:
The controls on the Keystation have to send SOME form of MIDI control message / data to Logic. Well if the faders on the Keystation are preset to send Ch1-9, Volume 0-127 messages, then when you move a fader on the Keystation (as the Logic Control) since the Keystation is still reaching the sequencer from the MIDI port, you will be sending MIDI values that can effect your current track possibly when you don't want to. The work around for this is to be sure that all the faders / knobs that you want to use as your fake Logic Control are sending useless MIDI data... i.e. CC 75, 76, 77, and so on. This way moving faders won't effect playback, although you could still in theory record this MIDI data into your sequencer. You could however filter this events from entering the sequencer input with a transformer since you know precisely what MIDI CC values you are changing. The easy way to assign these values is to use the program Enigma from M-Audio that I mentioned above.
More discussion specifically related to the Keystation Pro 88:
You can do a lot using the Controller Assignments and different Zones from the Logic Control. For instance, the real Logic Control has Solo, Mute, and Record buttons for the 8 faders. The Keystation Pro only has 1 button underneath each fader. But you could use one of the other buttons to toggle Solo, Mute, and Record mode so that depending on which mode your in, the buttons underneath each fader will correspond to Mute or Solo etc. By the way, a good setup from my experience is to use the first 8 faders of the Keystation as the track faders, and the final 9th fader for Master Volume. You can then set two of the buttons underneath the Knobs as Bank Left and Bank Right buttons to change the 8 fader tracks to correspond to the onscreen track groups of 8. Also don't forget that you can assign TWO functions to EACH button, since a button press can send a value of 127 and a button release can send a 00 value. So if you press and hold a button it can activate "Shift-select Mode" and until released it can make the buttons under the faders act as Volume to Zero resets or whatever you want. When you release the button it will go back to just Mute mode or Solo mode. The Controller Assignments window has MANY options, and parameters some of which are very confusing and take a lot of trial and error to understand... the manual helps a little but of course isn't perfect.

I'm thinking about buying a Keystation Pro 88 (2nd hand) so I was googling around and found this:
http://www.soundonsound.com/sos/Oct04/articles/keystation.htm
[quote]
I had some trouble getting the transport controls to work with Emagic's Logic, even when I loaded the 'Pro 88 Logic Preset.LSO' file on the supplied CD-ROM into Logic. I contacted the guys who designed and set up the Keystation here in the UK at the old Evolution offices, and between us we managed to work out what was going wrong. First of all, you need to enter the appropriate MIDI key commands in Logic's user preferences. These cannot be updated with an LSO file, so the commands have to be entered using the Learn Key function in Logic (see the screenshot below for the list we used). Then we discovered that the transport keys were toggling, which meant that only each second press of each key was actually working. It turned out that I had an early version of the Logic preset before this had been fixed, but the more recent one has been put on the M Audio web site for anyone else that needs it. It took about 30 seconds to change the output commands so that the buttons were no longer toggling.[/quote]
Did you get it to work correctly eventually?

Updating logic control problem

Hi. Hope somebody can help. I just bought a used Logic Control and I'm trying to update it to Mackie Control functionality. I have the update but the instructions are a bit confusing I have imported the MIDI file into Logic but then I am told to "Disable the Mackie Control/Logic Control as a midi controller". I don't know what this means. I have tried removing it from the control surfaces setup but no luck. When I play the midi file I get nothing. The logic control stays in "Waiting for MIDI upgrade" mode but no update. Help!

I am told to "Disable the Mackie Control/Logic Control as a midi
controller". I don't know what this means. I have tried removing
it from the control surfaces setup but no luck
From the instructions you state, that's what I'd infer from them.
When I play the midi file I get nothing. The logic control stays
in "Waiting for MIDI upgrade" mode but no update.
Where are you playing to MIDI file to? You sure you're playing it to the MIDI port that the LC is on, and that your interface isn't filtering sysex data?

Logic Control - XT display not resonding, noise coming thru midi....

I have a Logic Control and a Logic Control XT. XT on left, channels 1-8. Display on XT lights up, but doesn't recognize tracks (faders and other controls, do however).
"Midi in" on XT causes noise in my monitors (don't tell me it's impossible because midi sends 0 or 1 -- it IS causing interference in my monitors). Can bad midi cables or a bad midi interface cause noise?
Is my set up somehow incorrect?

I have a Logic Control and a Logic Control XT. XT on
left, channels 1-8. Display on XT lights up, but
doesn't recognize tracks (faders and other controls,
do however).
So everything works, but you get nothing on the display? When you power it up, do words come up on the display then (like a "Logic Control XT" welcome message?)
If not, perhaps the display has died?
"Midi in" on XT causes noise in my monitors (don't
tell me it's impossible because midi sends 0 or 1 --
it IS causing interference in my monitors). Can bad
midi cables or a bad midi interface cause noise?
You might have some kind of ground loop issue, which seems unlikely seeing as MIDI cables don't have a direct electrical connection.
It may be that your computer causes interference when sending MIDI (nothing to do with the Logic Control). Early motherboards, for instance, gave audio problems when using USB MIDI - I had an old motherboard which gave clicks in the audio drivers when sending MIDI via USB, which is why I used the serial bus MIDI instead, and that solved the problem.
Is my set up somehow incorrect?
Difficult to tell from just the info you provide!

How to use Fuzzy Logic Controller for transfer function in labview control and simulation loop?

I am facing problem with fuzzy PD logic controller for transfer function in control and simulation loop.
Plz Help me in this regard...................
i have attache snapshot of my program
Attachments:
fuzzy in simulation loop.JPG ‏52 KB

Hi Sankhadip,
Sorry for the late response. I was looking at your code and
I noticed that the graph scale does not start from zero. That might be the
reason why you don't see the transient in the simulation. To change the scales
simply double click on the lower limit and set it to zero. If this is not the
expected results, can you please post the expected results, so we can see what are the
differences between the results . Also, you might be using different
solvers, and that gives different results as well.
Thanks and have a great day.
Esmail Hamdan | Applications Engineering | National
Instruments

Final Cut Express and logic control

Hi,
has anyone ever achieved to combine final cut express and logic control?
I'm a logic audio user and Iwould be greatful to influence major features of final cut with the controller "logic control XT" and let them work together.
Thanks for your help and ideas!
Alex

No. FCE has no mixer.

Logic 9 and Logic Control Surface

I recently received a Behringer BCF2000 as a gift and have successfully set it up in LC (Logic Control) mode. I'm having an odd problem, however, as the control surface only is receiving from Logic and changes on the BCF2000 are not reflecting in logic. When I change sliders/pan positions/etc in Logic, the BCF2000 reflects these changes. However, pressing buttons on the BCF2000 is unresponsive and if I move a slider, the motorized fader will return to the position as set in Logic.
I have been scouring the manuals for a solution, I'm sure it's something simple but I'm getting very frustrated. Any help would be immensely appreciated. Thanks!

Indeed.
Remove the control surface driver, and use LC Xmu instead. It's the absolute best way to use the Korg controllers with Logic, and has just about every feature you want/need.
http://www.opuslocus.com/lcxmu/

Aux Channelstrips and Logic Control

Hi,
It seems almost impossible to have ONLY the tracks in the arrange window reflected in my Logic Control + Extender. If I use BFD 2 with many Aux they will appear on the Logic Control, although they are not shown in the arrange and cluttering up my workflow!
Why is it so difficult just to have the tracks in the arrange laid down to the Logic Control???

Read the manual's section where Environment is covered. Environment is the part of Logic which gives it unlimited power to control (or the ability of being controlled by) MIDI devices. Basically, the control surface could be configured in the Environment, including the way all the knobs and sliders are used if need be. However, you must know what you are doing and what you are configuring all the knobs and sliders for. Besides, a ready-to-use Logic template or set of templates for your keyboard may already exist.

Logic Control Faders Moving On Their Own

i have logic control by emagic v1.02. yes i have ensemble but its turned off and i'm using built in audio. what it does is when logic 8 is open and i touch a fader,even without song playing, when i touch the fader, it moves up about a few db. tried on different projects and does the same. there is no automation. anyone else experiencing this? and is there a fix?
thanks

Be sure to Rebuild Defaults for control surfaces after changing Logic's preferences for Touching Fader Selects Track. This might clear it up.
1.02 is the latest firmware for these devices. They've worked perfectly until Logic 8. Apple definitely made some mistakes and overlooked a few items when they rebuilt the control surface subsystem. Nobody's LC or MC is working in LP8 100% yet. I'm sure they'll fix it. Just a matter of time.

What are the logical structure and physical structure in oracle

what are the logical structure and physical structure in oracle and how can allocate a DB block size as default size is 8192?

From the Concepts Guide
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/toc.htm
The physical structures are:
Datafiles
Control Files
Redo Log Files
Archive Log Files
Parameter Files
Alert and Trace Log Files
Backup Files
The Logical Structures are:
Tablespaces
Oracle Data Blocks
Extents
Segments

How to insert row in table control and save the data in tables

Hi,
I have one table control i am displaying data into table control ,
my problem is : i want to display data into read mode in table control.
but when i click on insert button on the same screen i want one blank line should inserted into table control , then i want to insert some data into table control on that row , when i click the save button . the new data inserted into the table control is insert that data into ztable ,
please give me solution
main problen is how can know inserted line in table control and pass that data into ztable.

Hi,
Follow the below logic,
PROCESS BEFORE OUTPUT.
MODULE STATUS_0001.
MODULE POPULATE_TABLE_CONTROL. --> Get the data from table store in
                                                                      ITAB
LOOP AT GT_CTRL_LP_D516 INTO GS_WA_CTRL_LP_D516
       WITH CONTROL CTRL_LP_D516
       CURSOR CTRL_LP_D516-CURRENT_LINE.
The following module moves data to control
    MODULE MOVE_TO_CONTROL.--> Move data from ITAB to table control
ENDLOOP.
PROCESS AFTER INPUT.
LOOP AT GT_CTRL_LP_D516.
ENDLOOP.
MODULE EXIT AT EXIT-COMMAND.
MODULE USER_COMMAND_0001. --> Here you have to take out the values from table control and update database table
Reward points if helpful.
Thanks and regards,
Mallareddy Rayapureddy,
Munich, Germany.

What are the uses of table control and tabstrip control

can anyone tell me the uses of table control and tabstrip control

Hi,
table control is more comfortable for customizing.scroll bars all possible in this.where as it is not possible in step loops.
check this example.
PROGRAM ZBHTCTRL.
TABLES: LFA1, EKKO.
DATA: OKCODE1 LIKE SY-UCOMM,
OKCODE2 LIKE SY-UCOMM.
CONTROLS TABC TYPE TABLEVIEW USING SCREEN 1001.
DATA: BEGIN OF ITAB OCCURS 0,
MANDT LIKE EKKO-MANDT,
EBELN LIKE EKKO-EBELN,
BSTYP LIKE EKKO-BSTYP,
BSART LIKE EKKO-BSART,
END OF ITAB.
MODULE USER_COMMAND_1000 INPUT.
CASE OKCODE1.
WHEN 'BACK'.
SET SCREEN 0.
WHEN 'NEXT'.
SET SCREEN 1001.
SELECT * FROM EKKO INTO CORRESPONDING FIELDS OF TABLE ITAB WHERE
LIFNR = LFA1-LIFNR.
ENDCASE.
ENDMODULE. " USER_COMMAND_1001 INPUT
MODULE MOVE_DATA OUTPUT.
EKKO-MANDT = ITAB-MANDT.
EKKO-EBELN = ITAB-EBELN.
EKKO-BSTYP = ITAB-BSTYP.
EKKO-BSART = ITAB-BSART.
ENDMODULE. " MOVE_DATA OUTPUT
MODULE USER_COMMAND_1001 INPUT.
CASE OKCODE2.
WHEN 'BACK'.
SET SCREEN 1000.
ENDCASE.
ENDMODULE. " USER_COMMAND_1001 OUTPUT
MODULE STATUS_1001 OUTPUT.
SET PF-STATUS 'MENU'.
SET TITLEBAR 'TIT'.
ENDMODULE. " STATUS_1001 OUTPUT
MODULE STATUS_1000 OUTPUT.
SET PF-STATUS 'DMENU'.
SET TITLEBAR 'xxx'.
ENDMODULE. " STATUS_1000 OUTPUT
FORM ON_CTMENU_FORM1 USING CMENU TYPE REF TO CL_CTMENU.
CALL METHOD CMENU->LOAD_GUI_STATUS
EXPORTING
PROGRAM = ' ZBHTCTRL'
STATUS = 'CMENU'
MENU = CMENU.
CALL METHOD CMENU->ADD_FUNCTION
EXPORTING
FCODE = 'RX'
TEXT = 'RECIEVE'.
ENDFORM.
FLOW LOGIC:
PROCESS BEFORE OUTPUT.
MODULE STATUS_1000.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_1000.
PROCESS BEFORE OUTPUT.
MODULE STATUS_1001.
LOOP AT ITAB WITH CONTROL TABC CURSOR TABC-TOP_LINE.
MODULE MOVE_DATA.
ENDLOOP.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_1001.
LOOP AT ITAB.
ENDLOOP.
for more info check this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/dbac1d35c111d1829f0000e829fbfe/content.htm
thanks
Ashu.

Logic Control and LP8

Similar Messages

Maybe you are looking for