CTRL-ALT-F (Find) doesn't search for the given text string in hidden layers

[Big Frank]

CTRL-ALT-F (Find) doesn't search for the given text string in hidden layers
if this is intentional, why?
if it isn't, please could you fix it, since spellchecking just the initially visible part of a document , thinking you are spellchecking all layers, could prove to be at best embarrassing at worst a client relations disaster
if it's only happening to me, oh well, that figures
thanks

frank

[steve.ledger]

I can repeat that.
Maybe an oversight?

[mwenz]

Should it then unhide any and all hidden layers to be able to display the find?

[Acorn]

I've always clicked on the All layers / object visible icon in the Page & Layer Gallery when I search.

Acorn

[mwenz]

I've always clicked on the All layers / object visible icon in the Page & Layer Gallery when I search.

Acorn

Tis what I have done when I had hidden layers with text.

[Big Frank]

it is clearly a usability design flaw
there is no reason why you would create a layer, hidden or not, to intentionally retain its spelling errors
the purpose of a hidden layer is to be revealed
but since there is a workaround that requires a user to remember that search and replace won't work unless show all layers is selected it won't be addressed
how about a xara roadmap to fix these long-known bugs
not any time soon i'll bet

[Acorn]

it is clearly a usability design flaw
there is no reason why you would create a layer, hidden or not, to intentionally retain its spelling errors
the purpose of a hidden layer is to be revealed
but since there is a workaround that requires a user to remember that search and replace won't work unless show all layers is selected it won't be addressed
how about a xara roadmap to fix these long-known bugs
not any time soon i'll bet

BF, thank you for extending the discussion.
My workflow includes "Check spelling as you type". I know I'll will miss something; don't we all?
What should the application do when it finds an error within a hidden layer? It would have to unhide that layer, then you might correct the mistake and then what? Only hide the layer on going to the next spelling mistake? What happens if you decide to tweak the text box position? Should the layer now be considered to be in play?

I don't find unhiding all layers as onerous.
On exporting, I use small utilities to create a concordance of all text in the HTML file (just to really check).
I also force myself to click through all links and the tooltips don't get spell-checked, which I consider to be more heinous.

What Xara should do is better explain how the tools should be used together.

Acorn

[Big Frank]

This isn't about spelling errors and I don't know why I gave you that worm, an error on my part.

What should the application do when it finds an error within a hidden layer? It would have to unhide that layer

Not at all.

You know you have a particular word on a particular layer in the document but you cannot remember on which page and on which layer and you have something to add to that paragraph. So you Ctrl Alt F and search for that word -> the application currently takes you to that word, opening the layer it's on and highlighting on the screen the word in question. Unless it's on a hidden layer.

That is an omission.

On finding it on a hidden layer the application should simply take you to the layer, which cannot be hidden if you're on it. That's how it should work.

But what's even worse is that if you were on a hidden layer that obstructs the word in question which is on a visible layer when you initiate Ctrl Alt F, it also doesn't find the word! You can click Unhide all layersbut it still won't find the word you're looking for because, with all layers being visible, the hidden layers obstruct the word and Xara now doesn't see it.

There is no logical reason for Xara to deem you didn't want to find the word because it is on a hidden layer. This is a bug or, as Steve said more politely, an oversight. I'm also pretty certain it won't get fixed.

[handrawn]

if a layer is hidden then for it to be hidden from the search makes sense, hidden does not necessarily mean just 'visually'

I can see where you are coming from Frank, but I prefer it the way it is [in fact I'd prefer not to be able to add things to a hidden layer either]

[Acorn]

This isn't about spelling errors and I don't know why I gave you that worm, an error on my part.

All I was trying to indicate is that finding a spelling error and a search use similar approaches and neither work on hidden layers.

Acorn