Did you try 86? .80 had a number of regressions.
Darren,
I have a similar app that uses a single tcp connection to talk to monitoring probes. The way I constructed this in WiseJ was to create the tcp connection class as a static in the window_load event – that way there is only ever one connection in the scope of my application (except when the app pool recycles so you may end up with two copies so you will need some code to deal with failures and reconnections).
My tcp class raises events which my windows subscribe too in order to see the probe responses.
Your app will continue to run after stopping debug in Visual Studio because IISExpress continues to run – if you look in the apptray you can see the icon. Stop IISExpress and your app will stop.
HTH
Nic
Hi Harald,
Thanks for letting me now the translation feature was broken. I broke it when I changed MainForm to Page (it was Form previously). It’s fixed now.
Thanks, Frank
It works fine as I wanted
Set this.statusBar1.ShowPanels = false;
We have it set to true by default, which is wrong. The status bar can show either the text or the panels.
The expected behavior in WinForms and Wisej is to apply the localization at creation time.
Hi Tiago,
thank you for the example … but also this example does not work as expected, take a look at the screenshot: I switched from Espanol to English and nothing happened (I tried it with Chrome and Internet Explorer). Maybe a bug of the newest version of wisej 1.4.86.0?
Best, Harald
Hi Harald,
Have a look at InterwayDocs a WinForms/Wisej application that is translated in 4 languages: en/es/fr/pt.
There is a combo box to choose the language. On the Wisej application, the combo box changes the URL and that triggers the ApplicationRefresh event as Luca said. The ApplicationRefresh handler iterates all forms to force the refresh of translations.
In the RibbonBar project change
include: [wisej.mixin.MWisejComponent],
to
include: [wisej.mixin.MWisejControl],
in
wisej.web.ribbonBar.Item.js
Wisej previously was not checking if the control being added actually included the MWisejControl mixin. Now it does.
The behavior is correct. Controls are localized on creation, see InitializeComponent(). We are adding an event Application.CultureChanged to let an app decide what to do in case the language changes later. Now you can detect the language change in ApplicationRefresh in case it’s changed by altering the URL. Otherwise it’s not needed since Wisej detects the language from the browser.
In the web world servers have no way to update the browser without a request initiated by the browser. And background tasks (threads) have no connection to the the client. Wisej uses a websocket connection to allow the server to push the updates to the client, but you have to have websocket supported by your server.
Try this:
http://demo.wisej.com/ProgressSample
There is also more here:
https://wisej.com/docs/html/BackgroundTasks.htm
https://docs.microsoft.com/en-us/aspnet/signalr/overview/getting-started/supported-platforms
We have support for data-wisej but it’s not completed. If you look inside wisej.js you will find the function createEmbeddedControls. It will work like this:
<div data-wisej=”MyApp.CoolTreeView”></div>
It creates in inline root (qooxdoo widgets are hosted on a root container always, there is one for the entire application and then you can have inline roots for custom element, which is what we use to host controls in datagrid cells) in the div and places the control in there.
If you call Wisej.Core.createEmbeddedControls() manually you can test it. The outstanding issue is the lifetime of the component. Now it’s not rooted to the GC will destroy it.
So, the short answer is not yet. 🙂
Use the e.ColumnIndex, e.RowIndex passed in the event. The CurrentCell is the cell with the focus frame which may not be the one clicked. datagridview[e.ColumnIndex, e.RowIndex].
Hi,
Interesting. I just tried the wisej Sort example and this doesn’t refresh regularly either (on the same work machine).
I did try the sort program at home and this refreshed ok.
So, there appears to be something odd about my development PC!!!
I tried both in IE and in Chrome.
Any ideas, folks?
Thank you
Regards,
Darren
So setting filename in the handler didn’t work, but I’ve since discovered that there is a method on pdf.js that can set the filename:
PDFViewerApplication.setTitleUsingUrl() which takes a URL and then figures out the filename from it.
My problem now is that I cannot figure out how to access the PDFViewerApplication object. I’ve tried to do this from OnWebRender and from other event using Eval(string.Format(“PDFViewerApplication.setTitleUsingUrl(‘{0}’);”, Application.Url + fileName)); but I always get “PDFViewerApplication is undefined”
Unfortunately I’m not a js programmer so my understanding is very limited. Can anyone point me in the right direction?
TIA
Nic
Hi Luca,
sorry that was not the question.
When I switch the language at runtime (with URL or …) the translation of the label (that I have made in design mode) is not shown … the translation of the form’s caption however is shown … it seems to be that the translation of all controls within a form are not switched automatically.
And I found another behaviour: When I start the browser-session with URL “…/?lang=en” (default language otherwise is German) then it works. But when I change the URL to “…/?lang=de” (I do not close the browser’s session before) then the label’s contents are not switched to German.
Best, Harald
there you are …
You can use web.config with our owin implementation, like in IIS. If you are bundling everything in a single exe you can either extract web.config from embedded resources or you can change the global web config in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config.
Thanks both,
But still slightly confused. To use Application.Download I need to get the PDFViewer to call my handler. I’ve set:
pdfViewer1.PdfSource = this.GetPostBackURL();
but when the viewer is rendered it displays the same error as in my original post:
PDF.js v2.0.493 (build: c5c06bf5)
Message: PDFDocument: stream must have data
and my ProcessRequest(HttpContext context) handler is never called.
I’ve built and attached a simple example. You will see that the NotImplimentedException in the handler is never reached.
