PureBasic Forums - English

zikitrake wrote: Thank you!!!

Oh!, don't worry for this, I always can put a #nxExplorerBar_Container with standar PB TextGadgets.

Really grateful!

Absolutely, I was going to suggest considering that.

There seems to be an error in the nexus source when compiling for tailbite.

Error: undefined symbol nxGadgets_arraybaseclass_getupperbound

The source works as a .pbi file most of the time, however, every now and then it will throw the same error. Any ideas what this could be?

---DELETED---

can you upload the compiled PB lib as long it does not include ESGrid? I still cant get this to work at all.

---DELETED---Sent a PM but it don't work. I don't included so the lib was empty.
I'm so stupid , when I include it I get the same error.

Only works with: Sorry

Nexus will not Tailbite because of the optional parameters in many of the functions which you would attempt to export. You would need to address this first and create quite a few 'dummy' overloaded functions etc.

The point is that Nexus is not intended for use as a user-library as it is primarily for my own use really and I do not use closed user-libs.

As for use as an include file; if there are problems here you'll have to be more specific and tell me with which control etc?

and another request for nxExplorerBar :

a nxexplorerBar_DisableMenuItem() is possible?

Thank you, I love this lib!

zikitrake wrote:and another request for nxExplorerBar :

a nxexplorerBar_DisableMenuItem() is possible?

Thank you, I love this lib!

Nope.



Unlikely I'll be able to add that any time soon because I'm just too busy at the moment.

well, I'll try it myself (or remove/re-add items)

Thank you!

The easiest way will be to adjust the source so that you are able to use nx_SetGadgetItemAttribute() with #nxExplorerBar_ItemType to alter the menu item to a 'description' item. This would effectively disable the item. At the moment this attribute is 'get' only, but it may not be too difficult to alter the code to allow menu items to be converted to description ones and back again etc. When I get time I'll have a look.

Thank you Srod, currently I'm using remove/"re-add" items as you say (changing the item type)

I'll see your code to try your method (change attributes)

Regards,

nxPropertyBox controls.

This control has undergone a major update in the Purebasic 4.3 version (the version of Nexus for PB 4.2 is no longer supported). This is because I am finally using this control in a 'serious' and substantial application and am having to make a few alterations etc.

Changes include :

• Two new creation styles; #nxPropertyBox_EditableLabels and #nxPropertyBox_RemoveControlsWhenResizing. Using the first of these styles allows labels to be edited following a double click etc. The developer can validate all edits etc. Also, you can set the label editing colors etc.
• Added an editable combo type cell.
• Greatly refined the various selector type cells.
• The #nxPropertyBox_ItemUpdated callback message now fires in the case that lables have been edited etc. This message also provides additional information in the case that a selector type cell has been altered etc.
• Added a new callback notification : #nxPropertyBox_ContextMenu. This allows the developer to easily attach context menus to individual cells of a propertybox etc.

In the absence of a user manual, you have to fall back upon the "nxGadgets_Residents.pbi" source file in order to find additional information regarding these changes/enhancements.

I have also fixed some bugs with this control.

nxPropertyBox controls.

This control has undergone another quite major update in the Purebasic 4.3 version (the version of Nexus for PB 4.2 is no longer supported). This has again been driven by my use of this control in a very large application.

Basically, I needed a way of allowing some 'color selector' items of offering a 'default color' option and of thus being able to display colors as well as text (i.e. display a selected color or a string simply saying "Default color" etc.)

This was of course not possible for two reasons; i) the propertybox color selector items could not display text and, more importantly, ii) the Windows color common dialog has no option for a 'default color'.

This has been addressed (indirectly) by making a number of internal alterations to the nxPropertyBox control, most notably the addition of a new callback message : #nxPropertyBox_SelectorItemInvoked. This fires whenever the user attempts to invoke any of the selector items and allows the user to replace the resulting requester with a custom one. In addition, you can now dynamically switch an item's type at will (e.g. from a color selector item to a dynamic text dialog item and back again!) Very useful!

A new nxPropertyBox demo (demo 2) shows all of this working and uses my MenuColorPicker class (included with the demo) to good effect. The result is a custom color item which does exactly as described above (switching from a textual display to a colored image one)! By not 'hard coding' the MenuColorPicker class into Nexus we are of course free to use just about any type of dialog going and to switch items between all the various types.

Hi Srod,

I'm working now on new project with PB 4.30 that use Nexus with NxTreeField

if Im Include the nxGadgets.pbi, then appair a error on the NxtreeField.pbi

Line 916:PtInRect_(): Incorrect number of Parameters.

any idea?

Thanks
jpd

jpd wrote:Line 916:PtInRect_(): Incorrect number of Parameters.
any idea?

I believe you have to use a quad with PB4.30
http://www.purebasic.fr/english/viewtopic.php?t=34860
http://www.purebasic.fr/english/viewtopic.php?t=35443