Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Balloon warnings can not be disabled #1881

Closed
Maximus5 opened this issue Jul 31, 2015 · 7 comments
Closed

Balloon warnings can not be disabled #1881

Maximus5 opened this issue Jul 31, 2015 · 7 comments

Comments

@Maximus5
Copy link
Owner

Originally reported on Google Code with ID 1882

Required information!
OS version: Win7/SP1/x64
ConEmu version: 150119a

*Bug description*
ConEmu shows a balloon warning message for double bound hotkeys even if the balloon
messages are disabled. Since the double bound hotkey WIN+C is intended the shown balloon
message pops up each time ConEmu is started.

Reported by pfeiffer@tzi.de on 2015-01-27 17:46:45


- _Attachment: ConEmu-1.png
![ConEmu-1.png](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-1882/comment-0/ConEmu-1.png)_ - _Attachment: ConEmu-2.png
![ConEmu-2.png](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-1882/comment-0/ConEmu-2.png)_
@Maximus5
Copy link
Owner Author

Shown option affects only settings dialog hints.
But you are talking about error message.
You need to fix your hotkey to avoid it.

Reported by ConEmu.Maximus5 on 2015-01-27 19:09:31

@Maximus5
Copy link
Owner Author

I need to start ConEmu by WIN-C (thus I registered an external global hotkey) but on
the other hand I need ConEmu to actually close the window on closing the last tab.
Since I haven't found any way to let ConEmu react on WIN-C even if the ConEmu window
is actually closed (not minimized to TSA) my only idea was to register an additional
global hotkey.

Is there any option to keep ConEmu react on Win-C even if the window is actually closed?

Reported by pfeiffer@tzi.de on 2015-01-27 19:27:22

@Maximus5
Copy link
Owner Author

Ok, I got it by using /ShowHide for the external hotkey and unbounding the key inside
ConEmu! :-)

Unfortunately now there is a significant delay of 1-2s if minimizing the ConEmu window
by using the hotkey. I think that depends on the external call (ConEmu needs to be
launched each time). 

PS: Starting ConEmu the first time needs ~1s here too. I guess this is by design?

Reported by pfeiffer@tzi.de on 2015-01-27 19:42:55

@Maximus5
Copy link
Owner Author

Your question is illogical.

If you want to have TWO ConEmu instance, how do you think they can handle one exact
hotkey for minimize/restore?

If you want to have ONE ConEmu instance, you'll not see warning about duplicate hotkey.
Of course unless it is already hooked by another app (exactly as balloon says).

And delay is expected. You may examine LogFiles to see what happens when you run second
instance and check timings.

Verdict. Errors must not be disabled.

Reported by ConEmu.Maximus5 on 2015-01-27 22:05:31

@Maximus5
Copy link
Owner Author

No, I do not want to have TWO ConEmu instances. I want to use an external utility programm
that maintains several global hotkeys. This utility registers WIN+C as global hotkey
to launch ConEmu whenever I want (even if ConEmu is not running at all). But if ConEmu
is already started my intention was to just show ConEmu instead of launching it again,
thus I activated the WIN-C hotkey in ConEmu settings as well (leading to the known
error message balloon). 

Anyway I haven't known that /ShowHide argument and after disabling the WIN+C hotkey
in ConEmu and passing the /ShowHide argument from my global hotkey handler everything
is fine now!

Thanks for your support!

Reported by pfeiffer@tzi.de on 2015-01-28 14:39:40

@Maximus5
Copy link
Owner Author

If Win-C is already hooked by another hotkey manager it's impossible to hook it in ConEmu.
So you get lags.

Reported by ConEmu.Maximus5 on 2015-01-28 14:53:34

@Maximus5
Copy link
Owner Author

Reported by ConEmu.Maximus5 on 2015-01-28 14:55:11

  • Status changed: Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant