Using
[ main 0 exit ] with-ui
where ```main``` is my application I get what I need.
Thank you
Am Thu, 10 Nov 2016 16:35:43 +0100
schrieb Jon Harper :
> You need to initialize the UI. the with-ui (
> http://docs.factorcode.org/content/word-with-ui%2Cui.html ) word
It should work with my suggestion, I had tested it on ubuntu :
#! /home/jon/factor/factor
USING: ui.clipboards ui io namespaces kernel system ;
"B4: " print clipboard get [ clipboard-contents print ] when* flush
[ "AF: " print clipboard get clipboard-contents print flush 0
exit ] with-ui
Am Thu, 10 Nov 2016 07:32:52 -0800
schrieb John Benediktsson :
My platform is Linux. Trying
---
USING:
namespaces prettyprint ui.backend.gtk ui.clipboards
;
init-clipboard clipboard get clipboard-contents .
You need to initialize the UI. the with-ui (
http://docs.factorcode.org/content/word-with-ui%2Cui.html ) word does that.
Note that with-ui setups an event loop and doesn't finish until the
event-loop exists (when you close the last window), so you can call exit
directly to force it to exit.
Maybe
Right now they are commingled and clipboard use typically requires the UI
to be initialized.
But this works, for example on Mac as a script:
USING: io namespaces ui.backend.cocoa ui.clipboards ;
init-clipboard clipboard get clipboard-contents .
What platform are you trying to make this
In the Listener
```clipboard get clipboard-contents```
leaves the clipboard content on the stack.
In a Factor script I get an error. Because UI is not running I think.
Is there a way to read the clipboard content in a Factor script ?
Georg
Hi Chris,
On 2016-11-10 11:03, Chris Double wrote:
> With that I see what you are seeing. Both numbers print out after the
> last thread finishes. It looks like it's buffering in this case. If I
> add a 'flush' then I see them printed after 5 seconds then 10 seconds:
>
>
On Thu, Nov 10, 2016 at 10:00 PM, wrote:
> Any
> more ideas why? Is run-process blocking everyone? Is there some FFI call
> like you mentioned? Where could I start to debug this on my own?
The only difference to what you are doing and what my test did was
you're running as a
I was working through my factor-articles document [1] to update with a
recent Factor version and hit some issues with the distributed
messaging functionality. I've done a pull request here:
https://github.com/factor/factor/pull/1744
The issue was that for distributed messaging it really requires
Hi John,
On 2016-11-08 22:38, John Benediktsson wrote:
> There are a lot of ways to solve the problem, but without knowing more
> about what you're looking for, I'll just leave these here.
I spent the last half hour reading your code, running it and examining
the vocabularies. Very helpful,
Hi Chris,
On 2016-11-08 23:58, Chris Double wrote:
> I tried to duplicate the basics of your code with the following:
>
> self '[ "bash -c \"sleep 10\"" run-process drop 1 _ send ] "1" spawn
> self '[ "bash -c \"sleep 5\"" run-process drop 2 _ send ] "2" spawn
> receive
>
> This will spawn two
11 matches
Mail list logo