Robert Roessler: > I note that scintilla_release_resources in GTK-land is NOT a > per-instance Scintilla call... is this correct, and are there any > other "resources" that do not need to (or *should* not) be set or > initialized on a per-instance basis?
These are end of the whole process calls that are there mostly to allow running under a resource debugger like BoundsChecker or valgrind so you don't see spurious warnings at process end. The resources should be safely released just by exiting the process. The calls may also be useful if you need a very long lived process that can unload Scintilla and release all its resources but I've never tried that. > Put a different way, I am now re-initializing each Scintilla [widget] > instance, doing all of the style_clear_all, set_margin_mask_n, > set_code_page, the style_set_* calls, etc each time a new tab (with > its own Scintilla widget) is created... is this all required, or can > you mention any settings that do *not* need to be done for each new > instance? The Scintilla "properties" facility comes to mind for me, > for instance, as something that might be shared across instances. No, all user visible aspects should be set up again. Its only stuff like caches and locks that is shared and they should be invisible in terms of functionality to your code. Neil _______________________________________________ Scintilla-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scintilla-interest
