Re: [Inkscape-devel] handling statusbar messages
No, it just means that status bar messages need to be set from places that know which SPView they're operating on behalf of (if any), or less likely that an SPView needs to be passed in somewhere that it currently isn't.
Maybe we need to step back a moment though -- which g_warnings do you want to turn into status bar messages,
"Non-printable character"
and why?
Because the user needs some feedback to understand why a character he typed in (most likely in Unicode mode, but not necessarily) did not appear on the screen.
_________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=dept/features&pgmarket=en-ca&RU=http%3a%2f...
On Sun, 2003-12-14 at 23:24, bulia byak wrote:
No, it just means that status bar messages need to be set from places that know which SPView they're operating on behalf of (if any), or less likely that an SPView needs to be passed in somewhere that it currently isn't.
Maybe we need to step back a moment though -- which g_warnings do you want to turn into status bar messages,
"Non-printable character"
and why?
Because the user needs some feedback to understand why a character he typed in (most likely in Unicode mode, but not necessarily) did not appear on the screen.
That feedback needs to come from SPTextContext, then, for which you can get the appropriate view via SP_VIEW (SP_EVENT_CONTEXT_DESKTOP (thetextcontext)).
If the actual check is done in SPText (I forget if it is), then it needs to have some way of signaling that failure to its caller (an SPTextContext method, in this case).
-mental
participants (2)
-
bulia byak -
MenTaLguY