Re: wxGlade GUI improvement

"Brendan Simon (eTRIX)" <[email protected]>
Newsgroups gmane.comp.python.wxglade
Organization eTRIX pty ltd
Message-ID <[email protected]>
The wx.SP_LIVE_UPDATE style works well !!

I couldn't find any other sash style that wasn't very thin, except for
the 3DSASH.  I think having the ugly sash is better than a thin sash
(which is not obvious).

The wxPy demo has splitter windows, with thicker sash but no circle. 
Maybe that's worth looking at?  Might be just thin handle with
spacing/border around contents of panes?

The MDIWindows / `MDI with Sash Windows demo` also sahses with no circle
(might be the same as wxPy demo)?

The AUI_DockingWindowMgr (wxPy demo) is another alternative too.  It's
very flexible and the various panes/windows can be
docked/undocked/repositioned how ever the user wants.  It has the
circles in the sashes (maybe they can be removed?)

Finally, another option might be to use `wx.CollapsiblePane` instead
(see wxPy demo)?  That way you can toggle the widget tools pane in/out
of view as required (and the property pane too if desired, though I
imagine it's more useful to keep it open)

Brendan.

------------------------------------------------------------------------

On 26/5/18 4:31 am, Dietmar Schwertberger wrote:
> The sash handles (or whatever they're called) sort of work, but not
> well (on Mac at least).  When I drag the window isn't updated until I
> release the button, so I can't see the what it will look like until I
> release the drag operation.
>
> I will add wx.SP_LIVE_UPDATE for all platforms. That seems to work well.
>
>> The sash handle also looks non-mac like to me.  It looks wide and and
>> oldish (to me).  But that's a minor thing at this stage.
> On Windows 10 the default splitter style results in an invisible sash
> that's a few pixels wide. It's OK, but you need to know that there's a
> splitter.
> I agree that on Mac OS it looks clumsy. I have just tried some styles,
> but I could not find a good one.
> The wx.SP_THIN_SASH style is too thin, I think. It seems to be one
> pixel only.
>
> Maybe you want to experiment a bit and provide feedback.
> The relevant code is also in wxGladeFrame.__init__:
>
>         style = wx.SP_3D  # default, identical to wx.SP_3DBORDER |
> wx.SP_3DSASH
>         # style = wx.SP_LIVE_UPDATE | wx.SP_NOBORDER |
> wx.SP_THIN_SASH  # alternative
>         self.splitter1 = wx.SplitterWindow(self, style=style)
>         self.splitter2 = wx.SplitterWindow(self.splitter1, style=style)
>         self.palette = wxGladePalettePanel(self.splitter2)
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
wxGlade-general mailing list
wxGlade-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/wxglade-general
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.