Author Topic: Some more wxSmith problems  (Read 2917 times)

Offline anwender4711

  • Single posting newcomer
  • *
  • Posts: 5
Some more wxSmith problems
« on: March 19, 2007, 08:09:36 pm »
Besides some of the problems which are described here, I found some other problems when converting some of my wxGlade forms to wxSmith:

- a custom control is shown in the designer or in the preview only as a small black square in the top left corner of the form, although it is handled in the code correctly. When I click on the area where the custom control resides, I can see also the six even smaller black squares, which are shown for a selected control.

- when I change the variable name of an item, it is not directly shown in the resources tree. Sometimes I have to restart Code::Blocks the see the changes happen, sometimes it is enough to change the actual item in the resource tree and then go back to the item where I changed the variable name

- Sometimes it is not possible for me to change the ID of an item. After reopen the specific property dialog the ID always reverted to the default value, for example ID_TOOLBARITEM1. I noticed that this can happen, when you choose an ID which already exists, but this is not the case, when I have that problem. The only solution for me is to edit the wxs-file manually. Unfortunately I cannot se a rule, when it happens.

- According to the problem above it is sometimes useful to give more than one item the same ID, i.e. a toolbar item gets the same ID as an corresponding menu item. It would be desirable, when you have a checkbox for an ID, which let you choose, if you want the ID to be generated or not. With this checkbox it would be also possible to use own predefined ID values.

- At the moment I have no possibility to set my own variable names for menu items and toolbar items. It would be nice if I could to this as in other controls. Support for applying event handlers to menu items or toolbar items would also be nice.

- I defined some custom crontols using wxPanel in wxSmith putting some other controls on it. For some of the controls I need to pass for example the size to the constructor of the panel. With wxGlade it is possible, because the constructor of the panel doesn't contain a Create(parent,id,...) call. The disadvantage of this approach is, that if you change some of the paramters which in wxSmith are passed to the Create() call, these parameters can only be changed in the generated constructor code, which is not managed as in wxSmith. A solution could be, that  for example for the position I could choose between default position, static position and variable name. For the last case the generated code for a panel would look like this:

class MyPanel(wxWindow* parent, wxWindowID id, const wxPoint& pos)
{
  //(*Initialize(MyPanel)
  Create(parent,id,pos,...)
  ...
 //*)
}

This could be done for wxFrame and wxDialog, too.

- For one of my forms I wanted to set the wxCLIP_CHILDREN flag, which isn't supported in wxSmith. I could add it manually in the Style list, but it was obviously not used. It would be nice, if wxSmith supports manually added styles or supports some kind of user defined flags below the predefined flags

For all this problems I found some more or less ugly workarounds, but I would appreciate if I don't need this workarounds. Overall I have to make big compliments to byo for his great job on wxSmith.

« Last Edit: March 19, 2007, 09:37:41 pm by anwender4711 »

Offline byo

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 837
Re: Some more wxSmith problems
« Reply #1 on: March 19, 2007, 10:55:37 pm »
Thanks for feedback. But I've got one request. Please fill bug report at Berlios. Otherwise I could forget about it since I'm working on some bigger feature for wxSmith and may not remember your post after finishing current work ;)

Regards
  BYO

Offline anwender4711

  • Single posting newcomer
  • *
  • Posts: 5
Re: Some more wxSmith problems
« Reply #2 on: March 20, 2007, 12:28:50 am »
Thanks for feedback. But I've got one request. Please fill bug report at Berlios. Otherwise I could forget about it since I'm working on some bigger feature for wxSmith and may not remember your post after finishing current work ;)

Regards
  BYO

New features for wxSmith are always good news. I was a little bit too lazy to register at berliOS  :). I did it now and divided my list above into some bug reports and some feature requests

Offline byo

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 837
Re: Some more wxSmith problems
« Reply #3 on: March 20, 2007, 08:41:30 pm »
Tahnks for all reports. Now even if I'll forget about that, berlios will remember ;)

BYO