Wow this upcoming update sounds really promising with new UI elements and UIBuilder changes/additions.


Wanted to say thanks for seeking our opinions and working with us.
Cheers! :D

While you are doing so much work on UIbuilder recently, I know I already suggested it a while ago but I still would love an option to toggle smooth/small fonts within UIbuilder. Since the game's default is smooth fonts and UIbuilder only shows non-smooth fonts it always makes it impossible to properly position text elements in UIbuilder.

Non-smooth fonts/UIbuilder view:


Smooth fonts/ingame view:


How do you do internally for localized text strings? Do you do the windows first and force translators to stick within the sizes you set or is it the other way around? If the longest possible localized string could be shown in UIbuilder that would be grand.

I second, third, fourth, and fifth this request.

I can look into this to see how easy it would be.

We never really know how much space a localized string will take. The general rule of thumb is to leave 30% extra space. Russian and German seem to be the worst when it comes to long translations.

If something doesn't fit, our international department has been modifying the UI files and maintaining their own separate versions for each language. I'm trying to get away from this by having them tell me when elements aren't large enough so I can adjust them in our original source files.

It's not so much a UI Builder change, but I just wanted to drop this in and hope you could take a look at it one day.

Would it be possible to get /camp account to camp to the login window (with account, pass, char, and server) that you get if you load the game directly (ie skipping the patcher)?

I use UIBuilder a lot. I'm not sure I could do interface pieces by just editing the xml code directly. But there is one small annoyance that I would like to see changed. In the properties area of the UIBuilder window there are two columns. The entry and the data for that entry. When you resize the the UIBuilder window these columns resize dynamically. I would like the resize of the columns to be manual. The problem I'm having is when I am adding a long command to one of the ONwhatever entries it quickly runs out of room. And when I resize the window to see more, I end up with a huge blank area on the left column.

So it would be nice if the columns did not resize automatically.

You do know that you can double click the event script column to get a much larger multiline edit box, right? I know I missed that at first when starting out.

Thanks, in fact I didn't know about that. Well it's a bit better accept for one thing the properties box can't be resized and there is no word wrap, so again if I have a long command I have to scroll back and forth. I'm not trying to be to nit picky, but... I guess there are some people you just can't please. :)

No I understand, that's exactly one of the reasons why I very rarely use UI builder, I'm ten times more productive with a customizable text editor. :)

I'm pretty much the same way, but I use UIBuilder only for the basic layout and design. The actual editing later is done outside of it. It's so much easier/faster to change the code when using a text editor. I use to use UIBuilder like 90% of the time, but now I'm using Notepad ++/Dreamweaver around 90% of the time.

I took a look at Notepad++ and it's cool. But as for Adobe Dreamweaver $400 is a bit out of my price range to just do some EQ2 interface pieces. But as long as Rothgar is in the mood to make changes to UIBuilder I thought I might as well put in my suggestion.

Has anyone else noticed that in latest version of UIBuilder the visible option is a bit inconsistent. What I mean is that every now and again the visible button doesn't work, it's grayed out. And UIBuilder is adding "visible=false" to some lines.

I haven't tried to document the specific instances yet cause I wanted to check if it was just me.

It sounds like maybe you don't have the item selected when hitting the visible button. Sometimes what happens is that the item is selected in the UI and you get its properties in the property list. Then the item gets deselected in the UI, but its properties are still displayed in the list. When this happens, changes made to properties dont affect the obect.

I know, this is an old thread, but I wanted to ask if there are still some string manipulation functions in the work or not.

I love dragowulf spell timer window, but as it does not seem, that the UI will actually read the UTF8 files as UTF8 I would like to modify the window, I need to fine a workaround. (The HTML code corrupts the UI so I can't even load it.)

My idea was to check for the beginning and the ending of the name so that I can use these two checks for a name with German special characters in the middle. It would also help with spell chains, as you would not need to include the spell number in the name.

Or is support for LUA still in the works, as that should support this and many more options.

p.s. German special characters nor supported by the UI:
ä - ä
Ä - Ä
ö - ö
Ö - Ö
ü - ü
Ü - Ü
ß - ß

HTML entities have no relevance in XML. Also UTF8 does load and string comparisons are the only operation which works with non-ASCII characters. See e.g. the ProfitUI subclass detector for an example.

Hmmm ....

I tried "Böswillige Hetzrede VI" and "Buße VII" and both are not working. :confused:

Assuming you saved as valid UTF-8 then it might be drago's code (which I have not checked). You cannot perform any other operation with non-ASCII except for a comparison, this includes that you cannot copy the non-ASCII to another element for the comparison. The only way it works is how it's done in ProfitUI, i.e. the non-ASCII written in the XML on the line which does the comparison.

Well the settings include is a text, so could that be the problem?

Hmmm I 1st tried it with ConText, which normally writes valid UTF-8 files and also acknowledged the file as UTF-8. But after your posts I also tried Notepad++ and it seemed to work then. So in some way ConText did not use proper UTF-8.

So it's my fault. Thanks for your help never the less. :-/