In a proper systemd user session setup, enlightenment_start will be
gone. That is still not doable today and as I plan to roll more feature
in EFL regarding systemd, we need to prevent enlightenment to believe
it is the process started by systemd.
* e menus are now drawn directly onto the compositor canvas
* menu theme now requires at least one part which allows mouse events in every menu group (YOUR MENUS WILL NOT WORK IF YOU ARE USING A THEME WHICH LACKS THIS!!!!!!!)
* menus now also report dangling/zombie menus with slightly more accuracy now
This force the command to be run with exec and prevent them
for staying alive after startup or restart.
Signed-off-by: Cedric BAIL <cedric.bail@free.fr>
_populate_channel_editor:
use app->sys_card_name instead of
e_mod_mixer_card_name_get _populate_channels:
select default channel or first one
_create_cards:
do not reselect card and channel
e_mixer_app_dialog_select:
cleanup, remove unused _find_card_by_name and _find_channel_by_name
_mixer_popup_cb_mixer:
do not modifiy current selection on popup
capabilities is a bitmap with the following defined bits:
E_MIXER_CHANNEL_CAN_MUTE 0x01
E_MIXER_CHANNEL_IS_MONO 0x02
E_MIXER_CHANNEL_HAS_CAPTURE 0x04
E_MIXER_CHANNEL_HAS_PLAYBACK 0x08
E_Mixer_Channel is only used within audio subsystems
e_mod_mixer_channel_info_get_by_name returns a E_Mixer_Channel_Info
use e_mod_mixer_channel_info_free to free a single channel_info
When we call "grid_set" (as a result of the grid object moving or
resizing), we should update the monitor position text.
Signed-off-by: Christopher Michael <cp.michael@samsung.com>
Some people have reported that resizing is difficult, or that they
could not get to the max resolution of their monitor(s). Skipping the
refresh rate check during resolution finding fixes that ... With a big
fat Gotcha !!! because now after changing resolutions, the refresh
rate May not match what was previously selected....
So, as a word of CAUTION: After you set a resolution you should now
Verify your Refresh Rate before Applying, else you may be getting an
undesirable rate :/
Signed-off-by: Christopher Michael <cp.michael@samsung.com>
previously this was done in such a way that if the "owner" stacking object of an injected object was restacked, the injected object would remain at its original stacking level since it was not tethered to anything and did not have X managing stacking. now comp will anchor injected objects to the stacking container window and adjust stacking as needed for them
fixes shelf stacking in some cases