why spotter shows up when I type enter in the inputfield of the finder?
Hi guys you cannot imagine the amount of energy I'm losing because of the flux of the tools. why spotter shows up when I type enter in the inputfield of the finder? Is it on purpose? This is 5 times that I'm redoing a videos for the mooc. :( Stef
On 15-02-16 10:48, stepharo wrote:
This is 5 times that I'm redoing a videos for the mooc. :(
Isn't it amazing (and/or terrible) what kind of, and how many, little issues you tend to find when shooting a video/screencast to explain something? Every time I've made a screencast I've found things that first needed fixing or working around. Stephan
I'm so fucking sad.... These kinds of glitches are killing my fun and energy. I lost again one hour trying to produce a video for nothing. Stef Le 15/2/16 11:24, Stephan Eggermont a écrit :
On 15-02-16 10:48, stepharo wrote:
This is 5 times that I'm redoing a videos for the mooc. :(
Isn't it amazing (and/or terrible) what kind of, and how many, little issues you tend to find when shooting a video/screencast to explain something? Every time I've made a screencast I've found things that first needed fixing or working around.
Stephan
On 15 Feb 2016, at 11:59, stepharo <stepharo@free.fr> wrote:
I'm so fucking sad.... These kinds of glitches are killing my fun and energy. I lost again one hour trying to produce a video for nothing.
The question is: Do we stop changing and declare Pharo as finished? I do not know how to change things and at the same time stay stable⦠e.g. we could have not switched to use the new editor and we would have had much less problems⦠What is clear is that *if* we change there *will* be problems. It is not possible to change and then have no problems. Marcus
On Mon, Feb 15, 2016 at 10:48 AM, stepharo <stepharo@free.fr> wrote:
Hi guys
you cannot imagine the amount of energy I'm losing because of the flux of the tools. why spotter shows up when I type enter in the inputfield of the finder?
I just tried to reproduce that but for me this does not happen. Marcus
Lucky you. Le 15/2/16 12:16, Marcus Denker a écrit :
On Mon, Feb 15, 2016 at 10:48 AM, stepharo <stepharo@free.fr <mailto:stepharo@free.fr>> wrote:
Hi guys
you cannot imagine the amount of energy I'm losing because of the flux of the tools. why spotter shows up when I type enter in the inputfield of the finder?
I just tried to reproduce that but for me this does not happen.
Marcus
On Mon, Feb 15, 2016 at 5:48 PM, stepharo <stepharo@free.fr> wrote:
Hi guys
you cannot imagine the amount of energy I'm losing because of the flux of the tools. why spotter shows up when I type enter in the inputfield of the finder? Is it on purpose? This is 5 times that I'm redoing a videos for the mooc. :(
I can't make this happen in 50581 - 32-bit Linux. Except shift-enter in Finder input field still brings up Spotter. My first thought is maybe your shift key is somehow stuck. An aside: I thought to check behaviour by holding <shift> after evaluating... 2 second wait. InputEventSensor default shiftPressed inspect but inspector shows false. Is this expected? cheers -ben
Except shift-enter in Finder input field still brings up Spotter. Spotter is a global key-bind meaning that any user of km-dispatcher will by default bring up spotter on shift-enter... Perhaps it would be better to move this to those that actually uses it; in the WorldMorph bring up the default spotter, in Nautilus bring up a spotter with entries based on the context, etc..?
Forking it shows the expected result, but the input fetcher is running its own thread so this information should be available even though the UI is blocked by the wait ? [2 seconds wait. InputEventSensor default shiftPressed logCr ] fork. ---- Delay delaySchedulerClass. " DelayMicrosecondScheduler " Should not one of the experimental ones be the default scheduler class? https://pharo.fogbugz.com/f/cases/13756/Delay-scheduling-deadlock. "Delay initialize" sets the default one to DelayMicrosecondScheduler, and I guess it was re-initialized for the new session manager. Best regards, Henrik -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Ben Coman Sent: Monday, February 15, 2016 12:39 PM To: Pharo Development List <pharo-dev@lists.pharo.org> Subject: Re: [Pharo-dev] why spotter shows up when I type enter in the inputfield of the finder? On Mon, Feb 15, 2016 at 5:48 PM, stepharo <stepharo@free.fr> wrote:
Hi guys
you cannot imagine the amount of energy I'm losing because of the flux of the tools. why spotter shows up when I type enter in the inputfield of the finder? Is it on purpose? This is 5 times that I'm redoing a videos for the mooc. :(
I can't make this happen in 50581 - 32-bit Linux. Except shift-enter in Finder input field still brings up Spotter. My first thought is maybe your shift key is somehow stuck. An aside: I thought to check behaviour by holding <shift> after evaluating... 2 second wait. InputEventSensor default shiftPressed inspect but inspector shows false. Is this expected? cheers -ben
Hi,
On Feb 15, 2016, at 1:43 PM, Henrik Nergaard <henrik.nergaard@uia.no> wrote:
Except shift-enter in Finder input field still brings up Spotter. Spotter is a global key-bind meaning that any user of km-dispatcher will by default bring up spotter on shift-enter... Perhaps it would be better to move this to those that actually uses it; in the WorldMorph bring up the default spotter, in Nautilus bring up a spotter with entries based on the context, etc..?
Exactly. I argued for this a long time ago and I still think it would be the right thing to do. Doru
Forking it shows the expected result, but the input fetcher is running its own thread so this information should be available even though the UI is blocked by the wait ?
[2 seconds wait. InputEventSensor default shiftPressed logCr ] fork.
---- Delay delaySchedulerClass. " DelayMicrosecondScheduler " Should not one of the experimental ones be the default scheduler class? https://pharo.fogbugz.com/f/cases/13756/Delay-scheduling-deadlock. "Delay initialize" sets the default one to DelayMicrosecondScheduler, and I guess it was re-initialized for the new session manager.
Best regards, Henrik
-----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Ben Coman Sent: Monday, February 15, 2016 12:39 PM To: Pharo Development List <pharo-dev@lists.pharo.org> Subject: Re: [Pharo-dev] why spotter shows up when I type enter in the inputfield of the finder?
On Mon, Feb 15, 2016 at 5:48 PM, stepharo <stepharo@free.fr> wrote:
Hi guys
you cannot imagine the amount of energy I'm losing because of the flux of the tools. why spotter shows up when I type enter in the inputfield of the finder? Is it on purpose? This is 5 times that I'm redoing a videos for the mooc. :(
I can't make this happen in 50581 - 32-bit Linux. Except shift-enter in Finder input field still brings up Spotter. My first thought is maybe your shift key is somehow stuck.
An aside: I thought to check behaviour by holding <shift> after evaluating... 2 second wait. InputEventSensor default shiftPressed inspect
but inspector shows false. Is this expected? cheers -ben
-- www.tudorgirba.com www.feenk.com "Every now and then stop and ask yourself if the war you're fighting is the right one."
Have not problems here ... Pharo5.0 Latest update: #50581 Ubuntu 14.04 On 15.02.2016 10:48, stepharo wrote:
Hi guys
you cannot imagine the amount of energy I'm losing because of the flux of the tools. why spotter shows up when I type enter in the inputfield of the finder? Is it on purpose? This is 5 times that I'm redoing a videos for the mooc. :(
Stef
may be my keyboard baterry is the problem. I have no idea but I could reproduce it. Now I changed image. Just lost time. Stef Le 15/2/16 13:43, Volkert a écrit :
Have not problems here ...
Pharo5.0 Latest update: #50581 Ubuntu 14.04
On 15.02.2016 10:48, stepharo wrote:
Hi guys
you cannot imagine the amount of energy I'm losing because of the flux of the tools. why spotter shows up when I type enter in the inputfield of the finder? Is it on purpose? This is 5 times that I'm redoing a videos for the mooc. :(
Stef
participants (7)
-
Ben Coman -
Henrik Nergaard -
Marcus Denker -
Stephan Eggermont -
stepharo -
Tudor Girba -
Volkert