|
|
alt-tab-reset.gif (888,926 bytes) |
|
|
Still exists in 1.5.3svn r21584 |
|
|
@william or @jurajF do you fellas have any time to take a peak at this issue? |
|
|
Please fix this before 1.5.3 release :/ |
|
|
Per conversation w/ jghali on IRC <Kunda_> jghali, how would one debug 0013934 ? <jghali> Kunda_, the SE updates its content from current item when its window is activated and update item content when its window is desactivated <jghali> in story editor, just changing font or font size does nto change any text properties, you just modify the text cursor properties <Kunda_> right <jghali> when deactivating SE and activating again, text cursor properties are just lost as SE had to reload text from item <Kunda_> "...reload text from item" ? <Kunda_> what is 'item' here mean? like an object? <jghali> yep, reload text from text object <Kunda_> does SE recognize that it's being deactivated by an alt+tab event ? <Kunda_> could it potentially ? <jghali> it just get a notification from system that it has been desactivated <jghali> i don't see how we could fix this issue unless making the text editor modal again <jghali> which won't happen ... <Kunda_> jghali, so there is _no way_ that the system can differentiate for the SE that an alt+tab event has been triggered? <Kunda_> it's just binary on/off ? <jghali> we just get a system event <jghali> on windows the alt+tab is not even received by scribus <jghali> Kunda, the key combination is processed directly by system <jghali> which in return ask corresponding applications to hide or show its windows |
|
|
Something like this still exists in 1.5.5 and I think it is more serious than the description here might suggest. I am running Scribus on 64-bit Linux: OpenSuSE Leap 15.1 Steps to reproduce: 1) Open a scribus project that already has some text with paragraph styles attached. The style should *not* use the first font in the list of available fonts. 2) Select a text frame and open the Story Editor 3) Click on a word and verify that the font is as expected. 4) Switch to a different virtual desktop or activate the screen-lock then unlock again. (Changing focus to a different app on the same desktop is not enough) 5) Now look at the font dialogue in the Story Editor. It shows the first font in the list of available fonts. It continues to do this whatever text you select. Closing the Story Editor and re-opening it makes no difference. The only way back to correct behaviour is to restart Scribus, suggesting that some critical data-structure has been corrupted. This could be related to bug 0015649 because opening the search dialogue before switching desktops prevents the bad behaviour. |
- Anonymous
