All Answers

Try creating an instance and calling async on it:

Dim g As Wisej.Ext.Geolocation.Geolocation
 Dim Position = Await g.GetCurrentPositionAsync()

Hope that helps.

Best regards
Frank

Hi Eric,

Thanks for reporting!

This issue is fixed and logged as #1881 (https://www.wisej.com/issues/).  The fix will be available in the next release!

Best regards,

Levie

Hi all,

For those in need for vertical writing, I’m sharing here how I implemented it :

Add a StyleSheet component to the form.

In the StyleSheet “styles” property add this code :

.rotated270 { writing-mode: tb-rl; transform: rotate(-180deg); }

Add i.e a Label, set it’s “AutoSize” property to “false”

Due to the Stylesheet component, now you have a property attached to the label “CssClass”, let’s type the name of the style we defined “rotated270“.

For some controls, as soon as you start resizing it in the designer, the designer will show you the control with the vertical text.

For others like a textbox, it isn’t the case, but at least you can visually place your component.

Sometimes you have to play with the property “TextAlign” to get the wanted result.

Some other components like Listview and combobox need the addition of a”rotation” component instead of the “stylesheet” component.

In that case you define the angle into : rotation -> RotateZ=-90

I prefer to use as much as possible the stylesheet, because when you start using the rotate component, exact positioning becomes really tricky. At time of writing, it doesn’t support docking, and you have to try and fail the transform using the “origin” property, i.e “0% 100%” …

So, the bottom line is : not the perfect world, but at least you can achieve decent designs.

Regards.

Hi Angelo,

Thanks for reporting!

This issue has been logged as #1880 (https://wisej.com/issues/). A fix will be available in the next release!

Best regards,

Levie

Hi Luca,

Thank you, I’d like to define this by me and not use the default server locale.

Meanwhile, how could I define my own regional settings?

We don’t need the old paging. The datagrid control in Wisej uses virtual scrolling and an advanced cache system to render only the visible rows.

The iFramePanel control (and widget on the client) is a DIV element that contains an <iframe> element. It’s not the content of the iframe element, which is another document and window domain. Wisej exposes the getWindow() and getDocument() client side methods to retrieve the iframe’s window and document.

You’d have to call the javascript functions using this.getWindow() as the target.

Also, if you use iFramePanel1.Eval) the target is already iFramePanel1. It should be iFramePanel1.Eval(“this.getWindow().multiply(2, 3)”); Assuming that the iframe loads a document with a javascript function “multiply”.

If you want to use Call() instead on the iFramePanel1 control, you need to assign wrapper javascript functions to iFramePanel1. See the JavaScript component. Then you can do this in js (where “this” is iFramePanel1):

this.multiply = function(x, y) {

return this.getWindow().multiply(x,y);

}

And in C#

iFramePanel1.Call (“multiply”, 2, 3, (result) => { … });

or

int result = await iFramePanel1.CallAsync(“multiply”, 2, 3);

Hi,

This is a known issue with Wisej 2.0.24 when creating new projects.

Please try this solution:

1. Remove and readd references to Wisej.Framework and Wisej.Framework.Design (add it if it’s not there from “C:\Program Files\IceTeaGroup\Wisej 2\bin”)
2. Rebuild your solution
3. Completely close and reopen Visual Studio

Let me know if this works for you.

Sorry for the inconvenience.

Best regards,

Levie