[Oberon] PO2013 - System.CloseTrack / System.ExtendDisplay

[Jörg Straube]

The handling of multiple screens/desktops is a function of the OS.
If ETHO - being a complete OS - should support multiple screens/desktops we would have to implement this multiscreen functionality in ETHO. This is not done yet. If so, the frames with the same name will be fully synconized even if on different screens.

However your described setup is totally different: You start three different ETHO instances on top of a Linux OS. So you run three different Guest OSes (namely ETHO) on top another Host OS (namely Linux). This is called virtualization.
In this setup you can not expect that the GuestOSes syncronize files.

br
Jörg

> Am 15.05.2019 um 01:32 schrieb eas lab <lab.eas at gmail.com>:
> 
> Wojtek wrote:-
>> Imagine three or more tracks on top of each other..
>> Imagine CTRL-N cycling forward to the "next track", CTRL-B cycling back.
>> Being able to cycle through a linked list of tracks without closing them
>> will provide for a poor man multiple desktop.
> 
> Yes! Screen area is often a limiting factor.
> Imagine a project starting with files/userFrames A1,B1,C1 on a single <screen>.
> Later is has evolved to having 3 Screens, each with multiple UserFrames:
> [perhaps the SystemTrack stays constant?]:
> S1: A1, A2, C1, C3
> S2: B1, B2, A4, C4
> S3: A5, C2
> 
> Now, as in real-life, for directory-trees, the user may want to rearrange:
> considering which frames need best be seen together; to get:-
> S1: A1,A2,A3,A4,A5
> S2: B1,B2, A3
> S3: C1,C2,C3,C4, A3
> and per ETHO, all same-named Frames are syncronised/identical.
> 
> Currently under linux, [I don't know about M$pook] launching an ETHO in
> each of 3 destops, gives 3 independent/unsyncronised A3 files for the
> above scenario. Big problem: which I have with multiple desktops.
> 
> ==crg.
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon