Menu
▾
▴
#103 Issues with Recalling Named Subcorpus
Loading a named subcorpus appears to 'freeze' is when the search word does not exist in the selected subcorpus (common given that the default search word is keyword). The interface does not realise that the transmission is ended and the spinner keeps running. This is a UI glitch that needs to be fixed . Another glitch is that when you 'Load Named Subcorpora' [sic] from the menu while having another subcorpus already active, the interface fails to switch to the recently loaded subcorpus. You either
need to clear subcorpus selection before loading the new named subcorpus, or switch subcorpus on the toolbar (next to the search box). Yet another glitch, however, is that sometimes when you switch quickly via the toolbar webcli seems to fail reloading the query, which causes a situation similar to the 'freeze' that happens when you search for a non-occurring keyword. This might have something to do with javascript's faulty thread synchronisation mechanism, but this needs to be investigated. It doesn't happen very often but when it does it is problematic.
There is also the fact that the user has to switch to the relevant corpus if it is not the default SHE corpus otherwise the same thing happens.
