Sdl_image vs. xf86-input-mouse naming convention

This is really a minor issue, but I just wanted to point out that, people, we should pick either underscores or hyphens. Because mixing them just gets confusing. I realize it can be really hard to make all package naming completely perfect, because of the whole problem where you have to kind of name a package after the application contained therein. But you know, it's just a thought.
I'm switching to Hyphen Linux: "We Have Our Package Naming Conventions Totally Under Control."
Oh, and I'll say it first: "Yawn..."

The reason for this: it's following upstream stuff. xf86-input-mouse is named this way upstream, sdl_image is also named this way upstream.

Similar Messages

[xf86-input-evdev-trackpoint] Still no middle mouse scroll on T440p

Hi all,
This post is related to the launchpad bug "Middle button does not work for scrolling" and to the AUR package "xf86-input-evdev-trackpoint".
Abstract: The synaptics driver is currently not able to emulate scrollling using the middle mouse button on newer ThinkPads (**40 series). This AUR package aims at resolving this issue, but I'm having trouble to make it work.
So I installed the package and rebooted. The new file "90-evdev-trackpoint.conf" appeared in my /etc/X11/xorg.conf.d folder and the installation went fine. However:
My left and middle mouse buttons are not recognized afterwars, only my right mouse button works
I still have no middle mouse button scrolling feature
Maybe worth mentioning:
I do not use the testing repo
KDE desktop
System is up-to-date
The 90-.... Xorg conf file is the highest conf file number (so the settings should not be overridden)
Anyway, thanks for the effort to get that touchpad going, and thank you for your help!
Regards,
Laurent

Hi,
I played around with the config files, and have some results by now. Note that I use the touchpad too, which causes some more problems.
So the source of the problem was apparently my 50-synaptics.conf, in which the Touchpad sections used the "synaptics" driver. There were 2 occurrences, if I change both, it works!
However:
synaptics provides MUCH better usability than evdev, if you do not configure everything by now. Especially important was the hysteresis, which made normal touchpad clicks usable again.
tap-clicks are triggered too sensibly (with too little pressure on the touchpad). I think this is evdev related and only a setting, but I couln't fine one. Have you got an idea?
As I use the SoftButtonAreas and AreaTopEdge settings, the top border of my touchpad should emulate the three "classic" ThinkPad buttons, and the mouse pointer should not move. This worked fine with synaptic. Now that the driver is evdev, only the middle and right area react to those classic clicks, but the left mouse button area is dead. I have absolutely no idea how to get it back without having mouse pointer movements in those areas. Any suggestions?
Middle click events are not always delivered reliably
Btw: tap-to-click and normal click generally work fine in the areas below AreaTopEdge.
So, have you got an idea how to get the "dead" area working again?
And, why did you use evdev, and not synaptics? I assume you have to make evdev work before synaptics can work, no?
Furthermore: why did you disable your touchpad?
At last, my config files:
50-synaptics.conf
# Example xorg.conf.d snippet that assigns the touchpad driver
# to all touchpads. See xorg.conf.d(5) for more information on
# InputClass.
# DO NOT EDIT THIS FILE, your distribution will likely overwrite
# it when updating. Copy (and rename) this file into
# /etc/X11/xorg.conf.d first.
# Additional options may be added in the form of
# Option "OptionName" "value"
Section "InputClass"
Identifier "touchpad catchall"
Driver "evdev"
MatchIsTouchpad "on"
Option "TapButton1" "1"
Option "TapButton2" "3"
Option "TapButton3" "2"
# This option is recommend on all Linux systems using evdev, but cannot be
# enabled by default. See the following link for details:
# http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
MatchDevicePath "/dev/input/event*"
EndSection
Section "InputClass"
Identifier "touchpad ignore duplicates"
MatchIsTouchpad "on"
MatchOS "Linux"
MatchDevicePath "/dev/input/mouse*"
Option "Ignore" "on"
EndSection
# This option enables the bottom right corner to be a right button on
# non-synaptics clickpads.
# This option is only interpreted by clickpads.
Section "InputClass"
Identifier "Default clickpad buttons"
MatchDriver "evdev"
Option "SoftButtonAreas" "60% 0 0 2600 40% 60% 0 2600"
Option "AreaTopEdge" "2600"
Option "PalmDetect" "1"
Option "HorizTwoFingerScroll" "1"
Option "HorizHysteresis" "30"
Option "VertHysteresis" "30"
Option "FingerPress" "100"
# Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
# To disable the bottom edge area so the buttons only work as buttons,
# not for movement, set the AreaBottomEdge
# Option "AreaBottomEdge" "82%"
EndSection
Section "InputClass"
Identifier "trackpoint catchall"
MatchIsPointer "true"
MatchProduct "TrackPoint|DualPoint Stick"
MatchDevicePath "/dev/input/event*"
Option "EmulateWheel" "1"
Option "EmulateWheelTimeout" "200"
Option "EmulateWheelButton" "2"
Option "XAxisMapping" "6 7"
Option "YAxisMapping" "4 5"
EndSection
# This option disables software buttons on Apple touchpads.
# This option is only interpreted by clickpads.
Section "InputClass"
Identifier "Disable clickpad buttons on Apple touchpads"
MatchProduct "Apple|bcm5974"
MatchDriver "synaptics"
Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
EndSection
90-evdev-trackpoint.conf
Section "InputClass"
Identifier "TrackPoint"
MatchProduct "TrackPoint"
MatchDriver "evdev"
Option "EmulateWheel" "1"
Option "EmulateWheelButton" "2"
Option "XAxisMapping" "6 7"
EndSection
Thanks for your time, and keep up the great work!
Regards,
Laurent
Last edited by LimaSierra (2013-12-12 15:53:07)

Question about Best Practices - Redwood Landscape/Object Naming Conventions

Having reviewed documentation and posts, I find that there is not that much information available in regards to best practices for the Redwood Scheduler in a SAP environment. We are running the free version.
1) The job scheduling for SAP reference book (SAP Press) recommends multiple Redwood installations and using export/import to move jobs and other redwood objects from say DEV->QAS->PROD. Presentations from the help.sap.com Web Site show the Redwood Scheduler linked to Solution Manager and handling job submissions for DEV-QAS-PROD. Point and Shoot (just be careful where you aim!) functionality is described as an advantage for the product. There is a SAP note (#895253) on making Redwood highly available. I am open to comments inputs and suggestions on this issue based on SAP client experiences.
2) Related to 1), I have not seen much documentation on Redwood object naming conventions. I am interested in hearing how SAP clients have dealt with Redwood object naming (i.e. applications, job streams, scripts, events, locks). To date, I have seen in a presentation where customer objects are named starting with Z_. I like to include the object type in the name (e.g. EVT - Event, CHN - Job Chain, SCR - Script, LCK - Lock) keeping in mind the character length limitation of 30 characters. I also have an associated issue with Event naming given that we have 4 environments (DEV, QA, Staging, PROD). Assuming that we are not about to have one installation per environment, then we need to include the environment in the event name. The downside here is that we lose transportability for the job stream. We need to modify the job chain to wait for a different event name when running in a different environment. Comments?

Hi Paul,
As suggested in book u2018job scheduling for SAP from SAPu2019 press it is better to have multiple instances of Cronacle version (at least 2 u2013 one for development & quality and other separate one for production. This will have no confusion).
Regarding transporting / replicating of the object definitions - it is really easy to import and export the objects like Events, Job Chain, Script, Locks etc. Also it is very easy and less time consuming to create a fresh in each system. Only complicated job chains creation can be time consuming.
In normal cases the testing for background jobs mostly happens only in SAP quality instance and then the final scheduling in production. So it is very much possible to just export the verified script / job chain form Cronacle quality instance and import the same in Cronacle production instance (use of Cronacle shell is really recommended for fast processing)
Regarding OSS note 895253 u2013 yes it is highly recommended to keep your central repository, processing server and licencing information on highly available clustered environment. This is very much required as Redwood Cronacle acts as central job scheduler in your SAP landscape (with OEM version).
As you have confirmed, you are using OEM and hence you have only one process server.
Regarding the conventions for names, it is recommended to create a centrally accessible naming convention document and then follow it. For example in my company we are using the naming convention for the jobs as Z_AAU_MM_ZCHGSTA2_AU01_LSV where A is for APAC region, AU is for Australia (country), MM is for Materials management and then ZCHGSTA2_AU01_LSV is the free text as provided by batch job requester.
For other Redwood Cronacle specific objects also you can derive naming conventions based on SAP instances like if you want all the related scripts / job chains to be stored in one application, its name can be APPL_<logical name of the instance>.
So in a nutshell, it is highly recommend
Also the integration of SAP solution manager with redwood is to receive monitoring and alerting data and to pass the Redwood Cronacle information to SAP SOL MAN to create single point of control. You can find information on the purpose of XAL and XMW interfaces in Cronacle help (F1).
Hope this answers your queries. Please write if you need some more information / help in this regard.
Best regards,
Vithal

BPC Standard Naming Convention

Hi Gurus,
Could you please share BPC naming conventions standards?
I am looking for prefix for objects such as:
Environment
Model
Dimension
Team
Task Profile
Data Access Profile
Member Formulas
Logic Script
Business Rule
Controls
Input Screen
Report
Data Manager Package
Data Manager Package Link
Transformation File
Conversion File
Process Chain
Thanks.

As far as I know there are no naming conventions other than no special characters or spaces. NW is case sensitive, so you need to be careful there. In terms of prefixes, I'm not sure what you mean. Some of the technical objects in NW are in the CPMB namespace but you are not adding that namespace to anything
Here are some comments:
Environment - the description in the BPC admin client can, the technical name on the backend will be generated
Model - same as environment
Dimension - same as environment
Member Formulas - this is driven by member IDs
Input Screen - not sure what this is
Data Manager Package
Process Chain - the out of the box PCs are all in the CPMB namespace, the new ones just need to be copied in there but they wouldn't be created in BPC rather in BW
Hope this make sense,
Akos

Flatfile conversion with output file has a NAMING CONVENTION

Dear SAP experts,
I need some advise regarding my scenario.
I am converting a message into flatfile. (customized .csv)
But, the output .csv flatfile must have a naming convention.
E.g. Globus_20071020 (Customer name_YearMonthDate)
Can somebody give me ideas/inputs on what will I configure in File Receiver (FCC) in order to have an output file having a naming convention indicated above.
Or do i need additional configurations?
Please advise.
Thank you very much in advance.
Fred

Hi,
You could pass this kind of File name from mapping at runtime or
You could use the variable substitutions to create the fiel neame as per naming convention as adding date .
With reference to Variables youcould set file name as Globus_%payload.<Date>%
Pass the value in date field of payload
Refer
Variable Substitution
How to use Variable substituion
/people/sameer.shadab/blog/2005/09/23/an-interesting-usage-of-variable-substitution-in-xi
/people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
how to use attributes in variable substitution???:(
Dynamic file name
/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i --> Dynamic File Name using XI 3.0 SP12 Part I
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii --> Dynamic file name(XSLT Mapping with Java Enhancement) using XI 3.0 SP12 Part -II
Dynamic File name in File adapter
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
1. In the sender file adapter , select Adapter Specific Attributes --> FileName.
2. Use the code in this link to read the filename inside a UDF in your mapping.
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create(
http://sap.com/xi/XI/System/File,
FileName);
String filename = conf.get(key);
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/03612cdecc6e76e10000000a422035/content.htm
Thanks
Swarup

VC models...BeX naming conventions

Hello,
I have a problem in VC...with naming conventions.
The base Bex queries were not followed Naming Conventions and the VC models were completely designed based on the queries.
Now the management had decided to move the content only with naming conventions...from Bex we can do the query as Save As in a simple way. What about VC? Can we do it similar...i dont think so. Can someone help me with the best solution how to solve this issue.
what i did: I took the copy of VC model and added new datasource (Bex new query followed naming convention). Then i try to drag the input and output links to the new datasource i cant able to do that, is there a best way? my other question is if i change the links from old datasource to new datasource then all the fields and values for the rest of the model are blanked (not copied from the previous model). How to best solve this issue? Please advice...and consider this as high priority.
Note: If there is no solution to my question, how could SAP develop the tools with out thinking these constraints during the Product development. I feel like strange...please respond.
Thanks,
Pandu
Edited by: pandu on Jun 15, 2010 12:29 PM

Hi
I have a doubt regarding your requirement.
If you are creating new Bi queries, (with Save As) so what your are going to do with existing queries? If not, you can continue with same VC model, you just need to change model name as per convention.
Also for the second point you mentioned, VC is just for arranging the layout of the dashboard & the layout will remain same even if you delete exisitng queries & add new queries. Also the Data service (BI Query in this case) is a foundation of VC model & all other things like Input/ Output Form/Table are with reference to data service. So if you are deleting data service obviously all values will get reset. There are few constraints in VC but i dont think this is a constraint.
If possible, follow the naming convention in discripption of query for earlier queries which will not lead to duplication of efforts for earlier queries & Vc models. & You can start following naming convention for new queries.
Regards
Sandeep

[SOLVED] Touchpad Synaptics not works after last update of xf86-input

after this packages
xf86-input-synaptics 1.8.0-2 <<< works
xf86-input-synaptics 1.8.0-3 << not works
https://projects.archlinux.org/svntogit … 54796cff46
dmesg|grep input
[ 0.866883] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 1.842679] input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/0003:04F3:0103.0001/input/input2
[ 1.842756] hid-generic 0003:04F3:0103.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 04f3:0103] on usb-0000:00:14.0-1/input0
[ 1.843934] input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.1/0003:04F3:0103.0002/input/input3
[ 1.844001] hid-generic 0003:04F3:0103.0002: input,hidraw1: USB HID v1.10 Device [HID 04f3:0103] on usb-0000:00:14.0-1/input1
[ 2.169742] input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:09DA:9066.0003/input/input4
[ 2.169933] hid-generic 0003:09DA:9066.0003: input,hiddev0,hidraw2: USB HID v1.11 Keyboard [A4TECH USB Device] on usb-0000:00:14.0-2/input0
[ 2.171262] input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/0003:09DA:9066.0004/input/input5
[ 2.171357] hid-generic 0003:09DA:9066.0004: input,hidraw3: USB HID v1.11 Mouse [A4TECH USB Device] on usb-0000:00:14.0-2/input1
[ 10.099521] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input6
[ 10.099624] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7
[ 10.099692] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
[ 10.398671] input: PC Speaker as /devices/platform/pcspkr/input/input9
[ 11.840489] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10
[ 12.211308] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3a/LNXVIDEO:00/input/input11
[ 12.212530] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input12
[ 13.254950] sound hdaudioC0D0: inputs:
[ 13.580490] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input13
[ 13.580985] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
[ 13.581106] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
[ 13.581224] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
[ 17.274881] input: WebCam SC-13HDL11939N as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input17
journalctl -b |grep input
ago 21 09:02:37 drog-laptop kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
ago 21 09:02:37 drog-laptop kernel: input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/0003:04F3:0103.0001/input/input2
ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:04F3:0103.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 04f3:0103] on usb-0000:00:14.0-1/input0
ago 21 09:02:37 drog-laptop kernel: input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.1/0003:04F3:0103.0002/input/input3
ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:04F3:0103.0002: input,hidraw1: USB HID v1.10 Device [HID 04f3:0103] on usb-0000:00:14.0-1/input1
ago 21 09:02:37 drog-laptop kernel: input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:09DA:9066.0003/input/input4
ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:09DA:9066.0003: input,hiddev0,hidraw2: USB HID v1.11 Keyboard [A4TECH USB Device] on usb-0000:00:14.0-2/input0
ago 21 09:02:37 drog-laptop kernel: input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/0003:09DA:9066.0004/input/input5
ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:09DA:9066.0004: input,hidraw3: USB HID v1.11 Mouse [A4TECH USB Device] on usb-0000:00:14.0-2/input1
ago 21 09:02:40 drog-laptop kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input6
ago 21 09:02:40 drog-laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7
ago 21 09:02:40 drog-laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
ago 21 09:02:41 drog-laptop kernel: input: PC Speaker as /devices/platform/pcspkr/input/input9
ago 21 09:02:42 drog-laptop kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10
ago 21 09:02:42 drog-laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3a/LNXVIDEO:00/input/input11
ago 21 09:02:42 drog-laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input12
ago 21 09:02:43 drog-laptop kernel: sound hdaudioC0D0: inputs:
ago 21 09:02:44 drog-laptop kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input13
ago 21 09:02:44 drog-laptop kernel: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
ago 21 09:02:44 drog-laptop kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
ago 21 09:02:44 drog-laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
ago 21 09:02:47 drog-laptop kernel: input: WebCam SC-13HDL11939N as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input17
ago 21 09:02:52 drog-laptop acpid[589]: starting up with netlink and the input layer
ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event7 (Power Button)
ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event11 (Video Bus)
ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event10 (Video Bus)
ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event6 (Power Button)
ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event5 (Lid Switch)
cat /usr/share/X11/xorg.conf.d/50-synaptics.conf
# Example xorg.conf.d snippet that assigns the touchpad driver
# to all touchpads. See xorg.conf.d(5) for more information on
# InputClass.
# DO NOT EDIT THIS FILE, your distribution will likely overwrite
# it when updating. Copy (and rename) this file into
# /etc/X11/xorg.conf.d first.
# Additional options may be added in the form of
# Option "OptionName" "value"
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
# This option is recommend on all Linux systems using evdev, but cannot be
# enabled by default. See the following link for details:
# http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
MatchDevicePath "/dev/input/event*"
EndSection
Section "InputClass"
Identifier "touchpad ignore duplicates"
MatchIsTouchpad "on"
MatchOS "Linux"
MatchDevicePath "/dev/input/mouse*"
Option "Ignore" "on"
EndSection
# This option enables the bottom right corner to be a right button on clickpads
# and the right and middle top areas to be right / middle buttons on clickpads
# with a top button area.
# This option is only interpreted by clickpads.
Section "InputClass"
Identifier "Default clickpad buttons"
MatchDriver "synaptics"
Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
Option "SecondarySoftButtonAreas" "58% 0 0 8% 42% 58% 0 8%"
EndSection
# This option disables software buttons on Apple touchpads.
# This option is only interpreted by clickpads.
Section "InputClass"
Identifier "Disable clickpad buttons on Apple touchpads"
MatchProduct "Apple|bcm5974"
MatchDriver "synaptics"
Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
EndSection
xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ HID 04f3:0103 id=11 [slave pointer (2)]
⎜ ↳ A4TECH USB Device id=12 [slave pointer (2)]
⎜ ↳ A4TECH USB Device id=13 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ HID 04f3:0103 id=10 [slave keyboard (3)]
↳ WebCam SC-13HDL11939N id=14 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
synclient
Couldn't find synaptics properties. No synaptics driver loaded?
lsmod
Module Size Used by
bbswitch 12878 0
nls_iso8859_1 12461 1
nls_cp437 16553 1
vfat 21231 1
fat 61984 1 vfat
fuse 87446 5
uvcvideo 78952 0
videobuf2_vmalloc 12816 1 uvcvideo
ath3k 12685 0
videobuf2_memops 12519 1 videobuf2_vmalloc
videobuf2_core 47787 1 uvcvideo
ecb 12737 1
v4l2_common 12995 1 videobuf2_core
btusb 25625 0
bluetooth 394557 3 ath3k,btusb
videodev 126443 3 uvcvideo,v4l2_common,videobuf2_core
media 18365 2 uvcvideo,videodev
6lowpan_iphc 16588 1 bluetooth
snd_hda_codec_hdmi 45117 1
snd_hda_codec_realtek 67127 1
snd_hda_codec_generic 63126 1 snd_hda_codec_realtek
nvram 13034 0
joydev 17063 0
mousedev 17272 0
ipt_REJECT 12465 1
xt_comment 12427 2
arc4 12536 2
xt_LOG 17156 5
ath9k 94538 0
ath9k_common 21746 1 ath9k
ath9k_hw 403753 2 ath9k_common,ath9k
ath 26067 3 ath9k_common,ath9k,ath9k_hw
mac80211 514630 1 ath9k
r8169 68119 0
mii 12675 1 r8169
cfg80211 454161 4 ath,ath9k_common,ath9k,mac80211
snd_hda_intel 26327 4
snd_hda_controller 26727 1 snd_hda_intel
snd_hda_codec 108552 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
i915 864723 4
drm_kms_helper 49262 1 i915
snd_hwdep 17244 1 snd_hda_codec
snd_pcm 88487 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
iTCO_wdt 12831 0
iTCO_vendor_support 12649 1 iTCO_wdt
coretemp 12820 0
hwmon 12930 1 coretemp
led_class 12859 1 ath9k
intel_rapl 17356 0
rfkill 18867 3 cfg80211,bluetooth
x86_pkg_temp_thermal 12951 0
psmouse 102792 0
drm 258005 6 i915,drm_kms_helper
intel_powerclamp 17122 0
kvm_intel 143217 0
snd_timer 26614 1 snd_pcm
shpchp 35210 0
lpc_ich 20768 0
mei_me 17941 0
intel_gtt 17848 1 i915
kvm 413027 1 kvm_intel
crct10dif_pclmul 13394 0
crc32_pclmul 12915 0
crc32c_intel 21809 0
ghash_clmulni_intel 12978 0
cryptd 18553 1 ghash_clmulni_intel
microcode 22061 0
evdev 21544 29
pcspkr 12595 0
mac_hid 12633 0
i2c_algo_bit 12744 1 i915
i2c_i801 16965 0
mei 75033 1 mei_me
serio_raw 12849 0
i2c_core 50152 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev
tpm_tis 17134 0
thermal 17559 0
fan 12681 0
battery 13356 0
snd 69340 16 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
soundcore 13031 2 snd,snd_hda_codec
tpm 31467 1 tpm_tis
video 17995 1 i915
button 12909 1 i915
processor 27777 0
xt_limit 12601 7
wmi 17339 0
ac 12715 0
xt_tcpudp 12527 11
xt_addrtype 12557 4
nf_conntrack_ipv4 17706 7
nf_defrag_ipv4 12483 1 nf_conntrack_ipv4
xt_conntrack 12681 7
ip6_tables 26025 0
nf_conntrack_netbios_ns 12445 0
nf_conntrack_broadcast 12365 1 nf_conntrack_netbios_ns
nf_nat_ftp 12460 0
nf_nat 22338 1 nf_nat_ftp
nf_conntrack_ftp 16783 1 nf_nat_ftp
nf_conntrack 87324 7 nf_nat_ftp,nf_conntrack_netbios_ns,nf_nat,xt_conntrack,nf_conntrack_broadcast,nf_conntrack_ftp,nf_conntrack_ipv4
iptable_filter 12536 1
ip_tables 26011 1 iptable_filter
x_tables 27104 10 xt_comment,ip_tables,xt_tcpudp,xt_limit,xt_conntrack,xt_LOG,iptable_filter,ipt_REJECT,ip6_tables,xt_addrtype
ext4 497695 2
crc16 12343 2 ext4,bluetooth
mbcache 17171 1 ext4
jbd2 86460 1 ext4
hid_generic 12393 0
usbhid 44507 0
hid 102220 2 hid_generic,usbhid
sd_mod 44356 5
sr_mod 21903 0
cdrom 47479 1 sr_mod
crc_t10dif 12431 1 sd_mod
crct10dif_common 12356 2 crct10dif_pclmul,crc_t10dif
atkbd 22254 0
libps2 12739 2 atkbd,psmouse
ahci 29195 4
libahci 27158 1 ahci
libata 181553 2 ahci,libahci
ehci_pci 12512 0
scsi_mod 142915 3 libata,sd_mod,sr_mod
xhci_hcd 152990 0
ehci_hcd 69939 1 ehci_pci
usbcore 199328 7 ath3k,btusb,uvcvideo,ehci_hcd,ehci_pci,usbhid,xhci_hcd
usb_common 12440 1 usbcore
i8042 18002 1 libps2
serio 18282 6 serio_raw,atkbd,i8042,psmouse
EDIT:
cat /var/log/Xorg.0.log| grep Synap
[ 301.566] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event9)
[ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 301.566] (II) Using input driver 'evdev' for 'SynPS/2 Synaptics TouchPad'
[ 301.566] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 301.566] (**) evdev: SynPS/2 Synaptics TouchPad: Device: "/dev/input/event9"
[ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found 3 mouse buttons
[ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found absolute axes
[ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found absolute multitouch axes
[ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found x and y absolute axes
[ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found absolute touchpad.
[ 301.566] (II) evdev: SynPS/2 Synaptics TouchPad: Configuring as touchpad
[ 301.566] (**) evdev: SynPS/2 Synaptics TouchPad: YAxisMapping: buttons 4 and 5
[ 301.567] (**) evdev: SynPS/2 Synaptics TouchPad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 301.567] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 16)
[ 301.567] (II) evdev: SynPS/2 Synaptics TouchPad: initialized for absolute axes.
[ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0
[ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 301.567] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 301.567] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
(EE) [dix] SynPS/2 Synaptics TouchPad: unable to find touch point 1
EDIT2:
SOLVED!
just remove /etc/X11/xorg.conf.d/10-evdev.conf
Last edited by drog (2014-08-21 13:29:49)

lordheavy wrote:
X reads first configuration in /usr/share/X11/xorg.conf.d then /etc/X11/xorg.conf.d
When you copy 10-evdev.conf file into /etc/X11 you completly override previous system configuration. It's the reason copying synaptics configuration file into /etc/X11 fixes the issue
Defining default system configuration in /etc/X11 with previous xorg was a mistake, now it's fixed.
Wiki should be fixed. It's not a packaging bug, but a configuration bug.
@lordheavy
I agree with you that the new xf86-input-synaptics package is using the right configuration scheme, however it is breaking the functionality on every installed system. It was a packaging bug, which is now fixed, but it has to be handled manually by most users of previous versions. That's why I won't re-open the bug report FS#41589. Instead, I am asking here: shouldn't this change be notified to the users just like it has been done for most breaking changes on archlinux frontpage news?
By the way, thanks for your great work.

SAP naming conventions: customer DDIC objects, ABAP programming

SAP Note 16466 Customer name range for SAP objects contains the SAP naming conventions for customer DDIC objects. Rule of thumb is that the names reserved for customer objects start with 'Y' or 'Z'. However, this note contains the naming convention for DDIC objects only.
ABAP Code Inspector (transaction SCI) contains the following naming convention for ABAP programming:
- Global types: T_
- Global constants: C_
- Global data: gv_
- Global field-symbols: FS_
- Global parameters: P_
- Global select-options: S_
- Global field-groups: FS_
- Local types: LT_
- Local constants: LC_
- Local data: v_
- Local field-symbols: LFS_
This is the only place I know for ABAP programming naming convention. Does SAP has somewhere else any additional naming convention guidelines for ABAP programming?
Thanks in advance for your help.
Regards,
Jarmo Tuominen

Naming convention guidelines for ABAP programming is available in here: [Manage Successful Customer Development|https://websmp206.sap-ag.de/~sapidb/011000358700004444532001E].
Naming Data Types and Objects
The names of data types and objects have the form: <Classifier>_<Data type>_<Descriptor>.
The names of data types and objects have up to 30 characters.
Exceptions: names of input parameters and select options have up to 8 characters, and <Data type> and _ are omitted.
First component: Classifier
T Data type
C Constant
G Global data object
L Local data object
FS Field symbol
P Input parameter
S Select option
P Formal parameter in form
FM Formal parameter in function
Second component: Data Type
<t> Elementary data type, optionally followed by length
C<n> Type C of length <n>
N<l> Type N of length <n>
X<l> Type X of length <n>
D    Type D
T    Type T
I    Type I
P<d> Type P with <d> decimals
F    Type F
WA Work area
IT Internal table
Third component: Descriptor
Use meaningful English names. Later, your code may be maintained or analyzed by a programmer or support consultant who is not familiar with another language.
Use only alphanumeric characters (A-Z and 0-9) and separate words with underscores (_). Hyphens are reserved for separating components in structured data types.
Examples:
G_I_COUNTER (global counter)
T_IT_BOOKING_LIST (type for list of bookings)
G_IT_BOOKINGS (global internal table of bookings)
PSMOKER (input parameter for smoker flag: note omission of data type and _ for brevity)
Edited by: Jarmo Tuominen on Feb 21, 2011 2:13 PM

Components naming convention

Are there any components naming convention guidelines? For example, for text field components id, should that be prefix with textName or suffix with nameText, etc. In tutorials, I have seen both approach.

We compiled some conventions based in engineering input. You can see them at http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/about_components.html#general (see the id row in the table).
In the tutorials, we decided to not strictly follow these guidelines. Our reason was, we wanted the reader to focus on the lesson on hand. We didn't want to waste the users time renaming ids when it didn't really affect the outcome. These are one-time apps and thus the naming of the ids is not as important as with an app that will be worked on by different people over a span of time. Hope that makes sense.

Storage Location Naming Convention without WM!

Dear all
We are facing serious problem in our Storage Location for Raw Material.
We have 4 types of Raw Material Seating (S), Panel (P), Metal (M), Wood (W). And they are all stored under Storage Location: RWSL.
Requirement:
Although we have visual guideline as to which industrial rack will store the type of Material, it is insufficient. We need a more refined storage location down to which BIN of the rack we will put the Raw Material.
Due to limited time and resource, we cannot have WM implemented right now. Thus, we have come out with 2 alternative to overcome this problem:
Alternative 01:
We will use the Fixed Bin field in Storage Data 02 by putting the Bin number assigned to each Rack.
E.g. For Seating material code:SEAT01, we will maintain the Fixed Bin as R12A01/A02, it means this Seating material SEAT01 will be stored at Rack 12, fixed bin A01 or A02.
Question to Alternative 01: Will it cause problem in GR, GR, Transfer Posting and Stock Count?
Alternative 02:
Instead of going into details to put Fixed Bin field in Storage Data 2, we will abandan the existing Storage Location RMSL by introducing new format for Storage Location
Here is the example of Alternative 02:
For raw materials, we will use 4 digits location numbers, consistent with other Storage locations, the 4 digits storage location will start with u201CR _ _ _u201D to represent each location
And,
R _ _ _ is:
R = Raw materials
2nd digit = Division (S= Seating, P =Panel, W=Wood, M=Metal and W=Wood)
3rd digit = Rack Number (A, B, C, Du2026 and etc.)
4th digit = Rack Zone - each rack will broken down into zone, each rack can possibility have 2 to 3 zone. 1 Zone can be 1 colume of the Rack
An example of a possible location and its meaning will be
RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1
RPB3 = Raw materials warehouse, Panel Division, Rack B, Zone 3
The challenge of this is that instead of having 1 Raw Material Storage Location like RMSL, we will have a lot more storage locations each for division of Raw material due to the Rack Number we have as well as the Rack Zone.
Question to Alternative 02:
If we use this alternative, will it impact our future implementation of WM? From design wise, is it feasible?
Please advise what is the best approach and the feasible design on it.
Many thanks in advance.
Edited by: Daimos on May 13, 2009 10:15 AM

Hi, here is the Pro and Co of both approaches:
Method 01: Use existing SLOC and add the Storage Bin info
e.g. SLOC: STM1
         Storage Bin: RSC3, where RS = Rack Seating, C3 = column 3
Pro 01:
It will cause less effort as we only need to use LSMW for material master to add in the Storage Bin data for all material of SCM.
Pro 02:
I have tested out that in TCode MIGO, apart from SLOC, the pertaining Storage Bin data also appear. Based on my discuss with Xian Chen, sometimes they use MB1C(GR), MB1A(GI) rather than MIGO due to speed issue, I will need to check the field status if can have Storage Bin field APPEAR, if can, it will solve the problem
Con 01:
The Storage Bin information will only appear in MMBE (Stock Overview) but will not appear in the standard SAP Inventory Report (e.g. MB52 Warehouse Stock). To view it from SAP Inventory Report, we may need to customize the standard report to show the new field Storage Bin. It needs Abap effort.
Con 02:
We must have a very good naming convention for Storage Bin. And again, in the above example, if a material is put in SLOC STM1 at Storage Bin RA A1 or C4, it will set a very rigid rule in the future if we need to change it, as I fear that one the Storage Bin has been used up. It will not allow us to change (need to do testing to find out)
Con 03:
Do we have the time to define all the Storage Bin for each SLOC? Operation wise, the store personnel needs to design it
Method 02: Use the new SLOC
Pro 01:
RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1. More organized. Easy to tell the material is at which Rack and which Zone of the Rack.
Assumption:
01. we must not have too many rack for one Seating division and also not too many Zone for each
      Division, else it will cause confusion
02. 1 material should stick to 1 Rack 1 zone as much as possible, else later the PP consultant will
     have hard to to perform GI due to too many SLOC assigned to a material.
Pro 02:
In report wise, we are able to show the SLOC in inventory report. No need to enhance the existing inventory report as we do not use Storage Bin.
Con 01:
If there are too many SLOC creation due to it. It may cause problem for PP perform GI as too many selection available for a material. This can be avoided if stick to the General Rule that one material is tied with one SLOC.
Edited by: Daimos on May 16, 2009 5:07 AM

File name naming convention in File Adapter configuration in ID

Hi All ,
I have a query related to xml filename created in IDOC-XI-FILE scenario based on value of one of IDOC field .
The scenario is like this :
I have to send one xml file per store for material master . In this case how can I define my file name with store name in File adapter configuration in ID .
Naming convention should be
<b><storename>_date_masterdataname.xml</b>where store name is one of field of IDOC .
Plz help me .
Thanks in Advance
Regards
Prabhat Ranjan

Hi Prabhat,
take a look at this weblog:
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii
you have to specify variable substitution
(in the file adapter)
and give the path to the store name (in the variable sustitution table)
you <b>file name schema</b> (from the file communication channel can look like this)
%storename%_date_masterdataname.xml
Regards,
michal
Message was edited by: Michal Krawczyk

Is it possible to control the naming convention used by Aperture when importing photos? If so, how

When I import photos from my camera, I have them placed into projects based on the date the photos were taken. However, I do not like the naming convention used by Aperture as it causes the projects to sort into a non-chronologial order. The convention is MMM-DD-YYYY and I want to change it to YYYY-MM-DD. Is it possible in Aperture 3.2.4 to do this?

In the Import panel you can edit the preset for the file name format to "Image year - image month - image day - index" for example; the preset for folder names seems to be gone in Aperture 3,3 - at least I cannot find it any longer. You only seem to be able to enter the folder name manually in the Import panel.

Best practice for naming convention in BI 7.0

Hi All,
Is there a Best Parctice document for naming convention in BI 7.0?
Thanks,
S.B

hi,
chk this links...
http://help.sap.com/saphelp_nw04/helpdata/en/ba/83343ea7ff6a38e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/da/0318025d64a84b94542641ed77ee74/frameset.htm
hope this helps,
partha

Looking for best practice on naming conventions

Does anyone out there have a best practice on naming conventions that they could share.
I'm starting to find the need to create objects and associated variables and actions.
I can see this getting very messy, very quickly and would love to learn if someone has come up with a good set of guidelines that are both easy to follow and make perfect sense. (I know....what a balance to ask for!)
Thanks
Alan

Hi Alan,
Welcome to Adobe Community.
There are couple of things that you can keep in mind while naming objects.
When creating custom text caption styles, be sure to follow the correct naming conventions. Each caption style has a unique name, and you must
use this name at the beginning of each associated bitmap filename. For example, if you create a text caption style named “Brightblue,” the five
bitmap images that constitute the new style should be named as follows:
Brightblue1.bmp, an image with no callouts
Brightblue2.bmp, an image with a callout to the right or upper-right
Brightblue3.bmp, an image with a callout to the left or upper-left
Brightblue4.bmp, an image with a callout to the lower right
Brightblue5.bmp, an image with a callout to the lower left
Flash button-naming conventions
Each SWF button contains three layers: a button, an icon, and an action layer.
The SWF filename consists of the following elements:
Acronym for playback control (“pbc”)
Playback element identifier (“Btn” for button, “Bar” for bar, and so on)
Name of the button (“play”).
Hope this helps!
Thanks!

Inconsistent naming conventions for Adobe Reader in software scan

I just want to see if anyone knows why Adobe's free pdf Reader appears both as "Adobe Reader" AND "Adobe Acrobat Reader". I manage software licenses for an organization of 400+, and it's difficult to know if, for instance Adobe Acrobat - Reader 6.0.2 Update - 6.0.2, should or should not be counted as a purchased license without actually visiting each workstation to verify. I've spoken with our network operations personnel and they confirmed that it is not manually entered by our personnel, but that it is something in the software. ??
Furthermore, why are the naming conventions not consistent even among those that can be identified easily? The list below is what I see when I run a report for all Adobe software on our network.
Adobe Acrobat - Reader 6.0.2 Update - 6.0.2
Adobe Acrobat 4.0 - 4.0
Adobe Acrobat 5 -- SC Install
Adobe Acrobat 5.0
Adobe Acrobat 5.0 - 5.0
Adobe Acrobat 5.0 - 5.1
Adobe Acrobat 5.0 SC Support
Adobe Acrobat 6.0 Professional - 006.000.000
Adobe Acrobat 6.0 Standard - 006.000.000
Adobe Acrobat 6.0.1 Professional - 006.000.001
Adobe Acrobat 6.0.1 Standard - 006.000.001
Adobe Acrobat 7.0 Professional - 7.0.0
Adobe Acrobat 7.0.1 and Reader 7.0.1 Update - 7.0.2
Adobe Acrobat 7.0.2 and Reader 7.0.2 Update - 7.0.3
Adobe Acrobat 7.0.3 and Reader 7.0.3 Update - 7.0.4
Adobe Acrobat 7.0.5 Professional - 7.0.5
Adobe Acrobat 7.0.7 Professional - 7.0.7
Adobe Acrobat 7.0.8 Professional - 7.0.8
Adobe Acrobat and Reader 6.0.3 Update - 6.0.3
Adobe Acrobat and Reader 6.0.4 Update - 6.0.4
Adobe Acrobat and Reader 6.0.5 Update - 6.0.5
Adobe Acrobat Reader 3.01
Adobe Acrobat Reader for Pocket PC 1.0
Adobe Reader 6.0 - 6.0
Adobe Reader 6.0.1 - 006.000.001
Adobe Reader 7.0 - 7.0.0
Adobe Reader 7.0.5 - 7.0.5
Adobe Reader 7.0.5 Language Support - 7.0.5
Adobe Reader 7.0.7 - 7.0.7
Adobe Reader 7.0.8 - 7.0.8
Adobe Reader Chinese Simplified Fonts - 1.0
Adobe Reader Japanese Fonts - 1.0
Adobe Reader Korean Fonts - 1.0
If anyone can answer this, I'd appreciate it. Thanks.

Junlie et al,
Starting with Acrobat 9 (announced on 6/2/08), Adobe will support the new ISO/IEC 19770-2 standard for universal software tagging. The new standard will allow customers to correctly identify the name, version, type and licensing status of Adobe software (starting with the Acrobat 9 family and later on as new versions of the products are introduced later this and next year).
I DO understand your frustration with the in consistencies in the naming of our software, but the problem of software discovery goes well beyond our lack of discipline. This is one of the many reasons why Adobe invested time and effort with the industry group defining the new open standard, and in software asset management in general.
More information about tagging standard can be found here: http://www.agnitioadvisors.com/info/content/view/44/1/
- Juan-Carlos

Sdl_image vs. xf86-input-mouse naming convention

Similar Messages

Maybe you are looking for