473,657 Members | 2,680 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

(wxPython) wx.ProgressDial og - how to cancel out of?

I'm trying to use wx.ProgressBar, and the cancel button is not
responding.

Here is a simple program that exhibits the problem:

############### ############### ############### ############
import wx
import time

max = 10
app = wx.PySimpleApp( )
dlg = wx.ProgressDial og("Progress dialog example",
"variables to be shown here",
maximum = max,
style = wx.PD_CAN_ABORT
| wx.PD_CAN_SKIP
#| wx.PD_APP_MODAL
| wx.PD_ELAPSED_T IME
| wx.PD_ESTIMATED _TIME
| wx.PD_REMAINING _TIME
)

keepGoing = True
skip = False
count = 0

while keepGoing and count < max:
count += 1
wx.MilliSleep(1 000)
#time.sleep(1)
newtext = "(before) count: %s, keepGoing: %s, skip: %s " % \
(count, keepGoing, skip)
print newtext
(keepGoing, skip) = dlg.Update(coun t, newtext)
newtext = "(after) count: %s, keepGoing: %s, skip: %s " % \
(count, keepGoing, skip)
print newtext
dlg.Destroy()
############### ############### ############### ############

The dialog looks right when this runs, but....

What's right: I get a progress bar; it includes "Skip" and "Cancel"
buttons; it shows 10 seconds of progress, and updates once per second
with the variables' values on each iteration.

What's wrong is that I can't get clicking on the "Skip" or "Cancel"
buttons to have any effect. Instead, as soon as the dialog displays,
I get an hourglass, and it doesn't matter what I click on. Here's
what the print statements display, consistently, regardless of what I
try to click or whether I click nothing at all:

I:\python>test1 .py
(before) count: 1, keepGoing: True, skip: False
(after) count: 1, keepGoing: True, skip: False
(before) count: 2, keepGoing: True, skip: False
(after) count: 2, keepGoing: True, skip: True
(before) count: 3, keepGoing: True, skip: True
(after) count: 3, keepGoing: True, skip: True
(before) count: 4, keepGoing: True, skip: True
(after) count: 4, keepGoing: True, skip: True
(before) count: 5, keepGoing: True, skip: True
(after) count: 5, keepGoing: True, skip: True
(before) count: 6, keepGoing: True, skip: True
(after) count: 6, keepGoing: True, skip: True
(before) count: 7, keepGoing: True, skip: True
(after) count: 7, keepGoing: True, skip: True
(before) count: 8, keepGoing: True, skip: True
(after) count: 8, keepGoing: True, skip: True
(before) count: 9, keepGoing: True, skip: True
(after) count: 9, keepGoing: True, skip: True
(before) count: 10, keepGoing: True, skip: True
(after) count: 10, keepGoing: True, skip: True

Two oddities here:

1) As I read the docs, the keepGoing variable should be set to True,
unless I click on "Cancel," in which case it should be set to False
(which would end the loop). That doesn't happen. This is really what
I'm most concerned here with.

2) The variable "skip: set to False on the first iteration, and then
set to True on subsequent iterations? Note that this happens even if
no buttons are selected. This is just a weirdness to me, and not my
main concern, but I thought I'd mention it in case it's relevant.

You can see some variations in the commented-out code that I tried;
they did not help.

Relevant software and releases:

OS: Windows XP Home Edition, Version 2002, SP2
Python: ActivePython 2.5.0.0
wxPython: 2.8.1.1 (msw-unicode)

Any help appreciated.
Sep 15 '07 #1
7 6796
On Sep 15, 12:57 am, Terry Carroll <carr...@nosp am-tjc.comwrote:
I'm trying to use wx.ProgressBar, and the cancel button is not
responding.

Here is a simple program that exhibits the problem:

############### ############### ############### ############
import wx
import time

max = 10
app = wx.PySimpleApp( )
dlg = wx.ProgressDial og("Progress dialog example",
"variables to be shown here",
maximum = max,
style = wx.PD_CAN_ABORT
| wx.PD_CAN_SKIP
#| wx.PD_APP_MODAL
| wx.PD_ELAPSED_T IME
| wx.PD_ESTIMATED _TIME
| wx.PD_REMAINING _TIME
)

keepGoing = True
skip = False
count = 0

while keepGoing and count < max:
count += 1
wx.MilliSleep(1 000)
#time.sleep(1)
newtext = "(before) count: %s, keepGoing: %s, skip: %s " % \
(count, keepGoing, skip)
print newtext
(keepGoing, skip) = dlg.Update(coun t, newtext)
newtext = "(after) count: %s, keepGoing: %s, skip: %s " % \
(count, keepGoing, skip)
print newtext
dlg.Destroy()
############### ############### ############### ############

The dialog looks right when this runs, but....

What's right: I get a progress bar; it includes "Skip" and "Cancel"
buttons; it shows 10 seconds of progress, and updates once per second
with the variables' values on each iteration.

What's wrong is that I can't get clicking on the "Skip" or "Cancel"
buttons to have any effect. Instead, as soon as the dialog displays,
I get an hourglass, and it doesn't matter what I click on. Here's
what the print statements display, consistently, regardless of what I
try to click or whether I click nothing at all:

I:\python>test1 .py
(before) count: 1, keepGoing: True, skip: False
(after) count: 1, keepGoing: True, skip: False
(before) count: 2, keepGoing: True, skip: False
(after) count: 2, keepGoing: True, skip: True
(before) count: 3, keepGoing: True, skip: True
(after) count: 3, keepGoing: True, skip: True
(before) count: 4, keepGoing: True, skip: True
(after) count: 4, keepGoing: True, skip: True
(before) count: 5, keepGoing: True, skip: True
(after) count: 5, keepGoing: True, skip: True
(before) count: 6, keepGoing: True, skip: True
(after) count: 6, keepGoing: True, skip: True
(before) count: 7, keepGoing: True, skip: True
(after) count: 7, keepGoing: True, skip: True
(before) count: 8, keepGoing: True, skip: True
(after) count: 8, keepGoing: True, skip: True
(before) count: 9, keepGoing: True, skip: True
(after) count: 9, keepGoing: True, skip: True
(before) count: 10, keepGoing: True, skip: True
(after) count: 10, keepGoing: True, skip: True

Two oddities here:

1) As I read the docs, the keepGoing variable should be set to True,
unless I click on "Cancel," in which case it should be set to False
(which would end the loop). That doesn't happen. This is really what
I'm most concerned here with.

2) The variable "skip: set to False on the first iteration, and then
set to True on subsequent iterations? Note that this happens even if
no buttons are selected. This is just a weirdness to me, and not my
main concern, but I thought I'd mention it in case it's relevant.

You can see some variations in the commented-out code that I tried;
they did not help.

Relevant software and releases:

OS: Windows XP Home Edition, Version 2002, SP2
Python: ActivePython 2.5.0.0
wxPython: 2.8.1.1 (msw-unicode)

Any help appreciated.
I'm not seeing the error either. The code looks very similar to the
example in the demo. Maybe you can look at it and see the difference?
The only thing I see is that the demo embeds the ProgressDialog into a
Panel object.

You should probably post this to the wxPython mailing group:
http://wxpython.org/maillist.php

Mike

Sep 15 '07 #2
On Sep 14, 11:57 pm, Terry Carroll <carr...@nosp am-tjc.comwrote:
I'm trying to use wx.ProgressBar, and the cancel button is not
responding.

Here is a simple program that exhibits the problem:

############### ############### ############### ############
import wx
import time

max = 10
app = wx.PySimpleApp( )
dlg = wx.ProgressDial og("Progress dialog example",
"variables to be shown here",
maximum = max,
style = wx.PD_CAN_ABORT
| wx.PD_CAN_SKIP
#| wx.PD_APP_MODAL
| wx.PD_ELAPSED_T IME
| wx.PD_ESTIMATED _TIME
| wx.PD_REMAINING _TIME
)

keepGoing = True
skip = False
count = 0

while keepGoing and count < max:
count += 1
wx.MilliSleep(1 000)
#time.sleep(1)
newtext = "(before) count: %s, keepGoing: %s, skip: %s " % \
(count, keepGoing, skip)
print newtext
(keepGoing, skip) = dlg.Update(coun t, newtext)
newtext = "(after) count: %s, keepGoing: %s, skip: %s " % \
(count, keepGoing, skip)
print newtext
dlg.Destroy()
############### ############### ############### ############

The dialog looks right when this runs, but....

What's right: I get a progress bar; it includes "Skip" and "Cancel"
buttons; it shows 10 seconds of progress, and updates once per second
with the variables' values on each iteration.

What's wrong is that I can't get clicking on the "Skip" or "Cancel"
buttons to have any effect. Instead, as soon as the dialog displays,
I get an hourglass, and it doesn't matter what I click on. Here's
what the print statements display, consistently, regardless of what I
try to click or whether I click nothing at all:

I:\python>test1 .py
(before) count: 1, keepGoing: True, skip: False
(after) count: 1, keepGoing: True, skip: False
(before) count: 2, keepGoing: True, skip: False
(after) count: 2, keepGoing: True, skip: True
(before) count: 3, keepGoing: True, skip: True
(after) count: 3, keepGoing: True, skip: True
(before) count: 4, keepGoing: True, skip: True
(after) count: 4, keepGoing: True, skip: True
(before) count: 5, keepGoing: True, skip: True
(after) count: 5, keepGoing: True, skip: True
(before) count: 6, keepGoing: True, skip: True
(after) count: 6, keepGoing: True, skip: True
(before) count: 7, keepGoing: True, skip: True
(after) count: 7, keepGoing: True, skip: True
(before) count: 8, keepGoing: True, skip: True
(after) count: 8, keepGoing: True, skip: True
(before) count: 9, keepGoing: True, skip: True
(after) count: 9, keepGoing: True, skip: True
(before) count: 10, keepGoing: True, skip: True
(after) count: 10, keepGoing: True, skip: True

Two oddities here:

1) As I read the docs, the keepGoing variable should be set to True,
unless I click on "Cancel," in which case it should be set to False
(which would end the loop). That doesn't happen. This is really what
I'm most concerned here with.

2) The variable "skip: set to False on the first iteration, and then
set to True on subsequent iterations? Note that this happens even if
no buttons are selected. This is just a weirdness to me, and not my
main concern, but I thought I'd mention it in case it's relevant.

You can see some variations in the commented-out code that I tried;
they did not help.

Relevant software and releases:

OS: Windows XP Home Edition, Version 2002, SP2
Python: ActivePython 2.5.0.0
wxPython: 2.8.1.1 (msw-unicode)

Any help appreciated.
Supposedly a progress dialog does not work well on its own because
events get screwed up when there isn't a main loop. Try this:

import wx

app = wx.PySimpleApp( )

win = wx.Frame(None, -1, "Test Progress Dialog")
button = wx.Button(win, -1, "start download")

def on_button_click (evt):
max = 10
dialog = wx.ProgressDial og(
"Loading",
"progress:" ,
max,
style = wx.PD_CAN_ABORT
|wx.PD_ELAPSED_ TIME
|wx.PD_ESTIMATE D_TIME
|wx.PD_REMAININ G_TIME
)
keep_going = True
skip = False
count = 0
while keep_going and (count < max):
count += 1
wx.MilliSleep(1 000)

(keep_going, skip) = dialog.Update(c ount)
print skip

dialog.Destroy( )
button.Bind(wx. EVT_BUTTON, on_button_click )

win.Show()
app.MainLoop()

Sep 15 '07 #3

Terry Carroll wrote:
I'm trying to use wx.ProgressBar, and the cancel button is not
responding.

Here is a simple program that exhibits the problem:

############### ############### ############### ############
import wx
import time

max = 10
app = wx.PySimpleApp( )
dlg = wx.ProgressDial og("Progress dialog example",
"variables to be shown here",
maximum = max,
style = wx.PD_CAN_ABORT
| wx.PD_CAN_SKIP
#| wx.PD_APP_MODAL
| wx.PD_ELAPSED_T IME
| wx.PD_ESTIMATED _TIME
| wx.PD_REMAINING _TIME
)

keepGoing = True
skip = False
count = 0

while keepGoing and count < max:
count += 1
wx.MilliSleep(1 000)
#time.sleep(1)
newtext = "(before) count: %s, keepGoing: %s, skip: %s " % \
(count, keepGoing, skip)
print newtext
(keepGoing, skip) = dlg.Update(coun t, newtext)
newtext = "(after) count: %s, keepGoing: %s, skip: %s " % \
(count, keepGoing, skip)
print newtext
dlg.Destroy()
############### ############### ############### ############

The dialog looks right when this runs, but....

What's right: I get a progress bar; it includes "Skip" and "Cancel"
buttons; it shows 10 seconds of progress, and updates once per second
with the variables' values on each iteration.

What's wrong is that I can't get clicking on the "Skip" or "Cancel"
buttons to have any effect. Instead, as soon as the dialog displays,
I get an hourglass, and it doesn't matter what I click on. Here's
what the print statements display, consistently, regardless of what I
try to click or whether I click nothing at all:

I:\python>test1 .py
(before) count: 1, keepGoing: True, skip: False
(after) count: 1, keepGoing: True, skip: False
(before) count: 2, keepGoing: True, skip: False
(after) count: 2, keepGoing: True, skip: True
(before) count: 3, keepGoing: True, skip: True
(after) count: 3, keepGoing: True, skip: True
(before) count: 4, keepGoing: True, skip: True
(after) count: 4, keepGoing: True, skip: True
(before) count: 5, keepGoing: True, skip: True
(after) count: 5, keepGoing: True, skip: True
(before) count: 6, keepGoing: True, skip: True
(after) count: 6, keepGoing: True, skip: True
(before) count: 7, keepGoing: True, skip: True
(after) count: 7, keepGoing: True, skip: True
(before) count: 8, keepGoing: True, skip: True
(after) count: 8, keepGoing: True, skip: True
(before) count: 9, keepGoing: True, skip: True
(after) count: 9, keepGoing: True, skip: True
(before) count: 10, keepGoing: True, skip: True
(after) count: 10, keepGoing: True, skip: True

Two oddities here:

1) As I read the docs, the keepGoing variable should be set to True,
unless I click on "Cancel," in which case it should be set to False
(which would end the loop). That doesn't happen. This is really what
I'm most concerned here with.

2) The variable "skip: set to False on the first iteration, and then
set to True on subsequent iterations? Note that this happens even if
no buttons are selected. This is just a weirdness to me, and not my
main concern, but I thought I'd mention it in case it's relevant.

You can see some variations in the commented-out code that I tried;
they did not help.

Relevant software and releases:

OS: Windows XP Home Edition, Version 2002, SP2
Python: ActivePython 2.5.0.0
wxPython: 2.8.1.1 (msw-unicode)

Any help appreciated.
Or, if you want the progress dialog to start when your app starts--
rather than after a user clicks on a button--you can use a short
timer:

import wx

app = wx.PySimpleApp( )

win = wx.Frame(None, -1, "Test Progress Dialog")
timer = wx.Timer(win)
#win.Bind(wx.EV T_TIMER, on_timer_expiry , timer)

def on_timer_expiry (evt):
max = 10
dialog = wx.ProgressDial og(
"Loading",
"progress:" ,
max,
style = wx.PD_CAN_ABORT
|wx.PD_ELAPSED_ TIME
|wx.PD_ESTIMATE D_TIME
|wx.PD_REMAININ G_TIME
)
keep_going = True
skip = False
count = 0
while keep_going and (count < max):
count += 1
wx.MilliSleep(1 000)

(keep_going, skip) = dialog.Update(c ount)
print skip

dialog.Destroy( )
timer.Stop()

win.Bind(wx.EVT _TIMER, on_timer_expiry , timer)
timer.Start(100 0)

win.Show()
app.MainLoop()

Sep 15 '07 #4
On Sep 14, 11:57 pm, Terry Carroll <carr...@nosp am-tjc.comwrote:
I'm trying to use wx.ProgressBar, and the cancel button is not
responding.

Here is a simple program that exhibits the problem:

############### ############### ############### ############
import wx
import time

max = 10
app = wx.PySimpleApp( )
dlg = wx.ProgressDial og("Progress dialog example",
"variables to be shown here",
maximum = max,
style = wx.PD_CAN_ABORT
| wx.PD_CAN_SKIP
#| wx.PD_APP_MODAL
| wx.PD_ELAPSED_T IME
| wx.PD_ESTIMATED _TIME
| wx.PD_REMAINING _TIME
)

keepGoing = True
skip = False
count = 0

while keepGoing and count < max:
count += 1
wx.MilliSleep(1 000)
#time.sleep(1)
newtext = "(before) count: %s, keepGoing: %s, skip: %s " % \
(count, keepGoing, skip)
print newtext
(keepGoing, skip) = dlg.Update(coun t, newtext)
newtext = "(after) count: %s, keepGoing: %s, skip: %s " % \
(count, keepGoing, skip)
print newtext
dlg.Destroy()
############### ############### ############### ############

The dialog looks right when this runs, but....

What's right: I get a progress bar; it includes "Skip" and "Cancel"
buttons; it shows 10 seconds of progress, and updates once per second
with the variables' values on each iteration.

What's wrong is that I can't get clicking on the "Skip" or "Cancel"
buttons to have any effect. Instead, as soon as the dialog displays,
I get an hourglass, and it doesn't matter what I click on. Here's
what the print statements display, consistently, regardless of what I
try to click or whether I click nothing at all:

I:\python>test1 .py
(before) count: 1, keepGoing: True, skip: False
(after) count: 1, keepGoing: True, skip: False
(before) count: 2, keepGoing: True, skip: False
(after) count: 2, keepGoing: True, skip: True
(before) count: 3, keepGoing: True, skip: True
(after) count: 3, keepGoing: True, skip: True
(before) count: 4, keepGoing: True, skip: True
(after) count: 4, keepGoing: True, skip: True
(before) count: 5, keepGoing: True, skip: True
(after) count: 5, keepGoing: True, skip: True
(before) count: 6, keepGoing: True, skip: True
(after) count: 6, keepGoing: True, skip: True
(before) count: 7, keepGoing: True, skip: True
(after) count: 7, keepGoing: True, skip: True
(before) count: 8, keepGoing: True, skip: True
(after) count: 8, keepGoing: True, skip: True
(before) count: 9, keepGoing: True, skip: True
(after) count: 9, keepGoing: True, skip: True
(before) count: 10, keepGoing: True, skip: True
(after) count: 10, keepGoing: True, skip: True

Two oddities here:

1) As I read the docs, the keepGoing variable should be set to True,
unless I click on "Cancel," in which case it should be set to False
(which would end the loop). That doesn't happen. This is really what
I'm most concerned here with.

2) The variable "skip: set to False on the first iteration, and then
set to True on subsequent iterations? Note that this happens even if
no buttons are selected. This is just a weirdness to me, and not my
main concern, but I thought I'd mention it in case it's relevant.

You can see some variations in the commented-out code that I tried;
they did not help.

Relevant software and releases:

OS: Windows XP Home Edition, Version 2002, SP2
Python: ActivePython 2.5.0.0
wxPython: 2.8.1.1 (msw-unicode)

Any help appreciated.
And here's a version that hides the frame and shows it only after the
progress dialog has finished or been cancelled:

import wx

app = wx.PySimpleApp( )

win = wx.Frame(None, -1, "Test Progress Dialog")
timer = wx.Timer(win)
#win.Bind(wx.EV T_TIMER, on_timer_expiry , timer)

def on_timer_expiry (evt):
max = 10
dialog = wx.ProgressDial og(
"Loading",
"progress:" ,
max,
style = wx.PD_CAN_ABORT
|wx.PD_CAN_SKIP
|wx.PD_ELAPSED_ TIME
|wx.PD_ESTIMATE D_TIME
|wx.PD_REMAININ G_TIME
)
keep_going = True
skip = False
count = 0
while keep_going and (count < max):
count += 1
wx.MilliSleep(1 000)

(keep_going, skip) = dialog.Update(c ount)
print skip

dialog.Destroy( )
timer.Stop()

win.Show() #************** ******

win.Bind(wx.EVT _TIMER, on_timer_expiry , timer)
timer.Start(100 0)

#win.Show()
app.MainLoop()

Sep 15 '07 #5
Terry Carroll wrote:
>
2) The variable "skip: set to False on the first iteration, and then
set to True on subsequent iterations? Note that this happens even if
no buttons are selected. This is just a weirdness to me, and not my
main concern, but I thought I'd mention it in case it's relevant.
The docs say:

wx.PD_CAN_SKIP
This flag tells the dialog that it should have a "Skip" button which
the user may press. If this happens, the next call to Update() will
return True in the second component of its return value.

What I'm seeing is: the second item in the tuple returned by Update()
is False if the skip button wasn't clicked and it's True for one
return value when the skip button was clicked, then the value reverts
back to False when Update() returns the next time.

Sep 15 '07 #6
On Sep 15, 5:25 pm, 7stud <bbxx789_0...@y ahoo.comwrote:
dialog.Destroy( )
timer.Stop()
win.Show() #************** ******
You can also change that last line to win.Destroy(), and then the user
will never see the frame.

Sep 16 '07 #7
Thanks to both kyosohma and 7stud for the suggestions. I'll try
variations on the code suggested by 7stud, and follow up to the
wx-python list as kyosohma suggested if I need more help.
Sep 18 '07 #8

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
1372
by: plumpy321 | last post by:
Hi, I took an example from wxPython with the IE web browser and created a refresh button to automatically refresh a web page in 5 second intervals. But I notice that the memory utilization in Python keeps increasing over time. Can anyone tell me why this is happening? Here is my code: ============================================================================
5
10657
by: fooooo | last post by:
This is a network app, written in wxPython and the socket module. This is what I want to happen: GUI app starts. User clicks a button to 'start' the work of the app. When start is pressed, a new thread is spawned (threading module) and this thread starts listening for data on a socket. When someone connects, a new thread is spawned, It needs to do I/O on that socket and open a GUI window so the user can communicate with the client...
2
1405
by: ccahoon | last post by:
In wxPython, I want to be able to start downloading a file and have the window doing such remain interactive, so that the user can cancel downloading the next file. Also, if there is a way to cancel a downloading process, what is it? I am using urllib.urlretrieve. Thanks for any help, in advance.
7
1816
by: John Salerno | last post by:
I was reading in the wxPython wiki that most of the time you don't have to include the id parameter at all, and you can just use keyword arguments for other parameters. But I'm having trouble converting this code into that method (i.e., without the id parameter). I keep getting errors that involve wrong parameters, or that they are out of order, etc. So I'm hoping someone can show me how to re-write the constructors for InputForm and...
8
1683
by: Patrick Smith | last post by:
Hi, I'm hoping someone here will be able to help as I've been struggling with this problem for a few days now. I'm working on an application that is creating a ProgressDialog, and then creating a thread that runs a function from another module in the program. The problem is, when the cancel button on the ProgressDialog is pressed, the thread that was created continues to run. How can I make it so that when the cancel button on the...
9
4424
by: Tyler | last post by:
Hello All: I am currently working on a project to create an FEM model for school. I was thinking about using wxPython to gather the 12 input variables from the user, then, after pressing the "Run" button, the GUI would close, and the 12 input variables would then be available for the rest of the program. So far, what I have been able to do is mostly a reverse engineering job to get the frame to look right and return the text variable...
5
2604
by: Benjamin | last post by:
I'm writing a search engine in Python with wxPython as the GUI. I have the actual searching preformed on a different thread from Gui thread. It sends it's results through a Queue to the results ListCtrl which adds a new item. This works fine or small searches, but when the results number in the hundreds, the GUI is frozen for the duration of the search. I suspect that so many search results are coming in that the GUI thread is too busy...
4
1924
by: Jimmy | last post by:
Hi, wxPython is cool and easy to use, But I ran into a problem recently when I try to write a GUI. The thing is I want to periodically update the content of StatixText object, so after create them, I pack them into a list...the problem comes when I later try to extract them from the list! I don't know why? my code is as following: import wx, socket import thread
6
3710
by: Iain King | last post by:
Hi. I have a modal dialog whcih has a "Browse..." button which pops up a file selector. This all works fine, but the first thing the user has to do when they open the dialog is select a file, so I would like the dialog to automatically call the onBrowse function as soon as the dialog opens. However, I don't know how to do this. dlg.ShowModal() onBrowse() obviously doesn't work, and neither does the reverse. I was hoping
0
8407
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look ! Part I. Meaning of...
0
8319
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
0
8837
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. Here is my compilation command: g++-12 -std=c++20 -Wnarrowing bit_field.cpp Here is the code in...
0
8739
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth. The Art of Business Website Design Your website is...
1
6175
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms. Adolph will...
0
5638
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert into image. Globals.ThisAddIn.Application.ActiveDocument.Select();...
0
4171
by: TSSRALBI | last post by:
Hello I'm a network technician in training and I need your help. I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs. The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols. I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
0
4329
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
2
1732
bsmnconsultancy
by: bsmnconsultancy | last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.